Premium
1.2.1 Use Cases and Non‐functional Requirements Presented in Compact System Description A3s
Author(s) -
Nilsen Anders Fuglesteg,
Muller Gerrit
Publication year - 2014
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2014.tb03130.x
Subject(s) - functional requirement , non functional requirement , use case diagram , stakeholder , computer science , requirements analysis , system requirements , system requirements specification , requirements management , systems engineering , diagram , systems design , software requirements specification , software engineering , unified modeling language , engineering , database , programming language , class diagram , software system , software , software design , software development , software construction , public relations , political science , operating system
Translating stakeholder requirements into system requirements is important for guiding the detailed design towards a solution that meets the stakeholder needs. The methods typically used today in the company do not sufficiently capture performance requirements. We combined the functional and non‐functional aspects of a system in one diagram. We used compact system description A3s to communicate the diagram and other system information to stakeholders. We showed that presenting functions through use cases, annotated with non‐functional requirements, help capture the performance aspect of the system, and that compact system description A3s communicate the most important aspect of the system well.