Summary of basic concepts of software architecture

Source: Internet
Author: User

This course, like UML modeling and programming methodology, is a relatively high-level view of the entire software structure. Not a concern for algorithms, or language. If you are interested in becoming a software architect, you should take this course. Now I'm going to share with you the information I've compiled for this course.

Second, the noun explanation (each question 2 points, altogether 20 points)
1, b/s (interim)
A: Browser/server style, is a three-tier application structure of a way to implement.
Specific structure: Browser/web server/database server.

2. C/S (interim)
A: Customer/server style, based on the resource is not equal, and for sharing, and defines how the workstation connected to the server, to achieve data and applications distributed across multiple processing machines. The C/S architecture has three main components: database servers, client applications, and networks.

3, HMB
A: The software architecture style of the hierarchical message bus (hierarchical message bus-based style). The HMB style is based on hierarchical message bus, supports the distribution and concurrency of components, and communicates between components through messages.

4, DSSA
A: A domain-specific software architecture (domain specific software Architecture) is a standard software architecture that provides an organizational structure reference for a set of applications in a specific domain.

5. ADL (Interim)
A: The Software Architecture Description Language (Architecture Description Language) is a formal language that provides a specific syntax and framework for modeling the conceptual architecture of software, supported by the underlying semantic model.

6. XML
A: Extensible Markup Language (extensible Markup Language), XML is a standard language for data exchange and representation on the Internet, and is a meta-language (meta) that allows users to define their own markup.

7, ATAM
A: The Architecture Tradeoff Analysis method (Architecture tradeoff analytical methods), which is an architectural assessment of how much support the system uses or modifies the activity to determine the level of satisfaction that the architecture represents for the quality requirements represented by this scenario.

8. Web Service
A: Web services (Web service) is a new service-oriented architecture that defines a set of standard protocols for interface definitions, method invocations, Internet-based fabric registrations, and implementations of various applications.

9, MTTF
A: The average pre-expiration time (Mean hours to Failure) refers to the average time the software is working normally before it expires.

10. SOAP
A: The Simple Object Access Protocol (PROTOCOL), soap is an XML-based lightweight protocol for exchanging structured information in a loosely distributed environment, for a loose, The use of XML to exchange structured and typed information in a distributed environment provides a simple mechanism.

11. WSDL
A: Web Service Description Language (Web Services Description Language). Defines a set of XML-based grammars used to describe Web services as a collection of service access points that can be exchanged for messages.

12. UDDI
A: (Universal Description Discovery Integration) Unified description, Discovery, and integration protocols. is a Web-based distributed Web Services Information Registry Implementation Standard specification, but also contains a set of Access Protocol implementation standards, so that enterprises can register their own Web services, and let other enterprises can discover and access these Web services.

13, SAAM
A: (software Architecture analysis method) The software architecture methodology is the first software architecture analysis method that has been carefully designed and documented and widely used, originally designed to evaluate the architecture's modifiable nature.

14. MVC
Answer: (Model-view-controller style) model-View---controller style. It mainly deals with the problems faced in the development of software user interface. The MVC style divides interactive applications into 3 artifacts: views, models, and controllers, allowing multiple views to be built for a model.

15, Artifact-driven
A: Product-driven architecture design method extracts the architecture description from the product description of the method. Examples include the widely popular object-oriented analysis and design methods OMT and Oad.

16, Use-case-driven
A: The use case-driven architecture design approach is abstracted primarily from the use case export architecture. The unified process uses a case-driven approach to architecture design.

17, Domain-driven
A: Domain driven, architecture is derived from the domain model, and the domain model is developed in the domain analysis phase.

18, Pattern-driven
A: schema-driven, which derives the architecture abstraction from the schema

19. Component (Interim)
A: A component is a unit software that is semantically complete, grammatically correct, and has reusable value, and is a system that can be clearly identified during software reuse.

20. Connecting Parts (interim)
A: Connectors is an architectural building block that is used to build interactions between components and to dominate these interaction rules.

21. MTBF
A: (Mean time between Failure) mean no downtime, refers to the average working time between adjacent two failures, also known as the average fault interval, it reflects the quality of the product time, is to reflect the product in the specified time to maintain the function of a capability.

22, sensitive points
A: Refers to system model parameters that can change significantly due to changes in the architecture elements.

