Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
Deriving operational software specifications from system goals
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Deriving Tabular Event-Based Specifications from Goal-Oriented Requirements Models
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Goal-Oriented Requirements Enginering: A Roundtrip from Research to Practice
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Scenarios, goals, and state machines: a win-win partnership for model synthesis
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
| Hi-index | 0.00 |
During the process of eliciting requirements, it is important to be aware and constantly focused on the organizational goal like mission, vision, brand promise etc. It is important to understand purpose, goals and intentions as necessary conditions for successful design and development of products (for product companies). Losing focus on the organizational goal can lead to a disastrous situation especially where the customer completely relies on the supplier for full product development. This paper discusses a goal-oriented model that uses brand requirements to underpin the incoming requirements at every stage of development i.e. conceptualization, eliciting requirements, execution, and testing. The end result is a win-win relationship with the internal customer as well as the external customer.