{"title":"作为架构知识的业务目标","authors":"P. Clements, L. Bass","doi":"10.1145/1833335.1833337","DOIUrl":null,"url":null,"abstract":"In this paper we argue that business goals constitute an important type of architectural knowledge. Quality attributes are often the primary drivers (shaping forces) behind an architecture, but quality attributes derive from an organization's business goals, whether the organization is the one developing or acquiring the software system. We introduce a seven-part scenario format for capturing and articulating business goals, and a set of \"standard\" business goal categories. Finally, we introduce a method to help an architect elicit business goals and tie them to quality attribute requirements, adding to the architect's store of architectural knowledge.","PeriodicalId":325791,"journal":{"name":"Sharing and Reusing Architectural Knowledge","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2010-05-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"5","resultStr":"{\"title\":\"Business goals as architectural knowledge\",\"authors\":\"P. Clements, L. Bass\",\"doi\":\"10.1145/1833335.1833337\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"In this paper we argue that business goals constitute an important type of architectural knowledge. Quality attributes are often the primary drivers (shaping forces) behind an architecture, but quality attributes derive from an organization's business goals, whether the organization is the one developing or acquiring the software system. We introduce a seven-part scenario format for capturing and articulating business goals, and a set of \\\"standard\\\" business goal categories. Finally, we introduce a method to help an architect elicit business goals and tie them to quality attribute requirements, adding to the architect's store of architectural knowledge.\",\"PeriodicalId\":325791,\"journal\":{\"name\":\"Sharing and Reusing Architectural Knowledge\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2010-05-02\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"5\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Sharing and Reusing Architectural Knowledge\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1833335.1833337\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Sharing and Reusing Architectural Knowledge","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1833335.1833337","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
In this paper we argue that business goals constitute an important type of architectural knowledge. Quality attributes are often the primary drivers (shaping forces) behind an architecture, but quality attributes derive from an organization's business goals, whether the organization is the one developing or acquiring the software system. We introduce a seven-part scenario format for capturing and articulating business goals, and a set of "standard" business goal categories. Finally, we introduce a method to help an architect elicit business goals and tie them to quality attribute requirements, adding to the architect's store of architectural knowledge.