Software Architecture View

Who is the software architecture designed?

1.
Designed for users.

This includes not only functional requirements, but also non-functional requirements, such as performance, stability, and robustness.

2.
Designed for customers.

Users and customers are sometimes different. It can be understood as follows: customers pay for it and users are direct users of software products.

We need to fully consider the characteristics of our customers. Business objectives, time requirements, budget restrictions, and integration requirements.

3.
Designed for developers.

Focus on the non-functional requirements of software.

4.
Designed for management personnel.

Provide reference for the project manager to develop the project plan, manage the project division, and assess the project progress.

What is the software architecture view?

An architecture view is a simplified description of a system from a certain perspective or a certain point. The description covers a specific aspect of the system and omits entities unrelated to this aspect.

The reason for the emergence of the software architecture view: the idea of division.

On the one hand, for communication consideration, if the architect does not adopt the view mode, it will be difficult to communicate with different personnel.

On the other hand, software architecture is a very complex thing. In architecture, many concepts and technologies are involved, and methods that are conducive to the software architecture view make the problem clearer and simpler.

Traditionally, the architecture can be divided into two parts: physical architecture and logical architecture.

The logical architecture of the software specifies the logical elements of the software system and the relationship between these logical elements.

Task of the logical architecture of the software:

1.
Recognition function.

2.
Plan the function block interface.

3.
Define the usage relationship and mechanism between functions.

The Responsibility Division decision in the logical architecture is reflected in the division decisions of layers, subsystems and modules. It provides practical guidance for detailed design and programming implementation from a static perspective, with decomposition, collaboration is required. The logical architecture also specifies the interaction interfaces and mechanisms between different logical units.

Common interaction mechanisms include method calls, RMI-based remote method calls, and message mechanisms.

The physical architecture of the software specifies the physical elements of the component system, the relationships between these physical elements, and their policies for deploying them to the hardware. The physical architecture reflects the organization of the software system during dynamic operation.

The physical architecture specifies how the software system uses processes and threads to complete the expected concurrent processing, what passive objects will be called by the active objects of process threads for processing, and what the interaction mechanism is, this provides a dynamic view of the work objectives for detailed design and programming.

References

Software Architecture Design