Requirements management using SysML

Revision as of 17:06, 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

When starting an engineering project, ... Managing the complexity of the highly interdependent requirements in developing projects is crucial for projects success...

Document-based or model-based

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 the Project management office should shift the requirements management approach to a model-based approach. In a model-based-approach, ....... The products of the model-based approach depicts the messy structures ... with fewer.. as requiremetns can be inherited and derived from eachother.

A good mental model for understanding the dynamics of the model-based system is picturing a mountain. The mountain itself is the model "object" with all its different trees, animals, snow. The different view that can be extracted from the model to understand to system is then photographs of the moutain from different lokations. Two photos may show partly similar elements, but they will depict different truths about the moutain itself.

Affecting project and program management

References

150211142014_2_Friedentahl_-_A_Practical_Guide_to_SysML_2nd