Software Architecture - Exam Outline

xiaoxiao2021-04-11  171

1. View type and style (P195)

There are three types of views:

1) Block View Class: In this view, the element is an implementing unit, called a module. The module reflects a method based on code-based consideration. Here, the relationship between the modules includes IS A, IS Part of, and Depends ON.

2) Components and connector views (or C & C views): The element is a component, which is the main unit of calculation, and the connector is a communication means between the members. It is primarily a link relationship between components and connectors in the C & C view class.

3) Distribution View Class: Allocation view class represents the software element and one or more software being manufactured, or the relationship between the running external environment.

2. View has the meaning, function, side focus

A view is a set of system elements and their relationships.

3. Research causes SA

The importance of software architecture (P12)

1) Role in risk assumption and early design

1. Exchange of risk bearers work SA

An application software system, especially a large-scale software system involves numerous risk assumers: customers - generally the investors of the software system; system architect - designers for the software system as the overall architecture Programmer - Specific programming; tester - the function and performance of the test system reaches the design goal, these different risks are responsible for different characteristics of the application system architecture, respectively; customer care is currently designed Can the overall framework not exceed the budget, complete the person on time; if the user relationship application system is available, whether it is reliable; the project manager pays attention to the architect's architect specification, controllable and makes the team independent, coordinated Target realize. Therefore, the software architecture is called each risk bearer to express its own needs, and negotiate find a reasonable development plan to study objects, which is a means of exchange of risk bearers. Whether it is a risk of risk, it is not sufficient, which will cause direct and serious impact on the success or failure of the system.

2. Is the product SA for early design decisions

The software architecture reflects the earliest design decisions made to the system. The correctness of these early decisions is the most difficult, and these decisions are also the most difficult to change, and their impact is also the most profound.

3. Influence of application systems SA

The software architecture restricts the quality properties of the application system, so it has the dest firm influence on the declaration cycle of the entire software. The software architecture directly affects the following subsequent activities such as system design, development, maintenance, upgrade, evolution. Because, "In large software systems, the quality attribute is more implementation of system structure and functional division, and no longer relying only on the algorithm or data structure selected."

2) The role in each stage of software development

1. Project planning phase

Before initially determine the overall framework of the project, you must first examine the environment of the software system running, such as whether it is running under WAN for WAN? Is there a ready-made component or tool? Is there a heritage software system that is integrated into a new system?

2. Demand analysis phase

. . .

3. Project design phase

. . .

4. Project implementation phase

. . .

5. Test and system evaluation phase

. . .

6. Maintenance and upgrade phase

. . .

3) is a high-level multiplexing of system analysis and design

The software architecture has a bridge between demand and code; this bridge provides an abstract description (or model), the architecture reveals some properties while hiding another property . It works on software development:

1. Easy to understand 2. Multiplex

3. Construct

4. Evolution

5. Analyze

6. Manage

7. communicate with

4. Tactical method

5. Common modeling method

6. Various styles and features

7. What is a software architecture, the focus of the business cycle

8. Quality attribute, risk bearer, concept of evaluation process


New Post(0)