From system goals to software architecture. Lamsweerde, A. v. Formal Methods for Software Architectures, 2003. bibtex*:Lamsweerdesystemgoalssoftware2003abstract bibtex Requirements and architecture are two essential inter-related products in the software lifecycle. Software architecture has long been recognized to have a profound impact on non-functional requirements about security, fault tolerance, performance, evolvability, and so forth. In spite of this, very few techniques are available to date for systematically building software architectures from functional and non-functional requirements so that such requirements are guaranteed by construction. The paper addresses this challenge and proposes a goal-oriented approach to architectural design based on the KAOS framework for modeling, specifying and analyzing requirements. After reviewing some global architectural decisions that are already involved in the requirements engineering process, we discuss our architecture derivation process. Software specifications are first derived from requirements. An abstract architectural draft is then derived from functional specifications. This draft is refined to meet domain-specific architectural constraints. The resulting architecture is then recursively refined to meet the various non-functional goals modelled and analyzed during the requirements engineering process.
@article{lamsweerde_system_2003,
title = {From system goals to software architecture},
abstract = {Requirements and architecture are two essential inter-related products in the software lifecycle. Software architecture has long been recognized to have a profound impact on non-functional requirements about security, fault tolerance, performance, evolvability, and so forth. In spite of this, very few techniques are available to date for systematically building software architectures from functional and non-functional requirements so that such requirements are guaranteed by construction. The paper addresses this challenge and proposes a goal-oriented approach to architectural design based on the KAOS framework for modeling, specifying and analyzing requirements. After reviewing some global architectural decisions that are already involved in the requirements engineering process, we discuss our architecture derivation process. Software specifications are first derived from requirements. An abstract architectural draft is then derived from functional specifications. This draft is refined to meet domain-specific architectural constraints. The resulting architecture is then recursively refined to meet the various non-functional goals modelled and analyzed during the requirements engineering process.},
journal = {Formal Methods for Software Architectures},
author = {Lamsweerde, Axel van},
year = {2003},
note = {bibtex*:Lamsweerdesystemgoalssoftware2003},
keywords = {arquitetura de software, engenharia de requisito, modelagem KAOS, ⛔ No DOI found, 🔍No DOI found},
pages = {1 -- 19},
}
Downloads: 0
{"_id":"B4XJyohA9LtrmZ3pt","bibbaseid":"lamsweerde-fromsystemgoalstosoftwarearchitecture-2003","author_short":["Lamsweerde, A. v."],"bibdata":{"bibtype":"article","type":"article","title":"From system goals to software architecture","abstract":"Requirements and architecture are two essential inter-related products in the software lifecycle. Software architecture has long been recognized to have a profound impact on non-functional requirements about security, fault tolerance, performance, evolvability, and so forth. In spite of this, very few techniques are available to date for systematically building software architectures from functional and non-functional requirements so that such requirements are guaranteed by construction. The paper addresses this challenge and proposes a goal-oriented approach to architectural design based on the KAOS framework for modeling, specifying and analyzing requirements. After reviewing some global architectural decisions that are already involved in the requirements engineering process, we discuss our architecture derivation process. Software specifications are first derived from requirements. An abstract architectural draft is then derived from functional specifications. This draft is refined to meet domain-specific architectural constraints. The resulting architecture is then recursively refined to meet the various non-functional goals modelled and analyzed during the requirements engineering process.","journal":"Formal Methods for Software Architectures","author":[{"propositions":[],"lastnames":["Lamsweerde"],"firstnames":["Axel","van"],"suffixes":[]}],"year":"2003","note":"bibtex*:Lamsweerdesystemgoalssoftware2003","keywords":"arquitetura de software, engenharia de requisito, modelagem KAOS, ⛔ No DOI found, 🔍No DOI found","pages":"1 – 19","bibtex":"@article{lamsweerde_system_2003,\n\ttitle = {From system goals to software architecture},\n\tabstract = {Requirements and architecture are two essential inter-related products in the software lifecycle. Software architecture has long been recognized to have a profound impact on non-functional requirements about security, fault tolerance, performance, evolvability, and so forth. In spite of this, very few techniques are available to date for systematically building software architectures from functional and non-functional requirements so that such requirements are guaranteed by construction. The paper addresses this challenge and proposes a goal-oriented approach to architectural design based on the KAOS framework for modeling, specifying and analyzing requirements. After reviewing some global architectural decisions that are already involved in the requirements engineering process, we discuss our architecture derivation process. Software specifications are first derived from requirements. An abstract architectural draft is then derived from functional specifications. This draft is refined to meet domain-specific architectural constraints. The resulting architecture is then recursively refined to meet the various non-functional goals modelled and analyzed during the requirements engineering process.},\n\tjournal = {Formal Methods for Software Architectures},\n\tauthor = {Lamsweerde, Axel van},\n\tyear = {2003},\n\tnote = {bibtex*:Lamsweerdesystemgoalssoftware2003},\n\tkeywords = {arquitetura de software, engenharia de requisito, modelagem KAOS, ⛔ No DOI found, 🔍No DOI found},\n\tpages = {1 -- 19},\n}\n\n","author_short":["Lamsweerde, A. v."],"key":"lamsweerde_system_2003","id":"lamsweerde_system_2003","bibbaseid":"lamsweerde-fromsystemgoalstosoftwarearchitecture-2003","role":"author","urls":{},"keyword":["arquitetura de software","engenharia de requisito","modelagem KAOS","⛔ No DOI found","🔍No DOI found"],"metadata":{"authorlinks":{}},"html":""},"bibtype":"article","biburl":"https://bibbase.org/zotero/brunocpt","dataSources":["9N7FyBLqJ5Q2Suqzs"],"keywords":["arquitetura de software","engenharia de requisito","modelagem kaos","⛔ no doi found","🔍no doi found"],"search_terms":["system","goals","software","architecture","lamsweerde"],"title":"From system goals to software architecture","year":2003}