{"title":"非功能需求的领域独立本体","authors":"G. Dobson, S. Hall, G. Kotonya","doi":"10.1109/ICEBE.2007.76","DOIUrl":null,"url":null,"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.","PeriodicalId":184487,"journal":{"name":"IEEE International Conference on e-Business Engineering (ICEBE'07)","volume":"131 4 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2007-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"35","resultStr":"{\"title\":\"A Domain-Independent Ontology for Non-Functional Requirements\",\"authors\":\"G. Dobson, S. Hall, G. Kotonya\",\"doi\":\"10.1109/ICEBE.2007.76\",\"DOIUrl\":null,\"url\":null,\"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.\",\"PeriodicalId\":184487,\"journal\":{\"name\":\"IEEE International Conference on e-Business Engineering (ICEBE'07)\",\"volume\":\"131 4 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2007-10-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"35\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"IEEE International Conference on e-Business Engineering (ICEBE'07)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICEBE.2007.76\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE International Conference on e-Business Engineering (ICEBE'07)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICEBE.2007.76","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A Domain-Independent Ontology for Non-Functional Requirements
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.