non-functional requirementsproblem domain modelingrequirements elicitationrequirements engineeringsoftware architecture
Figures from the paper
Abstract (AI)
Key Research PointersBetter modelling and analysis of problem domains, as opposed to the behaviour of s oflwa re.Development of richer models for capturing and analysing non-functional requirements.Bridging the gap between requirements elicitation approaches based on contextual enquiry and more formal specification and analysis techniques.Better understanding of the impact of software architectural choices on the prioritisation and evolution of requirements.Reuse of requirements models to facilitate the development of system families and the selection of COTS.Multi-disciplinary training for requirements practitioners.
Key Findings
1
A key priority is integrating contextual-enquiry elicitation approaches with formal requirements specification and analysis techniques.
2
It calls for richer models capable of representing and analyzing non-functional requirements.
3
Requirements-model reuse is identified as a means to support system-family development and COTS selection, alongside multidisciplinary practitioner training.
4
The agenda highlights the need to understand how software architecture choices affect requirements prioritization and evolution.
5
The research agenda emphasizes modeling and analyzing problem domains rather than focusing exclusively on software behavior.
Research Object
software requirements engineering processes and requirements models
Research Subject
modeling, analysis, elicitation, specification, prioritization, evolution, and reuse of functional and non-functional requirements
Publication Details
Publication Date
2000-05-01
Journal
Publisher
ISSN
Open access PDF
Access Type
Author Information
Download PDF
Subscribe to digest