6. Conclusion
Conceptual modeling is still relevant for specifying "what the system should do" in precise terms that enable it to be realized. But it is insufficient to reason about "what the system should be used for" and to help the stakeholders in an IS project to understand their wishes, desires and needs, and the implications of these on the requirements imposed on the IS.
The article introduced a goal-directed requirements engineering approach that explores the "why" question in a systematic and participative way, leading to a consensual requirements document validated by all stakeholders and serving as a starting point for IS conceptualization.
The approach was illustrated by a case study of hotel room reservations.
The goals-based approach presented in the article can be applied in contexts other than IE: as a "means/ends"...
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Software technologies and System architectures
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Conclusion
Bibliography
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference