Premium
4.4.1 A Hybrid Requirements Capture Process
Author(s) -
Daniels Jesse,
Botta Rick,
Bahill Terry
Publication year - 2005
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2005.tb00697.x
Subject(s) - non functional requirement , requirements analysis , statement (logic) , computer science , functional requirement , software requirements specification , system requirements specification , requirements engineering , requirement , requirements elicitation , requirements management , software engineering , non functional testing , systems engineering , functional specification , system requirements , process (computing) , software requirements , software , software system , software design , software development , engineering , programming language , software construction , political science , law , operating system
Systems engineers traditionally produce a system requirements specification containing shall‐statement requirements. However, the rapid adoption of use case modeling for capturing functional requirements in the software community has caused systems engineers to examine the utility of use case models for capturing system‐level functional requirements. A transition from traditional shall‐statement requirements to use case modeling has raised some issues and questions. This paper advocates a unified requirements engineering method in which use case modeling and traditional shall‐statement requirements are applied together to effectively express both functional and non‐functional requirements for complex, hierarchical systems. This paper also presents a practical method for extracting requirements from the use case text to produce a robust requirements specification.