Shulou(Shulou.com)06/03 Report--

Opening instructions

As it is my own learning summary and experience of these technologies, mistakes are inevitable. With the mentality of technical exchange, they are published now, so I hope you can give us more advice. this can benefit some people and correct my wrong views, so as to improve with you!

What on earth is software architecture?

Software architecture can be simply described as a combination, interaction, and inheritance relationship between a series of components. Of course, such an explanation is basically acceptable to everyone. But in our opinion, this statement is a bit too abstract.

Software architecture has this standard definition, which refers to the standard of ANSI/IEEE. Software architecture can be understood as the system that plays a decisive role in the implementation and deployment of software-intensive systems.

The key point in software architecture is that it should meet the goals of project stakeholders and is of course functionally subdivided into functional and non-functional requirements.

Software architecture has a certain particularity, architecture design must be determined at the initial stage of development, and architecture design, as a key decision, must be determined in advance.

In fact, the software architecture is mainly to meet the goals of project stakeholders, if it can not meet the goals of project stakeholders, then this architecture solution will not work. The following figure shows the direct relationship between the system, architecture and project stakeholders as defined in the ANSI/IEEE standard.

At the beginning, it has been introduced that the expression tools of system architecture such as UML and Relation Rose,UML have basically become international standards.

UML class diagram: mainly describes the relationship between classes.

Use case diagram: describes the usage scenario.

Component diagram: used to describe reusable parts of the system. And it is easy to see the corresponding relationship between components and binaries.

Through the UML tool, we can describe the system architecture from different angles at a deeper level. Hold on to its core.

For the verification of software architecture, there is no good way to automatically verify whether the software architecture can achieve the goals of project stakeholders, only through multiple levels of testing in a variety of ways.

For example, through unit testing to verify a single function, integration testing to evaluate the compatibility of the system, acceptance testing to verify user satisfaction, whether the program provides the necessary functions.

In addition to the UML modeling tool, there is also IBM's famous Relation Rose. Here is an overview of the view mode that the tool has:

Architecture of the system

It can be said that no system is inseparable in the process of software system architecture. the more agile the system development method is, the more space is reserved for developers to implement the architecture.

The process by which the system architect decomposes the system ends up with a detailed design specification for the developer. Of course, the content and format of the detailed design specification also depends on the development method.

What is the architecture?

Most of the architecture is reflected in decisions that are difficult to change or expensive to change. But in the end, someone needs to make a decision.

The system analyst analyzes what the system does and how the architect designs to do it.

The architect is the link between requirements and specification.

The responsibility of the architect: the architect should be involved in the whole process of development. It includes analysis of requirements and architecture design, implementation, testing, inheritance and deployment.

According to the definition of ISO, an architect is defined as the person, team, or organization responsible for the architecture of the system.

Microsoft divides the system architecture into the following:

1. Enterprise architect.

2. Basic architect.

3. Specific technical architect.

4. Solution architect.

Finally, some rules in the process of software development are summarized.

1. Adding manpower for a project that is behind schedule will only make the project further behind schedule.

2. The complexity of the program will continue to increase until the maintenance staff feel powerless.

3. Architects and developers write programs differently. if architects build according to the way of developers, it will only become a failure in history.

A preview of the next article.

Architecture Design of UML

How to carry on the modeling through the UML tool, through the different angle analysis, obtains the core design.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.