23. Trade-Offs
Answer: Architecture elements that are related to multiple sensitive points.

24. Direct scene
A: A direct scenario is a scenario that the current architecture can support without modification.

25. Indirect scenario
A: cannot be directly supported by the current architecture, in order to meet the indirect scenario, you need to make some kind of modification to the architecture.

26. Quality Attribute Utility tree
A: In the form of trees to show the refinement of quality attributes. The root is the utility, next is the quality attribute layer, then the next layer is the mass attribute specific description classification, the last layer is the concrete scene.

Iii. question and Answer question (40 points)
1. What kinds of component description models are there?
Answer: 3C model, reboot model, Jade Bird component model.

2. Understand and compare three methods of component classification: keyword taxonomy, faceted taxonomy, and hypertext organization methods, how are they organized? How do I retrieve artifacts in them? What are the pros and cons of each approach?
For:
(1) Keyword classification: is a simple component library organization method, the basic idea is: according to the result of domain analysis, the concept of the application domain according to the order from abstraction to specific decomposition into a tree or a non-loop graph structure;
How to retrieve: The system displays the key tree structure of the component library directly to the user in the graphical user interface, and the user searches for the necessary keywords and extracts the corresponding components through the hierarchical browsing of the tree structure;
The advantages are simple and easy to implement. The disadvantage is that there is no application value in some situations, because users often can't describe the desired component function or behavior with the keywords already in the building library, and the browsing of the library is easy to get lost.

(2) Faceted classification: The main idea originates from the library science, in the facet classification mechanism, defines several "faces" which are used to characterize the component features, each of which contains several concepts that describe the features of the component on the surface. Facets can describe the function of the component execution, the data being manipulated, the context of the application of the component, or any other characteristic;
How to retrieve: constructs the query, retrieves the component, sorts the component;
The advantage is that it is easy to find similar components. The disadvantage is that the query is more troublesome;

(3) Hypertext organization method: The main idea is that all components must be supplemented by detailed functions or behavior of the document; The important concepts or components appearing in the description are interconnected by means of mesh linking; the reader can jump to a document that contains related concepts or artifacts in the process of reading the document. The full-text retrieval system matches the text of the user-given keyword description document, and realizes the browse-type retrieval of the component;
How to retrieve: The user first gives one or several keywords, the system in the component of the description of the document for accurate or fuzzy syntax matching, after the successful match, to the user to list the corresponding construction instructions;
The advantage is that the hypertext organization method provides a friendly and direct multimedia way for constructing components and reusing components. Because the network structure is more free and loose, the hypertext organization method is easier to modify the structure of the component library than the first two methods. The disadvantage is that in some cases, it is difficult for users to select components correctly during Hypertext browsing.

3, understand the software architecture of the four stages of development.
For:
(1) "No Architecture" design stage: the development of the main use of assembly language, small scale;
(2) Embryonic stage: the main use of decoupling curing development technology;
(3) Primary stage: The main use of object-oriented development technology. Modeling systems from a variety of angles (e.g. UML);
(4) Advanced stage: This stage is marked by the "4+1" model proposed by Kruchten. The center of Software Development is to describe the high-level abstract type of system;

4, according to the definition of software architecture, what parts do you think the model of software architecture should consist of? Period
A: Software architecture is defined as artifacts, connectors, and constraints. The component is a prefabricated and reusable software part, is the basic computing unit or data storage unit of the composing architecture, and the connecting piece is also a prefabricated and reusable software part, the connecting unit between the components, and the relation between the component and the connection is described by the constraint. This allows the software architecture to be written: Architecture = component + Connector + constraint.

5, at least three kinds of classic software architecture style.
For:
Warehouse style and Blackboard style
The architecture of the warehouse style consists of two components: a central data structure and a collection of independent artifacts.
Blackboard architecture consists of three parts: knowledge source, blackboard data structure, controller
Blackboard Architecture is a specialization of the warehouse architecture, which facilitates the sharing of large amounts of data, and facilitates the expansion of shared blackboard data structure.
MVC style
Separates the model from the view and controller, allowing multiple views to be built for a model. It simplifies the system design and ensures the expansibility of the system by decomposing all aspects of the problem.
C2 style
Consists of two elements: the component and the connector. Components can implement application requirements and encapsulate the functionality of any complexity. The communication between all the components is realized by the asynchronous message exchange mechanism, which is mediated by the connection pieces.

