Using business process modelling to reduce the effects of requirements changes in software projects

Abstract

Requests for changes to software systems have a potential damaging effect on software projects and the life span of software. Changes can not be avoided since it seems impossible to produce complete, correct and stable requirements. Late requests for deep, structural software changes are particularly harmful.We present an approach for early detection of evolutionary changes of software requirements, especially deep structural changes that have implications for the software architecture. The approach is based on using business process modelling (BPM) as a tool to increase the level of understanding of the problem domain in early stages. This enables the system stakeholders to identify and prevent certain types of changes earlier in the development process than what is usual with most commonly used development methods.We present a possible taxonomy of changes to help managing the different types of changes that are most important for our purpose.

A Taxonomy for Personal Processes: Results from a Semi-structured Interview

“…In [2], a taxonomy of change with four main classes are suggested: "time of change", "origin of change", "type of change", and "structural effect of change" that can be used in detecting changes before they are reported. A taxonomy for BPM flexibility with a focus of change is also suggested in study [6]: abstraction level of change, subject of change, and properties of change.…”

“…Several taxonomies are suggested within the Business Process Management (BPM) domain, i.e. for BPM techniques [1], requirement changes attributes [2], unstructured workflows [3], execution exceptions [4], process flexibility ( [5,6]) and time rules [7]. Yet, no taxonomy has ever been developed with a focus on personal processes.…”

ChaordicLedger: Knowledge Transfer for Industry

“…Beyond support for Complex Systems Engineering, a tangible impact exists in the ability to predict costs, estimate change impact, and quantify value. "Software development methods that integrate requirements analysis with the organizational and external requirements are crucial in view of the fact that socio-technical systems are a vital part of the organization's value chain" [8]. Using a tool to enable linkage between artifacts has the additional benefit of providing unambiguous inputs to the Cost Model for Verifying Requirements (CMVR), which is predicated on traceability of requirements from stakeholders down through individual tests [9].…”