Software Architecture (Final Review)

Article directory

Software Architecture

Software Architecture

Introduction to Software Architecture

Software crisis refers to a series of serious problems encountered during the development and maintenance of computer software.

Symptoms of software crisis :

Causes of software crisis :

Basic elements of software engineering : processes, methods, and tools.

Software Engineering Process (Five Activities):

Software Engineering Methods (Four Methods):

Software architecture composition (core model) : components + connectors + constraints

Architectural style : A conventional pattern used to describe the organization of systems in a specific application domain, reflecting the structural and semantic properties common to many systems in the domain.

Software framework : A software framework is the skeleton of an application system customized by developers. It is a reusable design of the entire or part of the system. It consists of a set of abstract components and the interaction between component instances.

Design pattern : describes some solutions to common problems in the software system design process. It is usually a widely recognized practice and knowledge summarized from a large number of successful practices.

The relationship between framework and architecture :

The architecture is presented as a design specification, while the framework is "half-finished" software.
The purpose of architecture is to guide the development of software systems, while the purpose of framework is to design reuse.

The relationship between frameworks and design patterns :

The framework gives the architecture of the entire application; while the design pattern gives
the solution to a single design problem and can be applied in different applications or frameworks.
For example: an online game can be developed based on NetEase's Pomelo framework, which is a high-performance, distributed game server framework based on
Node.js; when implementing a certain animation function,
the observer mode may be used to implement automated notification updates.
The goal of the design pattern is to improve the code structure and improve the structural quality of the program; the framework emphasizes the
reusability of the design and the scalability of the system to shorten the development cycle and improve the quality of development.

Component : It is a reusable software structural unit with a certain function, representing the main computing elements and data storage in the system.

Component acquisition :

Three schools of components :

CORBA: Object Management Group OMG's Common Object Request Broker Architecture CORBA.

OMG: Object Management Group
CORBA: Common Object Request Broker Architecture
EJB: EJB specification developed by Sun.
EJB: Enterprise Java Bean
DCOM: Distributed Component Object Model DCOM developed by Microsoft.
DCOM: Distributed Component Object Model

Component management :

Component description.
Classification and organization of components.
Personnel and authority management.

Component description is an abstract description of the essence of the component by the model, which mainly provides the basis for the production and reuse of components. From a management perspective, it is also necessary to describe the component, such as: implementation method, implementation body, comments, producer, production date, size, price, version and associated components. Together with the component model, they form a complete description of the component. describe.

Component classification and organization :

Keyword Taxonomy.
Facet classification.
Hypertext organization method.

Component management: personnel and authority management : including five types of users, namely registered users, public users, component submitters, general system administrators and super system administrators.

Component reuse :

Retrieve and extract components.
Understand and evaluate components.
Modify components.
Component assembly.

Component reuse: retrieval and extraction of components :

Keyword-based search.
Facet search method.
Hypertext search method.
Other search methods.

Component Reuse: Understanding and Evaluating Components :

The function and behavior of the component.
Relevant domain knowledge.
Adaptability constraints and exceptions.
Predictable modifications and modification methods.

Component reuse: component assembly :

Function-based assembly technology.
Data-based assembly technology.
Object-oriented assembly technology.

Connection : It is a way to establish and maintain behavioral associations and information transmission between components.

Connector : represents the interaction between components and realizes the connection between components.

The goals of software architecture : effectiveness, simplicity, reusability, and scalability.

Software architecture modeling

The Kruchten4+1 view model describes the software architecture from 5 different perspectives including logical view, process view, physical view, development view and scene view . Each view only cares about one aspect of the system. Only the combination of five views can reflect the entire content of the system's software architecture.

• Logical view : When using object-oriented design methods, the logical view is the object model.

• Process view : Describes the concurrency and synchronization aspects of the system's design.

• Physical view : Describes the mapping relationship between software and hardware, reflecting the distribution design of the system.

• Development view : Describes the static organization of software in the development environment.

Rational 4+1 view model :

、

use case view

•The use case view contains use cases that describe the behavior of the system as seen by users, analysts, and test engineers.

•The system architecture can be determined based on the view.

•UML:

Static aspect: use case diagram description.