Analysis of several common software architectures and characteristics

Software architecture is a collection of structured elements that have some form, that is, artifacts, including processing artifacts, data artifacts, and connectivity artifacts.

The processing component is responsible for processing the data, the data component is the information being processed, and the infiltration virtual connection component connects the different parts of the architecture.

This definition, which focuses on distinguishing between processing components, data components, and cluster combustion components, is largely maintained in other definitions and methods.

Due to some common characteristics of software systems, this model can be transferred between multiple systems, especially in systems with similar quality attributes and functional requirements, and can promote system-level reuse of large-scale software.

To put it simply, architecture refers to the elements that make up a system and the relationships between them, and is a metaphysical thing.

The architecture framework is similar to that of the mountain, which is more pragmatic for the architecture, and sometimes it is already a semi-finished product, which can be customized or secondary development on this basis.

Design patterns are different from architectures (which are not even comparable, although somewhat confusing by definition) because they are more generic and are common solutions and lessons learned for design.

For example, you can say that we are talking about the architecture of a system, but we can't just talk about the design patterns of a system, and at most we can only say how many design patterns and their variants are used.

The concept is as follows: A software architecture is a collection of structured elements with a certain form, that is, a set of artifacts, including processing artifacts, data artifacts, and connection artifacts. Processing components are responsible for processing data, data components are information being processed, and connecting components connect different parts of the architecture.

This definition, which focuses on distinguishing between processing components, data components, and connection components, is largely maintained in other definitions and methods.

Compared with "software architecture", the term "software architecture" is mostly used in the field of academic research, and "software architecture" is mostly used in the field of engineering practice, both of which are known by the foreign name of "software architecture", which is defined in the IEEE as "the basic organization of a system, including the various components, the relationship between the components and the environment, and the principles that guide its design and evolution." ”

If the research of software architecture only stays at the stage of non-formal block diagrams, it is difficult to meet the needs of further development.

To support architecture-based development, analysis and development tools with formal modeling notation and architecture descriptions are required.

From the perspective of the current situation of software architecture research, there has been a lot of progress in this field recently, among which the more representative is the Wright system proposed by Robert J A11en of Carnegiemellon University in the United States in l997.

Wright is a structured description language based on a formalized, abstract system model that provides a practical tool for describing and analyzing software architectures and structuring methods.

Wright's primary focus is on describing the structure, configuration, and methods of the system's software building blocks and Lien's bridging.

It uses an explicit, independent connection model as a way to interact, which allows the system to describe the abstract behavior of the system in terms of logical predicate symbology, rather than relying on specific system instances.

The system can also determine the consistency and completeness of the system's structural specifications through a set of static checks.

From the analysis of these characteristics, the Wright system is indeed suitable for the description and analysis of large systems.