When do projects end? - The role of continuous software engineering

Abstract

Agile development methods have been proven to increase the quality of interactive systems because they allow quick adaptation to continuously changing requirements that are enforced by a fast changing reality. Additionally, models are very helpful to specify the understanding of analysts; developers and users of the domain. If models can be animated, they provide very good basis for discussions. The engagement of all participants is often much higher in this case. Currently, a lot of specification languages like UML, BPMN, or S-BPM are used to document the results of the analysis of the domain in most projects. Additionally, it can be recognized that the focus on users increases. S-BPM is already an example for that. It provides a special view on business processes that is missing in BPMN. It focusses on subjects that often are users but could also be software systems. This shifting focus goes together with a trend from Technology-Driven Design to Human-Centered Design. The paper discusses the combination of agile development methods with Continuous Software Engineering. It argues for an integration of Human-Centered Design methods with business process modeling and Continuous Requirements Engineering. The concepts of existing approaches of Continuous Software Engineering are extended accordingly. Therefore, classical maintenance does not exist anymore.