Premium
The hybrid process that combines traditional requirements and use cases
Author(s) -
Daniels Jesse,
Bahill Terry
Publication year - 2004
Publication title -
systems engineering
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.474
H-Index - 50
eISSN - 1520-6858
pISSN - 1098-1241
DOI - 10.1002/sys.20013
Subject(s) - non functional requirement , statement (logic) , requirements analysis , computer science , system requirements specification , functional requirement , requirements elicitation , software requirements specification , requirements management , requirements engineering , requirement , process (computing) , systems engineering , system requirements , non functional testing , software engineering , software , software system , software design , engineering , software development , programming language , software construction , political science , law , operating system
For many years systems engineers have produced traditional system requirements specifications containing shall‐statement requirements. 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 hybrid requirements process in which use case modeling and traditional shall‐statement requirements are applied together to effectively express both functional and nonfunctional 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. © 2004 Wiley Periodicals, Inc. Syst Eng 7: 303–319, 2004