Building up and Exploiting AK assigment.pptx

document of education assigment for student

1. Adama Science and Technology University (ASTU) School of Electrical Engineering and Computing (SoEEC) Software Architecture and Design Assignment 1 Title: Building up and Exploiting Architectural Knowledge

2. 1. Introduction Architectural design, even well documented according to all the good recipes is only one small part of the A rchitectural Knowledge that is required to design a system. Bosch and others have pointed that design decisions, the tight set of interdependencies between them, and their mapping. the design and implementation downstream are also a key component of architectural knowledge

3. 2. Background Innovation is a quest into the unknown . T he definition of architectural innovation is either the improvement of existing parts or changing the connections between the components. Architecture innovation happens when improved efficiency of part is more the concern rather changing the system architecture directly. There is considerable evidence that technical innovations involve modest changes to the existing technology

4. 3. Problem of Statement The reason behind Exploiting Architectural Knowledge is :- design decision and other forces that drive the decisions usually are not explicitly captured. They are tacit knowledge Essential for solution but not documented.

5. . Research Objectives What knowledge does an architect use/need? What types of assumptions are made in an Architecture? Which types of decision are important to capture explicitly? How to share AK in a distributed setting How to describe AK How to manage AK

6. 5. Methodology We referred textbooks given by instructor and various documents in internet also from different research methodology options, we used the following:- Reviewing documents and Records Existing data

7. 6. Analysis Result We have two types of knowledge:- 1. Explicit :-stated clearly in detail . E.g. words, number, and specific formula, manual 2. Tacit :-understood and implemented without being stated . E.g. subjective insight, institution, experience and emotion We use cases to combine this Architectural knowledge

8. 7. Findings Capturing design rationale has been a key research topic for many years, leading to interesting models, tools and methods, but it has failed to transfer to practice. Why? This is mostly because the burden to capture assumptions and decisions outweighs largely the immediate benefits that the architect may draw , all what we may do with architectural knowledge could follow the same route as design rationale has done over the years nice ideas, but not practical

9. 8. Conclusion In this paper, we discuss the notion of architectural knowledge If we had a repository of architectural knowledge for a system , what would it ideally contain how would we build it, and exploit it in practice?