6, try to analyze and compare B/s, two-tier C/A and three-layer, and points out their advantages and disadvantages.
A: Two layer C/s architecture will be applied in Split, the server is responsible for data management, the client to complete the interaction with the user task. Advantages:
(1) The C/S architecture has a powerful transaction processing ability of data manipulation, the model idea is simple, easy to understand and accept, (2) The change of software and hardware has great adaptability and flexibility, it is easy to expand and reduce the system;
(3) The large application processing tasks are distributed to many low-cost computers connected by the network, so as to save a lot of expenses;
Disadvantages:
(1) High development cost;
(2) Client programming is complex;
(3) The content and form of information is unitary;
(4) The user interface style is different, the use of miscellaneous difficult to promote;
(5) difficult to transplant software;
(6) Difficult to maintain and upgrade software;
(7) New technology can not be easily applied;

The three-layer CS was modified on top of the above, and an application server was added.
Advantages:
(1) to allow a reasonable division of three-layer structure of the function, can improve the system and software maintainability and scalability;
(2) with good upgradeability and openness;
(3) The application of the various layers can be developed in parallel, you can choose the most appropriate development language;
(4) laid a solid foundation for the strict safety management;

b/S style is an implementation of the above three-tier application structure, the specific structure is: Browser/web server/database server.
Advantages:
(1) software based on B/S architecture, system installation, modification and maintenance are all in the server-side solution;
(2) To provide the heterogeneous machine, heterogeneous network, heterogeneous application services online, networking;
Disadvantages:
(1) Lack of support ability of dynamic page, not integrated with effective database processing ability;
(2) In the data query and other response speed, is much lower than the C/s system structure;
(3) The system expansion ability is poor, the security is difficult to control;

7, please introduce the MVC style architecture, and explain the advantages and disadvantages of this style.
A: Model-view-controller style is often referred to as the MVC style, mainly dealing with the problems faced in the development of software user interface. Separate the model from the view, controller, allowing multiple views to be built for a model
Has the following advantages:
(1) The various aspects of the problem is divided into consideration, simplifying the system design, to ensure the scalability of the system;
(2) Changing the interface does not affect the application's functional core, making the system easy to evolve and develop, maintainability is good;
(3) Easy to change, even in the runtime to change, providing a good dynamic mechanism;
Cons: Mainly confined to application software in the area of user interface development.

8, in the orthogonal software architecture, what is the complete orthogonal structure? Is it necessary to strictly adhere to the orthogonal structure in practice? What are the advantages of using an orthogonal software architecture? Period
A: The structure is completely orthogonal if the clues are independent of each other, that is, there are no calls between the components in the different threads. In practice, it is not necessary to strictly adhere to the structure orthogonal.
Advantages:
(1) The structure is clear and easy to understand;
(2) Easy to modify, maintainability is strong;
(3) The portability is strong, the reuse granularity is big;


9. What is the difference between hierarchical system structure and message-based hierarchical system architecture?
A: Hierarchies organize systems hierarchically, and the idea is that in a hierarchy, each layer provides services to the upper layers and serves as a customer to the lower level. Benefits of tiered systems: support for system design based on an increasing degree of abstraction, support enhancements, and support for reuse. The disadvantage of layered systems is that not every system can be easily divided into layered patterns, even hierarchically, for performance reasons, but also to combine some low-level or advanced functions, it is difficult to find a suitable, right level abstract method.
The message bus is the system's connector, responsible for the dispatch of messages, delivery and filtering, and the return of processing results. Messages are the only way to communicate between artifacts. Since the components are connected via the bus, it is not required that each component has the same address space or be confined to a single machine, so this style can describe the distributed development system and the system of corba.dcom and EJB specification well.

10. What is the difference between the architecture description Language and the programming language?
A: ADL has the following capabilities in comparison to other languages:
(1) Construction Capacity: ADL can use small independent architectural elements to build large-scale software systems;
(2) Abstract Ability: ADL makes component and connector descriptions in software architecture can focus only on their abstract features, regardless of their specific implementation details;
(3) The ability to reuse: ADL makes components of software systems, connectors and even software architecture become reusable parts of software system development and design;
(4) The combination ability: ADL makes each system element that it describes has its own layout structure, this description layout structure characteristic makes the ADL to support the software system dynamic change combination;
(5) Heterogeneous ability: ADL allows multiple different architectures to describe the existence of associations;
(6) Analysis and reasoning ability: ADL allows a variety of different performance and functional reasoning analysis of the architecture it describes;

