Towards modelling and reasoning support for early-phase requirements engineering

@inproceedings{yu97a, abstract = {Requirements are usually understood as stating what a system is supposed to do, as apposed to how it should do it. However, understanding the organizational context and rationales (the “Whys”) that lead up to systems requirements can be just as important for the ongoing success of the system. Requirements modelling techniques can be used to help deal with the knowledge and reasoning needed in this earlier phase of requirements engineering. However most existing requirements techniques are intended more for the later phase of requirements engineering, which focuses on completeness, consistency, and automated verification of requirements. In contrast, the early phase aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives. This paper argues, therefore, that a different kind of modelling and reasoning support is needed for the early phase. An outline of the i* framework is given as an example of a step in this direction. Meeting scheduling is used as a domain example}, address = {Annapolis, Maryland}, author = {Yu, Eric S. }, booktitle = {International Symposium on Requirements Engineering}, citeulike-article-id = {166377}, journal = {-}, keywords = {1406, i-star, model, requirements, software}, pages = {226--235}, posted-at = {2005-04-21 20:23:33}, priority = {0}, title = {Towards modelling and reasoning support for early-phase requirements engineering}, url = {http://ieeexplore.ieee.org/xpls/abs\_all.jsp?arnumber=566873}, year = {1997} }

TY - CONF ID - yu97a L3 - citeulike-article-id:166377 TI - Towards modelling and reasoning support for early-phase requirements engineering T2 - International Symposium on Requirements Engineering JF - - SP - 226 EP - 235 AD - Annapolis, Maryland N2 - Requirements are usually understood as stating what a system is supposed to do, as apposed to how it should do it. However, understanding the organizational context and rationales (the “Whys”) that lead up to systems requirements can be just as important for the ongoing success of the system. Requirements modelling techniques can be used to help deal with the knowledge and reasoning needed in this earlier phase of requirements engineering. However most existing requirements techniques are intended more for the later phase of requirements engineering, which focuses on completeness, consistency, and automated verification of requirements. In contrast, the early phase aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives. This paper argues, therefore, that a different kind of modelling and reasoning support is needed for the early phase. An outline of the i* framework is given as an example of a step in this direction. Meeting scheduling is used as a domain example KW - 1406 KW - i-star KW - model KW - requirements KW - software AU - Yu, Eric PY - 1997/// UR - http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=566873 ER -