Handling of Explicit Uncertainty in Requirements Change Management

Abstract

Innovation projects are characterized by numerous uncertainties. Typical concepts in development management like the application of safety coefficients imply limitations of the solution space. In contrast, explicit handling of uncertainties can support engineers in understanding the problem space and in utilising the full potential of the design space along iterative product development steps. As a result from literature analysis, there is a lack of a support for product development that addresses the specific problem of uncertainty and risk in the context of requirement changes. The aim of the contribution at hand is to enhance the efficient development of complex interdisciplinary systems by enabling uncertainty handling in requirements change management. Based on a classification of uncertainty types resulting in a descriptive model, risk management measures are identified to support requirements engineers. The proposed method includes identification & modelling, analysis, treatment and monitoring of risks and counter-measures. By applying this method, engineers are supported in adopting agile approaches and enabling flexible Requirements Engineering.

Reframed Design Thinking and Feasibility Analysis of UX Journey: Integrating User Experience and User Requirement for Solo Software Development

“…User requirements in many instances become larger and change more rapidly than they should. This situation occurs because of several possibilities, including (1) changes in business processes, (2) incomplete exploration of requirements, (3) a misunderstanding of the perceptions of users, (4) strategic changes inside the client organization, (5) stakeholder engagement, (6) the development team's communication quality (7), and (8) Improved comprehension of the technical solution [2,13]. Particularly, decisions about the deployment of preventative measures demand a thorough understanding of the risk of change.…”

“…The elicitating problem of user requirements occurs for various reasons. Several factors can cause this problem including [2,13,16] :…”

Proactive Management of Requirement Changes in the Development of Complex Technical Systems

“…Four action strategies are differentiated: avoidance, transfer, reduction and acceptance [27]. Proactive measures are assigned to an action strategy based on the intended effect [69]:…”

Proaktives Management von Anforderungsänderungen in der Entwicklung komplexer technischer Systeme

“…Unsicherheiten in der Produktentwicklung sind die Ursache für Anforderungsänderungen [GPO21;Neu16]. Teil des proaktiven Managements von Anforderungsänderungen ist daher die Erfassung von Unsicherheiten.…”

“…Je Unsicherheitsart können spezifische Maßnahmen zur Identifikation von Unsicherheiten eingeleitet werden. Eine Übersicht von epistemischen Unsicherheitsarten, spezifisch für den Kontext von Anforderungsänderungen, bietet [GPO21] (vgl. Abbildung 4-1).…”