Search

In this article we report some practical experiences of integrating education for sustainable development into established university teaching modules. The 2021 guidance on Education for Sustainable Development from the UK's standards bodies QAA and Advance HE is an important and urgent motivation for introducing sustainability into university courses. We take as our context a first-year introductory module in Chemical Products and Process in the School of Chemistry and Chemical Engineering and a second-year module in Software Engineering and Systems Development in the School of Electronics, Electrical Engineering and Computer Science, both at Queen's University Belfast. We outline some of the challenges of adding new themes to existing courses. We comment on ways of presenting themes of sustainable development alongside existing module content, and we indicate the type of work students produced. We identify approaches that resulted in good outcomes, and outline changes we have made with a view to improved future outcomes. [ABSTRACT FROM AUTHOR]

Software development activities are increasingly being conducted collaboratively across multiple time zones and multiple teams. This creates challenges in building shared values and trust, and in coping with asynchronous collaboration and communication. In response to these trends, tools such as wikis, blogs, web portals and groupware are being integrated in development processes to enhance the productivity and effectiveness of teams. To enable students to meet these challenges, there is a need to use technology in software engineering education to simulate authentic structures of work practices. Use of collaborative and discourse tools will provide students with the experiences of communicating and negotiating with diverse stakeholders with different views and backgrounds. It will also enable the development of transferable skills for working with community tools in the industry. As with most software design and development processes. Requirements Engineering (RE) is increasingly being conducted in distributed environments. Wikis are being used to provide a platform for asynchronous collaboration for participative requirements development. In a post-graduate RE part-time distance-learning course at the Open University in the UK. we have introduced wiki activities in the course to provide students with the opportunity to engage in small-group collaboration to emulate RE practice. In this paper, we discuss the nature of the RE process, the usage of wikis in RE practice, and the challenges of introducing collaborative-work and wikis on the RE course at the Open University and our solutions. We will draw on empirical evidence to discuss effectiveness of wiki in collaborative learning of the RE processes. [ABSTRACT FROM AUTHOR]

Examines the implication of perceptual bias on the pain research for software engineering in Great Britain. Applicability of the peak-end effect on the software engineering; Difference between the pain domain and of usability evaluation; Risk of peak-end effect misuse. INSET: Jugment and Decision-Making Literature..

Focuses on the knowledge management (KM) in software engineering in Great Britain. Improvement of knowledge on basic motivation and driver for KM; Advantages of KM on decreased time and cost and increased quality for business; Role of KM in software engineering.

The article presents three cases to illustrate that the digital world phenomenon which improves accessibility of services and communal communication could also raise several ethical issues relating to privacy, monitoring and data protection and could also have the potential to cause harm. It discusses a legislation in Great Britain that pose three key challenges for software engineers designing systems for the digital world. The notion of ethics-aware software engineering is also advocated in the article, where ethical considerations are taken into account across the software development cycle.

This research examines the prevalence of research software as independent records of output within UK academic institutional repositories (IRs). There has been a steep decline in numbers of research software submissions to the UK's Research Excellence Framework from 2008 to 2021, but there has been no investigation into whether and how the official academic IRs have affected the low return rates. In what we believe to be the first such census of its kind, we queried the 182 online repositories of 157 UK universities. Our findings show that the prevalence of software within UK Academic IRs is incredibly low. Fewer than 28% contain software as recognised academic output. Of greater concern, we found that over 63% of repositories do not currently record software as a type of research output and that several Universities appeared to have removed software as a defined type from default settings of their repository. We also explored potential correlations, such as being a member of the Russell group, but found no correlation between these metadata and prevalence of records of software. Finally, we discuss the implications of these findings with regards to the lack of recognition of software as a discrete research output in institutions, despite the opposite being mandated by funders, and we make recommendations for changes in policies and operating procedures. [ABSTRACT FROM AUTHOR]

Presents a debate on software engineering standards in Great Britain. Focus on safety-critical software for defense applications; Aim to assess the 'politics' of formal methods of software production; Implications of the standards on reshaping discipline of software engineering.

