Knowledge-based support for requirements engineering
Information and Software Technology
Object-oriented software engineering
Object-oriented software engineering
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Using UML: Software Engineering with Objects and Rules
Using UML: Software Engineering with Objects and Rules
An Integrated Environment for Requirements Engineering
IEEE Software
Requirements Engineering: The Emerging Wisdom
IEEE Software
Identifying Quality-Requirement Conflicts
IEEE Software
An Object-Oriented Tool for Tracing Requirements
IEEE Software
Classification of research efforts in requirements engineering
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
| Hi-index | 0.00 |
The least attention been paid to requirements engineering resulted in the software development effort facing myriad problems, ranging from incomplete requirements to inconsistent design and improper implementation. We look at one phase of requirements engineering - requirements elicitation. We propose a methodology that allows the requirements elicitor to bring forth the requirements in a methodical manner. It is domain specific and addresses information systems. We have borrowed certain concepts from system simulation - event, activity and process - in developing the methodology. Our methodology provides a mechanism by which the myriad operations of any information system are drawn forth and elicited appropriately using a two-model approach, viz. hierarchical-process model. No assumption, however, is made as to how the analysis or design need be ultimately performed beyond the requirements elicitation phase. We use the illustrative example of a University's information system to explain the use and efficacy of the methodology.