11. What are the seven architecture entities defined in Acme? What does the type and style of Acme mean?
A: Seven architecture entities: artifacts, connectors, systems, ports, roles, representations, and presentation mappings.
Architecture description An important capability is the ability to define a system's style or family. Style allows us to define domain-specific or application-specific design vocabulary, and how to use these vocabulary constraints, in Acme, designers can define three types, namely, attribute type, structure type and style.

12, understand the XML-based software Architecture description Language.
A: Due to the many advantages of XML in architecture description, different XML-based architecture description languages have been developed, such as Xadl 2.0, XBA, Xcoba.
XADL 2.0: Good extensibility, not a single language for describing a model, but a collection of model descriptions;
XBA: The application of XML to the description of the software architecture. Using the extensibility of XML, the existing ADL is described and defined.
Xcoba: Can dynamically reflect the system in the runtime architecture of relevant information, support the essence and evolution of the system, support component-based software development methods and the realization of communication between heterogeneous components;

13. The "4+1" view model of Krutchten is briefly introduced.
A: The Krutchten "4+i" view model includes logical views, development views, process views, physical views, and scene views from 5 different perspectives to describe the software architecture.
(1) The logical view mainly supports the functional requirements of the system, which is the service provided by the system to the end user;
(2) The development view should consider the internal requirements of software, such as the ease of software development, the reuse of software and the generality of software;
(3) The Process view focuses on the operating characteristics of the system, focusing on some non-functional requirements;
(4) Physical view mainly consider how to map software to hardware, solve the system topology, system installation, communication and other problems;
(5) The scene, through which the various views can be linked to describe how the different views of the component between the role;

14. What are the basic components of the design pattern? Please briefly describe each of its basic ingredients.
A: Four basic components of the design pattern: name, problem, solution, consequences. The name is usually used to describe a design problem, its solution and consequences, consisting of one or two words. Questions tell us when to use design patterns, explain problems, and their backgrounds. The solution is to describe the basic elements of the design, their relationships, their respective tasks, and their cooperation with each other. Consequences describe the results and tradeoffs after applying design patterns.

15. Why evaluate the software architecture? What are the aspects of evaluating the software architecture?
For:
Reason:
The software architecture reflects the most initial design decisions of the system, and for the same problem, the cost of correcting in the initial phase and the cost of correcting during the test or deployment phase are not an order of magnitude;
Assessment is the last chance to uncover hidden requirements and add them to the design;
Architecture is the center of the development process, and bad architecture can bring bad results;
Assessments are conducted in the following areas:
(1) Performance refers to the system's impact ability, that is, how long it takes to respond to an event, or the number of events that the system can handle in an event;
(2) Reliability is the basic ability of software system to maintain the functional characteristics of software system in the case of accidental or erroneous use in the face of application or system error;
(3) Availability is the percentage of time that the system can function normally;
(4) security refers to the ability of the system to provide services to legitimate users while preventing unauthorized users from using the attempt or denial of service;
(5) modifiable is the ability to quickly change the system at a higher performance cost;
(6) functionality is the ability of the system to accomplish the desired work;
(7) variability refers to the ability of an architecture to be expanded or changed to become a new system structure;
(8) integration refers to the degree to which the system can collaborate with other systems;
(9) Interoperability refers to the ability to interact with other environments or systems themselves;

16. What are the three main methods of software architecture evaluation? Please explain each of these methods briefly.
A: (1) Evaluation methods based on surveys or checklists: more flexible, can be used to evaluate multiple quality attributes, or at multiple stages of architecture design. However, since the results of the assessment are largely derived from the subjective assumptions of the evaluators, different evaluators may produce different or even different results, and the assessment of the level of familiarity with the field, and whether there is a wealth of relevant experience will be an important factor in the evaluation of the results;
(2) Scenario-based assessment: This architecture evaluation approach analyzes the degree to which the software architecture supports the scenario, i.e. the use of the system or the change in activity, to determine the level of satisfaction that the architecture represents for the quality requirements represented by the scenario;
(3) Measure-based assessment: involving three basic activities: first of all, we need to establish the mapping principle between quality attributes and metrics, that is, to determine how the quality attributes of the system are derived from the measurement results, and then obtain the measurement information from the software architecture document; Finally, some quality attributes of the system are deduced from the mapping principle. Measure-based assessment provides a more objective and quantifiable quality assessment;


