Requirements management using SysML
(→Introduction) |
(→Introduction) |
||
| Line 6: | Line 6: | ||
Managing the complexity of the highly interdependent requirements in developing projects is crucial for projects success... | Managing the complexity of the highly interdependent requirements in developing projects is crucial for projects success... | ||
'''The document-based-approach:''' | '''The document-based-approach:''' | ||
| − | In most organisations the approach to managing requirements is the so called document based approach; here requirements are categorised in a hieratic specification tree, and documented as text files. Part from being a rigorous proces that can be difficult to maintain, this approach has a fundamental flaw the deeply affects management decision making on a broad level. The problem with the document-based-approach arises as it can not depict the complex reality of the relations between components. Instead the relations are depicted in a | + | In most organisations the approach to managing requirements is the so called document based approach; here requirements are categorised in a hieratic specification tree, and documented as text files. Part from being a rigorous proces that can be difficult to maintain, this approach has a fundamental flaw the deeply affects management decision making on a broad level. The problem with the document-based-approach arises as it can not depict the complex reality of the relations between components. Instead the relations are depicted in a framing decided by the system engineer responsible for designing and maintaining the system. The drives a range of issues related to managements decision making, as certain perspectives of the system are not visble: making for traceability issues I.e. when tracing a customer requirements all the way down to the rationale behind decisions of low system level components This in turn makes it difficult to asses change impact in projects, and delivering with the right quality, .. leading to reduced quality and higher uncertainty.... The complexity and probability of damage drastically increases with the size of projects and width of program, as more complicated networks of relation arises between technology, stakeholders... |
Instead Project management offices should shift is approach to a '''model-based approach'''... | Instead Project management offices should shift is approach to a '''model-based approach'''... | ||
Revision as of 15:32, 22 February 2019
Abstract
Managing the complexity of the highly interdependent requirements in developing projects is crucial for projects success. Object-oriented modeling languages such as SysML provides a framework to model these relationships, making for a tool to comprehend complexity, comply with quality, and being responsive to change in requirements. These strong abilities arises from the nature of object oriented modeling, allowing traceability and... In this article, a brief introduction to SysML and requirements management will be introduced laying the basis for further discussion about how it can be taken in use in managing complex development projects. Three views will particularly be .... , affecting the project manager ... harnesing complexity, reducing risk and as a means of communication.
Introduction
Managing the complexity of the highly interdependent requirements in developing projects is crucial for projects success... The document-based-approach: In most organisations the approach to managing requirements is the so called document based approach; here requirements are categorised in a hieratic specification tree, and documented as text files. Part from being a rigorous proces that can be difficult to maintain, this approach has a fundamental flaw the deeply affects management decision making on a broad level. The problem with the document-based-approach arises as it can not depict the complex reality of the relations between components. Instead the relations are depicted in a framing decided by the system engineer responsible for designing and maintaining the system. The drives a range of issues related to managements decision making, as certain perspectives of the system are not visble: making for traceability issues I.e. when tracing a customer requirements all the way down to the rationale behind decisions of low system level components This in turn makes it difficult to asses change impact in projects, and delivering with the right quality, .. leading to reduced quality and higher uncertainty.... The complexity and probability of damage drastically increases with the size of projects and width of program, as more complicated networks of relation arises between technology, stakeholders...
Instead Project management offices should shift is approach to a model-based approach...
