2000Unpublished venueOpen access

Requirements engineering

Bashar Nuseibeh, Steve Easterbrook

Open full text 1,820 citations

Abstract

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.

Open-access reader

About this research paper

What this paper is about

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.

Why it matters

OpenAlex reports 1820 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

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 concepts: Computer science

Related papers

Back to paper searchBrowse research topicsOriginal source
Requirements engineering — Research Paper | ScholarLens