This article explores the conditions under which interprofessional relations may be characterized by conflict and/or cooperation through a case study of the rise of a software engineering (SWE) profession in the United States, United Kingdom, and Canada. Analysis of professional journal publications produced by the primary computing organizations in all three countries reveals that the development of a SWE profession in the United Kingdom, and to a lesser extent, the United States, has been a collaborative project pursued by engineering and computing organizations. In contrast, the development of SWE in Canada has been characterized by intense interprofessional conflict. The investigation suggests that interprofessional conflict may be mitigated when professionalizing groups seeking to lay claim to the same jurisdiction are similar in terms of their organizational size, outlook, and regulatory status. [ABSTRACT FROM AUTHOR]

Good data curation is integral to cohort studies, but it is not always done to a level necessary to ensure the longevity of the data a study holds. In this opinion paper, we introduce the concept of data curation debt-the data curation equivalent to the software engineering principle of technical debt. Using the context of UK cohort studies, we define data curation debt-describing examples and their potential impact. We highlight that accruing this debt can make it more difficult to use the data in the future. Additionally, the long-running nature of cohort studies means that interest is accrued on this debt and compounded over time-increasing the impact a debt could have on a study and its stakeholders. Primary causes of data curation debt are discussed across three categories: longevity of hardware, software and data formats; funding; and skills shortages. Based on cross-domain best practice, strategies to reduce the debt and preventive measures are proposed-with importance given to the recognition and transparent reporting of data curation debt. Describing the debt in this way, we encapsulate a multi-faceted issue in simple terms understandable by all cohort study stakeholders. Data curation debt is not only confined to the UK, but is an issue the international community must be aware of and address. This paper aims to stimulate a discussion between cohort studies and their stakeholders on how to address the issue of data curation debt. If data curation debt is left unchecked it could become impossible to use highly valued cohort study data, and ultimately represents an existential risk to studies themselves. [ABSTRACT FROM AUTHOR]

• Overview of human biases influencing digital forensics investigators. • Analysis of the UK's Post Office case, pointing to root causes and biases. • Digital forensics investigation framework to mitigate against human bias. • Evaluation of framework by digital forensics investigator. Software invisibly permeates our everyday lives: operating devices in our physical world (traffic lights and cars), effecting our business transactions and powering the vast World Wide Web. We have come to rely on such software to work correctly and efficiently. The generally accepted narrative is that any software errors that do occur can be traced back to a human operator's mistakes. Software engineers know that this is merely a comforting illusion. Software sometimes has bugs, which might lead to erratic performance: intermittently generating errors. The software, hardware and communication infrastructure can all introduce errors, which are often challenging to isolate and correct. Anomalies that manifest are certainly not always due to an operator's actions. When the general public and the courts believe the opposite, that errors are usually attributable to some human operator's actions, it is entirely possible for some hapless innocent individual to be blamed for anomalies and discrepancies whose actual source is a software malfunction. This is what occurred in the Post Office Horizon IT case, where unquestioning belief in the veracity of software-generated evidence led to a decade of wrongful convictions. We will use this case as a vehicle to demonstrate the way biases can influence investigations, and to inform the development of a framework to guide and inform objective digital forensics investigations. This framework, if used, could go some way towards neutralising biases and preventing similar miscarriages of justice in the future. [ABSTRACT FROM AUTHOR]

Focuses on issues related to the study of software engineering in Great Britain. Importance of adoption of the same correct construction methods as other fields; Accomplishment of verification of embedded software; Use of automated tools to assist human designers.

Where do workers with Higher Education (HE) degrees develop their work skills? Although few would expect these to be developed in HE exclusively, there exists an assumption that the core skills of those working in graduate occupations are predominantly formed at HE. This article examines how within four graduate occupations, employers and workers assess the extent HE is thought to develop the skills and knowledge used within the work process. It draws on occupational case studies on the work of laboratory-based scientists, software engineers, financial analysts and press officers, using interview data with workers, employers and stakeholders. The study shows that structural barriers prevent HE to take a significant part in work skill and knowledge development, but also that HE is not necessarily heavily relied upon for skill formation. More precaution is required when linking the skill demands for graduate work with the skills that are developed or associated at university. [ABSTRACT FROM AUTHOR]

