Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Information and Software Technology
Software architecting without requirements knowledge and experience: What are the repercussions?
Journal of Systems and Software
Can Patterns Improve i* Modeling? Two Exploratory Studies
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
Analyzing trust in technology strategies
Proceedings of the 2006 International Conference on Privacy, Security and Trust: Bridge the Gap Between PST Technologies and Business Services
Experimental comparison of attack trees and misuse cases for security threat identification
Information and Software Technology
Conceptual Modeling: Foundations and Applications
Techniques for merging views of software processes
Graph transformations and model-driven engineering
Interactive Analysis of Agent-Goal Models in Enterprise Modeling
International Journal of Information System Modeling and Design
International Journal of Information Systems and Social Change
Checking feasible completeness of domain models with natural language queries
APCCM '12 Proceedings of the Eighth Asia-Pacific Conference on Conceptual Modelling - Volume 130
PLANT: A pattern language for transforming scenarios into requirements models
International Journal of Human-Computer Studies
Hi-index | 0.00 |
The use of viewpoints has long been proposed as a technique to structure evolving requirements models. In theory, viewpoints should provide better stakeholder traceability, and the ability to discover important requirements by comparing viewpoints. However, this theory has never been tested empirically. This paper reports on an exploratory case study of a key hypothesis of the viewpoints theory, namely that by creating separate viewpoint models to represent different stakeholder contributions, and explicitly merging them, important hidden requirements can be discovered. The case study compared two modelling teams using the i*notation to capture requirements for new webbased counselling services for a large charitable organisation. One team used viewpoints; the other did not. The conclusions include that viewpoint merging improves the understanding of the problem domain, but is very time consuming. The process of merging was more important than the merged product. The study also indicates a need for better model management tools, as both teams encountered dif- ficulty in managing large, evolving models.