Premium
1.4.1 Practical SysML Applications: A Method to Describe the Problem Space
Author(s) -
Lempia David,
Jorgensen Ray
Publication year - 2011
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2011.tb01187.x
Subject(s) - set (abstract data type) , traceability , computer science , systems modeling language , key (lock) , unified modeling language , systems engineering , separation of concerns , space (punctuation) , software engineering , management science , engineering , programming language , software , computer security , operating system
Customers are looking for solutions to problems that they are having. The problem description methodology starts with the group of customers called the stakeholders and ends with a set of functions that need to be implemented to satisfy the needs of each of the stakeholders. Building the wrong feature or building features that are not used are costly forms of waste in engineering development. Likewise, building exactly what the customer wants and delivering the most valuable functions early is the key to project success. There are a number of SysML and UML methodologies published. These methodologies generally lead the engineer from requirements to analysis to structural design and back to behaviors. Because of the methodology, it is easy to mix the solution ideas in with the problem definition. Adding solution ideas too early constrains the possible solutions that can be utilized when the set of problems is investigated. Also, these existing methodologies yield poor traceability and throw‐away diagrams. This problem description methodology describes a logical evolution of thought, a reduced simplified set of diagrams, traceable requirements, and diagrams that easily evolve into implementation or test.