Viewpoint analysis: a case study
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Patterns of software: tales from the software community
Patterns of software: tales from the software community
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
SanFrancisco Design Patterns: blueprints for business software
SanFrancisco Design Patterns: blueprints for business software
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Pattern Languages of Program Design 4
Pattern Languages of Program Design 4
Game Design Theory and Practice
Game Design Theory and Practice
Enhancing a Requirements Baseline with Scenarios
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Software Process Reuse in an Industrial Setting
ICSR '96 Proceedings of the 4th International Conference on Software Reuse
Hi-index | 0.00 |
The requirements elicitation is essential to the success of software development projects. Many papers have been written that promulgate specific elicitation methods. However, none have yet modeled elicitation in a way that makes clear the critical role played by situational knowledge. This paper presents a unified model of the requirements elicitation process that emphasizes the applying the concepts of patterns as it transforms the current state of the business requirements and the situation to an improved understanding of the requirements and, potentially, a modified situation. One meta-model of requirements elicitation, selection of an appropriate elicitation technique, is also captured in the model. The values of this model are: (a) an improved understanding of elicitation helps analysts improve their elicitation efforts and (b) as we improve our ability to perform elicitation, we improve the likelihood that systems we create will meet their intended customers' needs. These patterns are elicited from coordination and transaction costs economics theories and they are validated through a wide variety of relevant situation.