Technology enabled continuous software development

Clarke, Paul M.; Eklund, Peter; O’Connor, Rory V.

doi:10.1145/2896941.2896943

Cited by 7 publications

(6 citation statements)

References 1 publication

(1 reference statement)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…More agility is therefore also needed. In an ideal situation, quality and productivity factors would converge on a single point, and this is perhaps an outcome that can be achieved through the more aggressive adoption of technology-enabled software development processes [18] that we are starting to see emerging in the general software engineering field.…”

Section: Fig 3 Use Of Situational Factors In Defining a Safety Profilementioning

confidence: 99%

Situational Factors in Safety Critical Software Development

Nevalainen¹,

Clarke

McCaffery

et al. 2016

Communications in Computer and Information Science

View full text Add to dashboard Cite

Abstract. The generic software development situational factors model has been developed in order that environments within which software is developed can be profiled and better understood. Situational context is a complex concern for software developers, with a broad set of situational factors holding the potential to affect any one software development project. Safety critical software development is broadly similar to other kinds of software development / engineering. But there are some additional or more dominant situational factors. In this article we conduct a conceptual experiment to define safety critical software development context using situational factors. Eleven such factors are identified, with some of the factors requiring elaboration beyond the detail presently available in the generic situational factors model. We firstly discuss the appropriateness of the selected factors in generic safety critical software development context. Thereafter we apply the selected factors to the medical device and nuclear power domains. Selected situational factors can be used as a high level profile and starting point for more detailed process and safety assessment. Discussion about potential use cases and further development needs is also presented.

show abstract

Section: Fig 3 Use Of Situational Factors In Defining a Safety Profilementioning

confidence: 99%

Situational Factors in Safety Critical Software Development

Nevalainen¹,

Clarke

McCaffery

et al. 2016

Communications in Computer and Information Science

View full text Add to dashboard Cite

show abstract

“…The authors take the view that one can consider CSE to be the next major wave in software engineering to follow the agile software development 11 and lean software development 12 movements. It is different to these earlier approaches in that CSE emphasizes the role of tooling in software development, 13 which at least to some extent runs contrary to the agile manifesto, which values individuals and interactions over processes and tools. With CSE, the importance and investment in tool chains is large, and its centrality to the delivery life cycle is likely to raise its value to at least be on a par with the value associated with individuals and interactions.…”

Section: Introductionmentioning

confidence: 93%

“…Microservices are small applications that can be deployed independently, scaled independently, and tested independently and that has a single responsibility . The term microservice architecture refers to a style of development under which a system is broken down into a number of small co‐operating components, where these components typically interact over a direct point‐to‐point interface (for example, http) or using an event bus technology such as Apache Kafka or RabbitMQ.…”

Section: Case Study Companymentioning

confidence: 99%

“…Microservices are small applications that can be deployed independently, scaled independently, and tested independently and that has a single responsibility. 13 The term microservice architecture refers to a style of development under which a system is broken down into a Productivity Team ability to carry out tasks quickly; general productivity.…”

Section: Microservice Architecturementioning

confidence: 99%

See 1 more Smart Citation

Continuous software engineering—A microservices architecture perspective

O’Connor

Eklund

Clarke

2017

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

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.

show abstract

“…Microservice are a small application that can be deployed, scaled and tested independently and that has a single responsibility [3]. The Microservices architecture is an architectural alternative in building an application.…”

Section: Introductionmentioning

confidence: 99%

Design and Implementation of Microservices System Based on Domain-Driven Design

Fajar¹

2020

IJETER

View full text Add to dashboard Cite

PT. XYZ as an IT company has developed a basic product system for e-procurement applications to meet the needs of automation in the internal procurement process of a company. The e-procurement application system developed by PT. XYZ is designed using a monolithic architecture where the application is wrapped in a large package and dependencies between modules. The modules are an integrated whole process. If there is a change or enhancement to one particular module that is made to adjust the business process, then this will have an impact on the functionality of the other modules. Therefore it is necessary to consider other architectural alternatives so that in the future the e-procurement application system is more adaptive to change. So, it can face problems that arise with old architecture. We proposed the design the transformation process using microservices architecture. We use Domain-Driven Design (DDD) approach. The results showed that the microservices architecture design can produce a system that is more adaptive to a change in which the module is designed to stand alone.

show abstract

Technology enabled continuous software development

Cited by 7 publications

References 1 publication

Situational Factors in Safety Critical Software Development

Situational Factors in Safety Critical Software Development

Continuous software engineering—A microservices architecture perspective

Design and Implementation of Microservices System Based on Domain-Driven Design

Contact Info

Product

Resources

About