A Domain-Independent Ontology for Non-Functional Requirements Export

@proceedings{citeulike:3379282, abstract = {Despite considerable research on ontologies for representing requirements models (and metamodels), little progress has been made in using ontologies to represent non-functional requirements. Non-functional requirements define the overall qualities of the resulting system. Because they are restrictions on system services, non-functional requirements are often of critical importance, and functional requirements may need to be sacrificed to meet them. However, because of their diverse nature, non-functional requirements are often expressed in non-standard domain-specific ways. This paper describes a nonfunctional requirements ontology that can be used to structure and express constraints as part of quality of service specification. The approach is illustrated using a small case-study.}, author = {Dobson, G. and Hall, S. and Kotonya, G.}, booktitle = {e-Business Engineering, 2007. ICEBE 2007. IEEE International Conference on}, citeulike-article-id = {3379282}, citeulike-linkout-0 = {http://dx.doi.org/10.1109/ICEBE.2007.76}, citeulike-linkout-1 = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=4402149}, doi = {10.1109/ICEBE.2007.76}, journal = {e-Business Engineering, 2007. ICEBE 2007. IEEE International Conference on}, keywords = {non-functional, semantic\_web}, pages = {563--566}, posted-at = {2008-10-06 12:04:16}, priority = {4}, title = {A Domain-Independent Ontology for Non-Functional Requirements}, url = {http://dx.doi.org/10.1109/ICEBE.2007.76}, year = {2007} }

TY - CONF ID - citeulike:3379282 L3 - citeulike-article-id:3379282 N2 - Despite considerable research on ontologies for representing requirements models (and metamodels), little progress has been made in using ontologies to represent non-functional requirements. Non-functional requirements define the overall qualities of the resulting system. Because they are restrictions on system services, non-functional requirements are often of critical importance, and functional requirements may need to be sacrificed to meet them. However, because of their diverse nature, non-functional requirements are often expressed in non-standard domain-specific ways. This paper describes a nonfunctional requirements ontology that can be used to structure and express constraints as part of quality of service specification. The approach is illustrated using a small case-study. JF - e-Business Engineering, 2007. ICEBE 2007. IEEE International Conference on EP - 566 TI - A Domain-Independent Ontology for Non-Functional Requirements T2 - e-Business Engineering, 2007. ICEBE 2007. IEEE International Conference on SP - 563 KW - non-functional KW - semantic_web AU - Dobson, G AU - Hall, S AU - Kotonya, G PY - 2007/// UR - http://dx.doi.org/10.1109/ICEBE.2007.76 ER -