Deriving Goals from a Use-Case Based Requirements Specification |
| |
Authors: | Annie I Antón Ryan A Carter Aldo Dagnino John H Dempster Devon F Siege |
| |
Affiliation: | (1) College of Engineering, North Carolina State University, Raleigh, North Carolina, USA, US;(2) Asea Brown Boveri Inc., Power T&D Company, Raleigh, North Carolina, USA, US |
| |
Abstract: | Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their
richness and informality. In some instances, for example when a project’s budget or schedule time is reduced at short notice,
practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification.
Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves
focused attention. We describe our experiences during a goal-driven requirements analysis effort for an electronic commerce
application. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability,
inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks.
We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality
systems during goal and scenario analysis. |
| |
Keywords: | :Goal-based requirements engineering – Requirements specification – Use cases |
本文献已被 SpringerLink 等数据库收录! |
|