17. What are the basic steps of the SAAM and Atam assessment methods?
Answer: Saam step:
Scene generation;
Architecture description;
The classification and priority of the scene are determined;
A separate assessment of the indirect scenario;
Assessment of the relevance of the scenario;
To form an overall assessment;

Atam steps:
Introduction Atam;
introduction of commercial motives;
Introduce the architecture;
Identification of the architecture method;
Generate mass attribute utility tree;
Analysis of the architecture approach;
Brainstorming and setting the scene priority;
Analysis of the architecture approach;
Provide evaluation results;

18. What are the core technologies of Web services, and how these technologies play a role in Web services?
A: The Web Service technology core is based on the standard of Extensible Markup Language XML. Includes soap, WSDL, and UDDI.
SOAP: The use of HTTP as the underlying communication protocol, RPC as a consistent call path, using XML as a data transmission format, allowing service providers and service requesters through the firewall in the Internet environment to interact;
WSDL: Defines a set of XML-based grammars used to describe Web services as a collection of service access points that can be exchanged for messages;
UDDI: Web-based distributed Web Services Information Registry Implementation Standard specification, but also contains a set of Access Protocol implementation standards, so that enterprises can register their own Web services, and let other enterprises can discover and access these Web services;

Four, look at the picture answer (30 points)
1, please according to P38 figure 3-5 to introduce the composition of the blackboard system.

For:
(1) Knowledge Source: A discrete piece of application-specific knowledge;
(2) Blackboard data structure: reflect the application to solve the state of the database;
(3) Controller: control (i.e. the call to knowledge source) is determined by the state of the blackboard;

2, please interpret HMB style component model according to P59 figure 3-26. Period

A: In the component model shown in Figure 3-26, the upper left side is the interface part of the component, a component can support many different interfaces, each interface defines a set of input and output messages, depicts the external services provided by the component and the required environmental services, reflecting the interaction between the component and the environment. The upper right is a component behavior characterized by a finite state automaton with output, which responds to the message based on the current state and may lead to a change of state, when the component receives the foreign message. Below is the definition of the internal structure of a composite member, which is made up of a simpler sub-component connected by a local message bus. The message bus provides a unified integration mechanism for the whole system and the components of each level.

3. Please interpret the properties and services of the message bus according to P60 figure 3-27. Period

A: Message Bus properties: Widget instance table, component-Message response registration form, Message Filter table. Services: Message registration, message dispatch, message delivery, message filtering. In the description of the graph, the component 1 registers the message of interest to the message bus, forms the component Message Response registration form, and the message bus locates the message to the corresponding responder according to the type of the message received and the component-Message response registration form, and is responsible for returning the processing result. When necessary, the message bus can also filter and block messages that are accepted if they are not messages that are of interest to the message bus.
The component is only interested in the message itself and does not care how the message is generated, and the issuer and receiver of the message do not have to know each other's situation. This makes the coupling degree between the components is low, the component reusability is good, and the component replacement is easier. In a system defined by a generic interconnect interface, the connection between the components is a fixed match between the requested service and the service provided, and in HMB, the component may cause changes in state after it responds to the incoming message. Therefore, a component may respond differently when it receives the same message in different states at different times.

4. According to P147 figure 5-2, the meta-model of architecture design method is introduced.

A: The meta-model is an abstraction of various architectural design models. The concept is represented by a rounded rectangle, the connection between the concepts is represented by a line, and a diamond symbol is used to denote the correlation between the four concepts.
Customer: Indicates those who are concerned with the architecture design of the system concerned personnel;
Requirements Specification: Describes the system requirements for the architecture to be developed;
Product: A description of a product that represents a method;
Solution Abstraction: Defines a conceptual representation of the substructure;
Architecture Description: Defines the specification of the architecture;
Domain knowledge: Used to denote the scope of knowledge used in solving a problem;

5. Please outline the steps of the architecture-based software development process according to P167 figure 6-1. and explain the need for each step? Or, what role do they play in the software life cycle?

