AMDiRE - Artefact Model for Domain-independent RE

The various influences on processes and application domains make requirements engineering (RE) inherently complex and difficult to implement. When it comes to define an RE reference model for a company-wide use, we basically have two options: we can establish an activity-based RE approach where we define a blueprint of the relevant RE methods and description techniques, or we can establish an artefact-based approach where we define a blueprint of the RE artefacts rather than a blueprint of the way of creating the artefacts. In the last six years, we have established several artefact-based RE approaches and empirically underpinned the advantages of applying those approaches in industry. Those approaches remain, however, complex as they encompass various modelling concepts, and, in particular, incorporate their particularities of the different application domains, such as the one of business information systems. For this reason, we consolidated the different approaches and established the AMDiRE approach, i.e. the artefact model for domain-independent requirements engineering. AMDiRE includes a detailed artefact model that captures the basic modelling concepts used to specify RE-relevant information, tool support, and a tailoring guideline that guides the creation of the artefacts. To provide a quick overview of the basic concepts of AMDiRE and the underlying principles, this report serves as a Cheat Sheet. This cheat sheet shall facilitate the basic understanding about the fundamentals in artefact orientation and provide an overview of a flexible artefact-based RE approach ready to be applied in practical contexts without focussing on technical details.     «

The various influences on processes and application domains make requirements engineering (RE) inherently complex and difficult to implement. When it comes to define an RE reference model for a company-wide use, we basically have two options: we can establish an activity-based RE approach where we define a blueprint of the relevant RE methods and description techniques, or we can establish an artefact-based approach where we define a blueprint of the RE artefacts rather than a blueprint of the...     »