Key points are not available for this paper at this time.
Better 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.
Nuseibeh et al. (Mon,) studied this question.