Architectural Knowledge
by
Patricia Lago
—
last modified
Apr 26, 2012 10:35
—
filed under:
KnowledgeModel
Definitions
| Term: Architectural Knowledge |
Domain: Cross-cutting issues | ||||
|---|---|---|---|---|---|
| Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
| D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
Architectural Knowledge (AK) is defined as the
integrated representation of the software architecture of a
software-intensive system (or a family of systems), the architectural
design decisions, and the external context/environment [Lago2006]. This definition
explains the original version which defines AK = Design + design
decisions [Kruchten2006]. {SYN:AK} |
||||
Competencies
- VUA: Software architecture; http://www.cs.vu.nl/en/sec/imse;
Hans van Vliet, Patricia Lago, Qing Gu
References
- [Lago2006] Lago, P. & Avgeriou, P. First workshop on sharing and reusing architectural knowledge SIGSOFT Softw. Eng. Notes, ACM Press, 2006, 31, 32-36
- [Kruchten2006] Kruchten, P., Lago, P., van Vliet, H.: Building up and Reasoning about Architectural Knowledge. In: C. Hofmeister, I. Crnkovic, R. Reussner (eds.) Quality of Software Architectures, Proceedings 2nd International Conference, pp. 43–58. Springer, LNCS 4214 (2006)
