This paper describes a Goal Centric approach for effectively maintaining critical system qualities such as security, performance, and usability throughout the lifetime of a software system. In Goal Centric Traceability (GCT) non-functional requirements and their interdependencies are modeled as softgoals in a Softgoal Interdependency Graph (SIG). A probabilistic network model is then used to dynamically retrieve links between classes affected by a functional change and elements within the SIG. These links enable developers to identify potentially impacted goals; to analyze the level of impact on those goals; to make informed decisions concerning the implementation of the proposed change; and finally to develop appropriate risk mitigating strategies. This paper also reports experimental results for the link retrieval and illustrates the GCT process through an example of a change applied to a road management system.
%0 Conference Paper
%1 cleland05icse
%A Cleland-Huang, Jane
%A Settimi, Raffaella
%A BenKhadra, Oussama
%A Berezhanskaya, Eugenia
%A Christina, Selvia
%B International Conference on Software Engineering
%C St. Louis, MO, USA
%D 2005
%I ACM
%K goal requirements traceability
%P 362--371
%R http://doi.acm.org/10.1145/1062455.1062525
%T Goal-centric traceability for managing non-functional requirements
%U http://portal.acm.org/citation.cfm?id=1062525
%X This paper describes a Goal Centric approach for effectively maintaining critical system qualities such as security, performance, and usability throughout the lifetime of a software system. In Goal Centric Traceability (GCT) non-functional requirements and their interdependencies are modeled as softgoals in a Softgoal Interdependency Graph (SIG). A probabilistic network model is then used to dynamically retrieve links between classes affected by a functional change and elements within the SIG. These links enable developers to identify potentially impacted goals; to analyze the level of impact on those goals; to make informed decisions concerning the implementation of the proposed change; and finally to develop appropriate risk mitigating strategies. This paper also reports experimental results for the link retrieval and illustrates the GCT process through an example of a change applied to a road management system.
@inproceedings{cleland05icse,
abstract = {This paper describes a Goal Centric approach for effectively maintaining critical system qualities such as security, performance, and usability throughout the lifetime of a software system. In Goal Centric Traceability (GCT) non-functional requirements and their interdependencies are modeled as softgoals in a Softgoal Interdependency Graph (SIG). A probabilistic network model is then used to dynamically retrieve links between classes affected by a functional change and elements within the SIG. These links enable developers to identify potentially impacted goals; to analyze the level of impact on those goals; to make informed decisions concerning the implementation of the proposed change; and finally to develop appropriate risk mitigating strategies. This paper also reports experimental results for the link retrieval and illustrates the GCT process through an example of a change applied to a road management system.},
added-at = {2008-01-22T21:41:57.000+0100},
address = {St. Louis, MO, USA},
author = {Cleland-Huang, Jane and Settimi, Raffaella and BenKhadra, Oussama and Berezhanskaya, Eugenia and Christina, Selvia},
biburl = {https://www.bibsonomy.org/bibtex/2e95c38a270786371143f04568243089a/neilernst},
booktitle = {International Conference on Software Engineering},
doi = {http://doi.acm.org/10.1145/1062455.1062525},
interhash = {1961d265a667fa9f05719982daeee4f0},
intrahash = {e95c38a270786371143f04568243089a},
keywords = {goal requirements traceability},
pages = {362--371},
publisher = {ACM},
timestamp = {2008-01-22T21:41:57.000+0100},
title = {Goal-centric traceability for managing non-functional requirements},
url = {http://portal.acm.org/citation.cfm?id=1062525},
year = 2005
}