A Survey of Information Requirements Analysis Techniques
ACM Computing Surveys (CSUR)
Studying programmer behavior experimentally: the problems of proper methodology
Communications of the ACM
Experimental investigations of the utility of detailed flowcharts in programming
Communications of the ACM
Softwear Reliability
Executable requirements for embedded systems
ICSE '81 Proceedings of the 5th international conference on Software engineering
Prototyping as a tool in the specification of user requirements
ICSE '81 Proceedings of the 5th international conference on Software engineering
DAS - an automated system to support design analysis
ICSE '78 Proceedings of the 3rd international conference on Software engineering
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Specifications a key to effective software development
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Prototyping techniques for different problem contexts
CHI '89 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Formal Approach to Scenario Analysis
IEEE Software
A scenario-based methodology for conducting requirements elicitation
ACM SIGSOFT Software Engineering Notes
A formal approach to scenario integration
Annals of Software Engineering
Making use of scenarios: a field study of conceptual design
International Journal of Human-Computer Studies
Requirements tools: phase I in a software development methodology
ACM SIGSOFT Software Engineering Notes
PLANT: A pattern language for transforming scenarios into requirements models
International Journal of Human-Computer Studies
Hi-index | 0.00 |
The three major facets of software requirements engineering are: (1) requirements identification, (2) requirements analysis, and (3) requirements communication. Much research addresses the latter two aspects, but few practical approaches exist for addressing the first one. Hence, system requirements remains the most critical and problemprone area of system development. There is thus an urgent need for a methodology which helps a user identify requirements and realize potential impacts, in a timely manner.The objectives of this research are: (1) develop a methodology (and accompanying tools) to aid users in identifying requirements before building a system, and (2) evaluate the effectiveness of the methodology (and tools) in actual use.The novel approach of this research is an attempt to capture the conceptual system as visualized by the user, by use of operational examples ("scenarios"). By means of simulation and man-machine interface techniques, the scenarios may serve as a "quick and dirty" prototype of the intended system, providing the means for requirements analysis and validation, and for communicating the real intent of the requirements. It is anticipated that the methodology can be extended to fully support the concept of step-wise refinement and continuing system validation.