Premium
A scenario‐based approach for requirements engineering: Experience in a telecommunication software development project
Author(s) -
Kaindl Hermann
Publication year - 2005
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.20030
Subject(s) - requirements engineering , software engineering , computer science , metamodeling , requirements analysis , systems engineering , requirement , software requirements specification , non functional requirement , requirements elicitation , context (archaeology) , software requirements , model driven architecture , requirements management , domain (mathematical analysis) , system requirements specification , software development , software , engineering , software design , programming language , software construction , paleontology , mathematical analysis , mathematics , biology
Scenarios have been studied theoretically, and they have been successfully applied, e.g., in requirements engineering. Still, requirements engineers using scenarios in practice are facing real‐world challenges. Especially, the fit of scenarios in the larger context of requirements engineering is an issue. So, for effective and efficient application of scenario‐based approaches in real‐world practice more experience will have to be gained and reported. We report on experience of scenario‐based requirements engineering for a real‐world telecommunication software development project. Scenarios were represented in this project by use of SDL (Specification and Description Language) diagrams rather than narratives in natural language. Still, the SDL diagrams were integrated with a hypertextual representation in natural language of functional requirements for the system to be built. They were also linked to a large domain model of telecommunication concepts built in the course of this project. All this modeling was guided by employing the metamodel of this scenario‐based approach for requirements engineering. © 2005 Wiley Periodicals, Inc. Syst Eng 8: 197–210, 2005