This paper gives a brief introduction to the capability issues in the UK and expands on the University of North London's capability curriculum. A short background to the module of software engineering and elaborates on the rationale for and the development of the new module, software engineering for computer science. It discusses the need for a partnership between educators, employers and the government in moving forward the capability agenda. Le développement d'un module d'ordinateur incorporant un curriculum de capacité. Cet article donne une brève introduction des curriculum de capacité dans le Royaume Uni et traite des curriculum de capacité de l'Université de North London. Un bref rappel de l'arrière plan des modules de software pour l'engineering, puis on élabore un raisonnement pour le développement du module nouveau: Software d'Engineering pour la science informatique. L'article discute le besoin de partenariat entre éducateurs, employeurs et le gouvernement en avancant vers un programme de capacité. Die Entwicklung eines Rechnermodule einschließenden Lehrplans Dieser Beitrag gibt eine kurze Einführung zum Thema Begabung im UK und leitet über zur Lehrplanentwicklung der Universität von Nord-London. Er zeigt kurz den Hintergrund zum Thema Software Engineering auf und geht dann ausführlicher auf die Begründung und die Entwicklung der neuen Module Software Entwicklung für Computerwissenschaften ein. Er belegt die Notwendigkeit einer Partnerschaft zwischen Erziehungswissenschaftlern, der Wirtschaft und der Regierung bei der Weiterentwicklung der Lehrpläne. [ABSTRACT FROM AUTHOR]

The article focuses on the development of a model curriculum for a new kind of software engineering technique, the Aspect-oriented software development (AOSD) in Great Britain. The new kind of discipline is transitioning from specialized industrial courses to post-graduate teaching in universities and is very evident in enterprise application research. The increasing maturity of the new discipline requires the development of a curriculum that will train students in the application of a three-dimensional approach to systems analysis, development and evolution. The European Network of Excellence on AOSD has proposed a model curriculum that is of modular in nature, providing a structured body of knowledge that allows selection of specific topics on a specific time. INSET: Aspect-Oriented Software Development.

The Urban Observatory (UO) at Newcastle represents a multi-million-pound investment in ubiquitous urban sensing, providing one of the largest real-time environmental datasets in the world. This research facility, majority staffed by research software engineers, provides open data used by community groups, local and national government, and research projects ranging from cyber-security to flood forecasting. Requirements and demands have developed over the last three years, and as new data sources were incorporated, RSEs were introduced with expertise in machine learning, high-performance computing, and hybrid database architecture. The UO's journey has not been plain sailing. Early efforts were plagued by communication problems and inconsistent clocks, rapid growth and attempts to maintain flexibility resulted in severe performance degradation, and progression into providing statistics about crowd density and people movements has introduced cyber-security and data protection challenges. This mixture of skills has broadened the remit of the RSEs involved, emphasised the need to communicate the lessons learned by means other than traditional academic publishing, and created opportunities for staff development in the form of new skills and supervision. The UO benefited from simultaneous improvements made by RSEs across the university; staff in similar roles were beginning to meet and discuss software engineering in their own research contexts, the need for formal recognition of their roles, and career progression. This began as links between software engineers within computing and engineering but has grown to incorporate diverse backgrounds from across the university. From initial interactions, these have become a series of meetups where staff in different disciplines can come together to discuss best practices when developing software for research. Progress is being made gaining recognition for the RSE role within the university, and the visibility of RSEs in the UO is benefiting the cause.Today, the UO receives and archives more than one hundred metrics per second, in addition to still images, video, radar and laser-scan matrices. Machine learning methods are applied in real-time across CCTV streams, and significant changes are identified using edge processing to reduce network loading. The introduction of data queues, progressively more sophisticated data sharding, thirty edge processors, and hourly replication has drastically reduced the frequency of problems. This would not have been possible without recognition for RSEs and their skills, and leveraging knowledge from the whole university. Incorporating robust software engineering principles into the UO played a key role in allowing it to grow from a research project in a single school to one of the university's flagship research facilities, and a world-leading exemplar for running city-scale experiments on IoT networks. Designing systems that scale, are reliable, and well-maintained is the central aim of an RSE. Examples such as this will help both in Newcastle and in the wider national community for a long term aim of getting RSEs recognised as a career path within academic institutions. The UO in Newcastle is the first of six observatories in the UK, and as these other observatories begin provisioning their networks, we hope it will facilitate RSE collaboration nationally and internationally. [ABSTRACT FROM AUTHOR]

