From its earliest days, software development has been beset with challenges in relation to timely delivery, appropriateness of features, and quality of deliverables. Many advances in software development processes have helped to address these concerns. For example, agile software development has helped to deliver working software more frequently, and capability maturity frameworks have brought about improved consistency in quality levels. However, the age‐old challenge of better, cheaper, faster software has continued to beguile developers. In this paper, we discuss an emerging approach to software development, continuous software engineering (CSE), wherein software of operational quality may be delivered on a very frequent basis, up to many times in a given day. This approach uses a complex set of independent tools that together reduce the lead time in delivering commercial‐grade software. Having examined the situational context of one industrial organization applying CSE, we conclude that the approach may not presently be appropriate to all manners of software development. Nonetheless, the authors are of the view that CSE represents a significant progression in software engineering and that software development settings of all types stand to gain from aspects of the CSE approach.
Abstract. The software development process is continuously changing, there is huge pressure to condense release cycles into shorter and shorter timeframes, tools are changing dramatically and companies must continually examine the efficacy of their development process. Attempting to hit a moving target is difficult and it is a decision which can have a major effect in terms of both the end-product and the business. In this paper, we discuss the role of situational context in deciding upon the software development process through the analysis of two case studies. The case studies take a detailed look at the organisational profile and context of each company in turn before we compare and contrast each situational context for factors that may influence the development process. We then compare the processes each company has chosen before our discussion of the role context plays in choosing a 'correct' software development process. While both companies have enjoyed sustained business growth and while both are agile in mind-set, we find that they are in fact quite distinct in their processes, this distinction being driven by their different situational contexts.
Given that organizations need to innovate and release software in faster parallel cycles of days or even hours, there are good reasons why new practices are being adopted in industry. In this paper, we present the case of a highly responsive process that is driven by tooling technology and which facilitates continual delivery of software at up to hourly intervals. This approach can inform academic and practitioner dialogue on current challenges and potential solutions, and on the evolution of new 'better' practices. CCS Concepts• Software development process management KeywordsSoftware development lifecycle; Lean software development.
Over the decades, a variety of software development processes have been proposed, each with their own advantages and disadvantages. It is however widely accepted that there is no single process that is perfectly suited to all settings, thus a software process should be molded to the needs of its situational context. In previous work, we have consolidated a substantial body of related research into an initial reference framework of the situational factors affecting the software development process. Practitioners can consult this framework in order to profile their context, a step necessary for effective software process decision making. In this paper, we report on the findings from a case study involving process discovery in a small but successful and growing software development firm. In this organization, which has a focus on continuous software evolution and delivery, we also applied the situational factors reference framework, finding that context is a complex and key informant for software process decisions. Studies of this type highlight the role of situational context in software process definition and evolution, and they raise awareness not just of the importance of situational context, but also of the complexity surrounding software process contexts, a complexity which may not be fully appreciated in all software development settings. CCS Concepts• Software and its engineering ➝ Software creation and management ➝ Software development process management ➝ Software development methods.
In this paper, we provide an analysis of Function as a Service (FaaS) infrastructures. FaaS is an important, emerging category of cloud computing, which requires that software applications are designed and deployed using distributed, highly-decoupled service-based architectures, one example of which is the microservices architecture paradigm. FaaS is associated with on-demand functionality and allows developers to build applications without the overhead associated with server management. As such, FaaS is a type of serverless provisioning model wherein a provider dynamically manages and allocates machine resources, with the developers deploying source code into a production environment. This research provides an analysis of scalability, cost, execution times, integration support, and the constraints associated with FaaS services provided by several vendors: AWS Lambda, Google Cloud Functions, and Azure Functions. We discuss the implications of the findings for software developers.
In this paper, we present a data mining approach for analysing students' clickstream data logged by an e-learning platform and we propose a machine learning procedure to predict course completion of students. For this, we used data from a short MOOC course which was motivated by the teachers of elementary schools. We show that machine learning approaches can accurately predict the course outcome based on clickstream data and also highlight patterns in data which provide useful insights to MOOC developers.
Misunderstandings in voice radio communication have been identified as a root cause of accidents at sea. One reason is language problems in a multi ethnic industry. Standard Marine Communication Phrases (SMCP) was developed by the IMO to mitigate this problem, but studies show it is not commonly used. Difficulties to pronounce and understand English spoken by different nationalities adds to the problem. Maybe text messaging could be useful in non-time critical marine communication? This paper presents a study where VHF voice versus text messages in a land-based deep sea pilotage scenario was compared. The finding was that text based messages worked well and that there was a lower risk of misinterpreting the information.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
334 Leonard St
Brooklyn, NY 11211
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.