In my thesis I have conducted different case studies to validate the use of the viewpoint analyzer, a tool based on a production system, to help the analysis of viewpoints. Using different descriptions written in VWPL the tool would identify "candidates" for wrong information, inconsistencies and missing information.
The case studies did also pointed out that by having an agenda for discussing discrepancies would increase the overall knowledge about the topic at hand.
The paper below provides a case study that sheds more light of the importance on this agenda for discussion in the process of having better conceptual models.
Proceedings of the 13th IEEE International Conference on
Requirements Engineering, 2005
Do viewpoints lead to better conceptual models? An exploratory case study, by
Easterbrook, S. Yu, E. Aranda, J. Yuntian Fan Horkoff, J. Leica, M. Qadir, R.A.
Using the Concept of Viewpoints in Requirements Engineering
Welcome
Almost 20 years ago I wrote a thesis on the use of Viewpoints in Requirements Elicitation. It was one of the first works that explored the idea of using different viewpoints for better understanding software requirements. It stands on the shoulders of two giants: SADT and Core, but it went further as to use automation in the process of using different viewpoints and perspectives to elicit more sound requirements.
I am making the original text available. I will also use this space as to gather work related to the topic.
Please fell free to comment. I will moderate the comments, and may comment on some of them. The intention of this space is to foster debate as well as to serve as a reference on the topic.
I am making the original text available. I will also use this space as to gather work related to the topic.
Please fell free to comment. I will moderate the comments, and may comment on some of them. The intention of this space is to foster debate as well as to serve as a reference on the topic.
No comments:
Post a Comment