Electronic Patient Records systems configured into large enterprise models have become the assumed best route forward. In England, as in several other countries, this has expanded to a major meta-enterprise procurement programme. However, concerns are raised that such systems lack user ownership, and experience from other sectors shows difficulties with large enterprise systems. At a time of great change and once again shifting organizations, is this move simply building large and ponderous edifices with unstable materials? Latest software engineering research is now demonstrating the potential of an alternative model, enabling trusted information brokers to search out in real time at point of use data held in registered local and departmental systems. If successful, this could enable a new and less cumbersome paradigm. The data could move where needed whatever the service configuration. A concept demonstrator has been built set in the context of health and social care in England. It is important for all technological support to the health sector to be reviewed as new technologies emerge so as to identify and exploit new opportunities, and the results of this 3 year project show that the health record information broker route merits further investigative research. [ABSTRACT FROM AUTHOR]

The government of the United Kingdom is offering significant amounts of funding to increase engagement between researchers and technology companies involved in the creative economy , a sector worth £100b per annum. The sector has naturally evolved into clusters involving actors as diverse as the BBC, the Victoria and Albert Museum, and freelance game designers. It collaborates and competes with multinational powerhouses including Google, Microsoft, and Pixar. The imbrication of academic researchers in the sector makes it a good example of the extension of academia to industry, raising ethical but also methodological and practical questions. This article describes a project that embedded a research software engineer (RSE) from a digital humanities (DH) laboratory into a small technology start-up engaged in high risk R&D of an immersive narrative story-telling platform. The platform is enabled by artificial intelligence and has the capacity to remember user input and modify narrative options and character mood accordingly. The team included a researcher specialising in narrative theory and digital production. The project demonstrated the utility of the critical application of DH methods and the need to develop career pipelines to produce people capable of working at the intersection of higher education and industry. [ABSTRACT FROM AUTHOR]

Presents news briefs pertaining to management in Great Britain as of June 1988. Industry-related experience for mathematics teachers; Opportunity for young women to discover a career in engineering; Scheme to solve the skill shortage in software engineering.

The article focuses on the use of Simple Object Access Protocol (SOAP) to determine and define the content of the XML document and to interoperate with other applications in Great Britain. SOAP is a lightweight protocol used for exchange of information in a decentralized and distributed environment. It states that SOAP-based services are the basis on the inclination toward service-oriented architecture, but it also made mention of the difficulties because a software engineer has to master all the necessary specifications. It further stresses that though SOAP promises portability it would still be wise to consider factors such as network latency in the conversion of XML documents. INSET: SOAP Resources.

Copyright of RED - Revista de Educación a Distancia is the property of Universidad de Murcia and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

In this paper we present survey data characterizing the implementation of SPI in 85 UK companies. We aim to provide SPI managers with more understanding of the critical success factors of implementing SPI. We present an analysis of the critical implementation factors identified in published case studies. We use a questionnaire to measure the use of these factors in ‘typical’ software companies. We found that many companies use SPI but the effectiveness of SPI implementation is variable. Many companies inadequately resource SPI and fail to evaluate the impact of SPI. On the other hand, companies show a good appreciation of the human factors associated with implementing SPI. Copyright © 2002 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

This paper introduces a proof‐of‐concept spatial decision support system (SDSS) that assists decision‐makers to generate equitably distributed sensor networks and evaluate their placement with reference to specific population‐based coverage criteria. Our approach centres equity in infrastructure distribution; we focus on the decision‐making process required to achieve the best possible sensor coverage of the geographical area for selected vulnerable populations and visualise trade‐offs in coverage inherent in infrastructure distribution. The development of the tool brings together expertise from quantitative geography, urban planning, data science and software engineering, and its technical development is underpinned and shaped by interviews with decision‐makers and their iterative feedback. Through this, we ask: how can decision support tools help with the work of building equitable infrastructure? As well as a technical application, our approach develops a conceptual framework for evaluating sensor network purpose and distribution before actual placement. The unique combination of distribution algorithms, user interface and decision‐maker input, developed by an interdisciplinary team, offers a novel approach to sensor network conceptualisation and generation. Our research contributes to the understanding of the distribution of essential infrastructure and can be repurposed for any sensor type and geographical location to promote equity in infrastructure distribution. [ABSTRACT FROM AUTHOR]