A: This procedure consists of the following steps:
(1) Export architecture requirements: Architectural requirements are created by the development organization and are influenced by the technical environment and the personal experience of the architect. The output of this step is 3: Enumerate the functional requirements, enumerate the specific architecture requirements, enumerate the quality scene sets, and provide specific tests for the architecture requirements;
(2) Design architecture: An architecture designer makes some design decisions when developing an architecture, and then analyzes these design decisions by considering different architectural constructs and view diagrams. Architecture design is an iterative process that first makes certain decisions and analyzes them, then reconsider and re-decide until the design is closed;
(3) Documented architecture: Architecture documents are designed to support program designers and analysts. It is an effective tool for deepening communication between various system-related personnel and can derive architectural requirements from it. Creating and maintaining an architectural document is one of the key factors in the success of a long-term software architecture;
(4) Analysis of the architecture: identify potential risks, verify that the given design can handle the proposed quality requirements, the need for external evaluators to participate in order to ensure unbiased inspection, and ensure the credibility of the evaluation results;
(5) Implementing the architecture: when transforming an architecture into code, consider a variety of common software engineering and project management Knowledge: detailed design, coding implementation, testing, configuration management, etc.
(6) Maintenance architecture: For the architecture, good documentation, good release and good maintenance are all very important. In the absence of any aspect of activity, the architecture will inevitably deviate from its initial principles;

6, please according to P207 figure 8-1 analysis of service providers, service requesters and service registry three roles, and the workflow between them.

For:
Role:
(1) Service provider: publishes its own services and responds to requests for services;
(2) Service registry: Register published Web services, categorize them, and provide search services;
(3) Service requester: Use the service registry to find the required services, and then using the service;
Workflow: The service provider hosts a software module that can be accessed over the network, defines the service description of the Web services and publishes it to the service registry, and the service requester uses a find operation to retrieve the service description from the service registry, and then uses the service description to bind to the service provider and invoke the Web The services implement or interact with it.

7. Please refer to the specific work steps of UDDI according to P229 figure 8-11.

For:
(1) Software companies, standardization organizations, and programmers define how the enterprise plans to register in UDDI and begin publishing descriptive information about these rules to the UDDI registry. These rules are called technical models;
(2) The enterprise registers with the UDDI registry a description of the enterprise and the Web services it provides;
(3) The UDDI registry assigns each entity a unique identifier in the relevant program so that it can keep abreast of the current situation of all these entities;
(4) Other types of customer and business applications such as electronic trading sites and search engines use the UDDI registry to discover Web Services of interest to them;
(5) Other enterprises can call these services, convenient and rapid business application dynamic integration;


A Fill in the blanks (10 points)--Organize yourself
Component Description Model:
3 C model, reboot model, Bluebird building model.
Component Classification Method:
Keyword classification, faceted taxonomy, hypertext organization.
The history of software architecture development:
"No architecture" design stage, embryonic stage, primary stage, advanced stage.
Classic Software Architecture Style:
Pipe-filter style;
Data abstraction and object-oriented style;
An implicit invocation style based on events;
hierarchical system style;
Warehouse style and blackboard style;
MVC style;
Interpreter style;
C2 style;
Typical software Architecture Description Language:
Unicon
C2
Wright
Acme
XML-based Architecture description Language:
XADL 2.0
XBA
Xcoba
The "4+1" model consists of 5 views:
Logical view
Process View
Physical view
Development view
Scene
Basic components of the design pattern:
Schema name, problem, solution, consequences.
Architecture Design Methodology:
Product-driven approach;
Use case-driven approach;
Domain-driven approach;
mode-driven approach;
The software architecture evaluates the mass attributes of general concern:
Performance
Reliability
Availability of
Security
Modifiable
Functional performance
Variability
Integration of
Interoperability
The main ways to evaluate software architecture:
Assessment methods based on questionnaires or checklists;
Scenario-based evaluation method;
Variable-based evaluation method;
Software Architecture Definition:
Software architecture ={components, connectors, constraints}
The WEB services architecture is based on three types of roles:
Service providers, service registries, service requesters.
SOA (service-oriented architecture) is a Web services architecture with three roles: Service provider, service registry, and service requester.
3 C Model:
Concept: Concept
Content: Contents
Context: Contextual
Software Architecture Description Method: (interim)
Graphical representation tools
Intra-Module connection language
The system description language based on software component
Adl
Framework standard for Software architecture description


Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Summary of basic concepts of software architecture

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.