Designing object-oriented software
Designing object-oriented software
Software engineering, the software process and their support
Software Engineering Journal - Special issue on software process and its support
Inquiry-Based Requirements Analysis
IEEE Software
A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification
IEEE Transactions on Software Engineering
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Requirements envisaging by utilizing scenarios
Requirements envisaging by utilizing scenarios
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
A client oriented requirements baseline
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Enhancing a Requirements Baseline with Scenarios
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
An active hypertext model for system requirements
IWSSD '93 Proceedings of the 7th international workshop on Software specification and design
Non-functional requirements: from elicitation to modelling languages
Proceedings of the 24th International Conference on Software Engineering
Scenario evolution in requirements elicitation processes: scenario pattern and framework approach
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Scenario support for effective requirements
Information and Software Technology
| Hi-index | 0.00 |
This work reports on a framework for scenario evolution. We have studied, based on a laboratory case study, the evolution of scenarios from elicitation to coding, thus using the requirements baseline in a full cycle. Considering our observations of over a hundred and fifty scenarios we discovered a series of relationships and operations that occurred during the evolution. Our framework is a contribution to better understand scenario evolution and to help the tractability and identification of those actions belonging to the environment and those shared with the software.