This paper examines the efficiency and effectiveness of a prescriptive systems development methodology in practice. The UK government’s mandatory Structured Systems Analysis and Design Method (SSADM) was examined to determine its value to software projects. The evidence was collected from interviews with 17 project managers, discussions with participants on three large software projects and from observing 90 end users in training. The conclusions are that prescriptive information systems methodologies are unlikely to cope well with strategic uncertainty, user communication or staff development. The recommendations are to focus more on soft organizational issues and to use approaches tailored to each project. © 1997 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

The article focuses on the British Standards Institution (BSI), a standards body in Great Britain appointed by royal charter to promote standards in the best public interest. Included is a list of different kinds of standard that may be developed by the BSI. Particular focus is given to the responsibilities of a BSI committee on software engineering, along with the idea behind the committee's diverse membership.

The article focuses on the impact of test-driven design on the quality of software designs in Great Britain. It illustrates the process by which software developers use the test-driven design in determining the quality of software and relates on a statistical research that proves that the test design indeed helps increase the quality of software although it lessen productivity rate due to difficulty in writing the codes. Moreover, it discusses the way that the design is helping the improvement of code quality in a manner by which it provides a common ground for software developers and business people to sit down and work on a project.

The article reports on the data archiving strategy initiated by Severn Trent Water in Great Britain as part of the roll-out of a new enterprise resource planning (ERP) system from SAP AG applications for more than 5,000 water users. It notes that the program provides best services and deliver the lowest charges to customers. It notes that with the use of the software application from SAP, it can produce number of benefits to consumers by providing accurate data and offers operational costs down.

The article informs about the extensive use of computer software in the civil nuclear industry. Software failures occur due to flaws in designing during the software development phase. It reveals that software used in safety critical systems are against the guidelines of Great Britain's Nuclear Installations Inspectorate. It discusses the theoretical and practical aspects of various standards of safety critical software. The prediction regarding the software are not considered worthwhile as they are incapable of demonstrating right failure rates and flaw density. It is suggested not to depend on Safety Integrity Levels, rather, attempts should be made to avoid erroneous data values.

The article focuses on the career of software engineer Lincoln Wallen in Great Britain. It indicates that Wallen's research on the application of computer in solving mathematical problems has helped him becoming a successful software engineer. He was named as a British Petroleum Venture Research Fellow at the University of Texas at Austin. He moved to the company Criterion Software and became the firm's vice president of Renderware Mobile in Guildford, Surrey.

Purpose: This paper investigates how individuals' decision-making approach and perceptions of a game's cognitive realism affect the performance of virtual businesses in a web-based simulation game. Design/methodology/approach: Survey data are collected from 274 business simulation game users and is analysed using the fsQCA technique. Findings: The study identifies three alternative pathways to high and low performance in a business simulation game. Results indicate that a flexible decision-making approach exists in all high performance pathway solutions. Where a game is perceived to be realistic, a more focused decision-making approach is associated with high performance. However, where perceived cognitive realism is absent, a less focused experimental decision-making approach is employed, which increases the chances to achieve low performance. Finally, perceived cognitive realism and an experimental decision-making approach are found to be mutually exclusive for achieving high performance. Originality/value: Whilst the learning benefits of web-based simulation games are widely acknowledged, the complex interplay amongst factors affecting performance in games is under-researched. Limited research exists on how perceptions of a game's cognitive realism interact with user decision-making approaches to affect performance. [ABSTRACT FROM AUTHOR]

This section comments on an article about software process improvement approaches in Japan and Great Britain. There is a growing fear that Japan may take over the software market. It comments on the competition of the Japanese software industry with Europe and the United States.

Six articles and case studies examine continuing education in the United Kingdom. Highlights include vocational education and training; the Professional, Industrial and Commercial Updating Programme (PICKUP); retraining in software engineering; Higher Introductory Technology and Engineering Conversion Course (HITECC); training needs in manufacturing; and the Seafish Open Learning Project. (LRW)