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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
