Software Architecture in Action, Oquendo F., Leite J., Batista T., 2016

Software Architecture in Action, Oquendo F., Leite J., Batista T., 2016.
 
   This book is designed for teaching software architecture modeling techniques to both graduate and undergraduate students, in order to prepare them to architecting complex software-intensive systems. It is also appealing for practitioners and members of a software development team such as architects, designers, programmers, project managers, since it is structured around practical modeling approaches spanning different roles in software development.




Introducing SysML for SysADL.
SysML was jointly defined by the Object Management Group (OMG) and the International Council on Systems Engineering (INCOSE). It is a general-purpose modeling language for systems engineering, including in particular softwareintensive systems engineering. It supports the specification, analysis, design, verification, and validation with a diagrammatic notation that is more expressive and flexible than UML while being smaller.

SysML. by being a generalization of UML with a smaller notation, is easier to learn than UML and, of course, very easy to learn for those who already know UML. As shown in Lig. 1.1, it provides nine kinds of diagram, of which seven are borrowed from UML. Of these seven, four are used as they are (package diagram, use case diagram, sequence diagram, and state machine diagram) and three were extended (block definition diagram generalizes class diagram; internal block diagram generalizes composite structure diagram, and activity diagram was extended with more general features). The two new diagrams provided by SysML are the requirement diagram for expressing the definitions and dependencies of requirements and the parametria diagram mostly for defining quantitative constraints.

Contents.
Part I Fundamentals.
1 Introduction to Software Architecture.
1.1 The Concept of Software Architecture.
1.2 Language for Modeling Software Architecture.
1.2.1 Why Conceiving SysADL.
1.2.2 Introducing SysML for SysADL.
1.2.3 SysADL as a Specialization of SysML for Architecture Modeling.
1.3 Designing Software Architecture with SysADL.
1.3.1 Describing Software Architectures.
1.3.2 Designing Quality-Based Software Architectures.
1.3.3 Designing Style-Based Software Architectures.
1.3.4 Textually Representing Software Architectures.
1.4 Running Case Study to Illustrate Software Architecture.
1.5 Summary.
Further Reading.
References.
2 Viewpoints for Describing Software Architectures.
2.1 The Definition of Software Architecture.
2.2 Software Architecture Description.
2.3 Concepts for Describing Software Architecture.
2.4 Architectural Viewpoints and Views.
2.4.1 Architectural Viewpoints.
2.4.2 Architectural Views.
2.5 Summary.
Further Reading.
Reference.
3 Eliciting Requirements of Software Architectures.
3.1 Introduction.
3.2 The Concept of Requirement.
3.3 Requirement Constructs.
3.4 Dependencies Between Requirements.
3.5 Requirements Diagram.
3.6 Applying Requirement Constructs.
3.7 Summary.
Further Reading.
4 Specifying the Structure of Software Architectures.
4.1 Introduction.
4.2 Structural Viewpoint and Views.
4.2.1 Structural Viewpoint.
4.2.2 Structural Views.
4.3 Structural Constructs.
4.3.1 Component.
4.3.2 Ports.
4.3.3 Value Types.
4.3.4 Components with Ports Typed by Value Types.
4.3.5 Connector.
4.3.6 Configuration.
4.3.7 Composite Components.
4.4 Diagrams for Structural Views.
4.4.1 Block Definition Diagrams.
4.4.2 Internal Block Diagrams.
4.5 Describing the Architecture from the Structural Viewpoint.
4.6 Summary.
Further Reading.
5 Specifying Behavior of Software Architectures.
5.1 Introduction.
5.2 Behavioral Viewpoint and Views.
5.2.1 Behavioral Viewpoint.
5.2.2 Behavioral Views.
5.3 Behavioral Constructs.
5.3.1 Activity.
5.3.2 Action.
5.3.3 Equations in the Action Definition.
5.3.4 Relating Definition of Activities and Actions.
5.3.5 Relating Components and Connectors with Activities and Actions.
5.4 Diagrams for Behavioral Views.
5.4.1 Block Definition Diagrams.
5.4.2 Activity Diagrams.
5.4.3 Parametric Diagrams.
5.5 Relating Structural and Behavioral Viewpoints.
5.6 Describing the Architecture from the Behavioral Viewpoint.
5.7 Summary.
Further Reading.
6 Specifying Executable Software Architectures.
6.1 Introduction.
6.2 Executable Viewpoint and Views.
6.2.1 Executable Viewpoint.
6.2.2 Executable Views.
6.3 Executable Constructs.
6.3.1 Executable.
6.3.2 Action Language.
6.4 Summary.
Further Reading.
Reference.
7 Executing Software Architectures.
7.1 Introduction.
7.2 Executing an Architecture.
7.2.1 Executing Components.
7.2.2 Executing Connectors and Delegations.
7.2.3 Executing Configurations.
7.3 Executing Activities.
7.3.1 The Semantics of Activity Elements.
7.3.2 Executing an Activity.
7.4 Executing the RTC System Example.
7.5 Summary.
Further Reading.
Part II Quality-Based Architectures.
8 Introduction to Quality-Based Architectures.
8.1 What Is a Quality.
8.2 What Is Quality-Based Architectures.
8.3 Analysing Quality-Based Architectures.
8.4 Quality Attributes: Modifiability, Scalability, and Fault Tolerance.
8.5 Summary.
Further Reading.
9 Designing Modifiability in Software Architectures.
9.1 Introduction.
9.2 Expressing Modifiability Using Software Architecture Concepts.
9.2.1 Modifiability Causes and Effects.
9.2.2 Modifiability Quality Attributes.
9.2.3 A Classification of Modifiability Effects.
9.2.4 Examples of the Add Primitive.
9.3 Modifiability Tactics.
9.3.1 Using Modifiability Tactics.
9.4 Analysing Modifiability in the RTC System.
9.4.1 RTC System Requirements.
9.4.2 RTC System—Causes.
9.4.3 Analysing the Ripple Effect in ARCH1.
9.4.4 Design a New Architecture: ARCH2.
9.4.5 Analysing the Ripple Effects in ARCH2.
9.4.6 Comparing Modifiability in ARCH1 and ARCH2.
9.5 Summary.
Further Reading.
Reference.
10 Designing Scalability in Software Architectures.
10.1 Introduction.
10.2 Scalability Causes and Effects.
10.3 Scalability Quality Attribute.
10.4 Scalability Tactics.
10.5 Applying the Scalability Tactics.
10.5.1 The Component Definitions of ARCH2 and ARCH3.
10.5.2 The Configuration of ARCH2 and ARCH3.
10.5.3 The Configuration of RoomTemperatureControllerCP.
10.5.4 The Definition of CompositeMonitorCFD.
10.5.5 The AllTemperaturesCN Connector in ARCH3.
10.6 Scalability Analysis.
10.6.1 RTC System Requirements.
10.6.2 RTC System—Causes.
10.6.3 Analyzing the Ripple Effect.
10.7 Summary.
Further Reading.
11 Designing Fault Tolerance in Software Architectures.
11.1 Introduction.
11.2 Fault Tolerance Causes and Effects.
11.3 Fault Tolerance Quality Attributes.
11.4 Fault Tolerance Tactics.
11.5 Applying Fault Tolerance Tactics.
11.5.1 The Configuration of ARCH3 and ARCH4.
11.5.2 The HeartbeaterCP Component.
11.6 Fault Tolerance Analysis.
11.6.1 RTC System Requirements.
11.6.2 RTC System—Causes.
11.6.3 Analyzing the Ripple Effect.
11.7 Summary.
Further Reading.
Part III Style-Based Architectures.
12 Introduction to Style-Based Architectures.
12.1 What Is an Architectural Style.
12.2 What Is a Style-Based Architecture.
12.3 Architectural Styles.
12.4 Summary.
Further Reading.
13 Pipe-Filter Architectural Style.
13.1 Conceptual Overview.
13.2 Pipe-Filter Structural Viewpoint.
13.3 Pipe-Filter Behavioral Viewpoint.
13.4 The Pipeline Substyle.
13.5 Summary.
Further Reading.
14 Client Server Architectural Style.
14.1 Conceptual Overview.
14.2 An Example of Client–Server in RTC System.
14.3 Client–Server Structural Viewpoint.
14.4 Client–Server Behavioral Viewpoint.
14.5 Summary.
Further Reading.
15 Feedback Control Loop Architectural Style.
15.1 Conceptual Overview.
15.2 Feedback Control Loop Structural Viewpoint.
15.3 Feedback Control Loop Behavioral Viewpoint.
15.4 Summary.
Further Reading.
16 Blackboard Architectural Style.
16.1 Conceptual Overview.
16.2 Blackboard Structural Viewpoint.
16.3 Blackboard Behavioral Viewpoint.
16.4 Tuple Space.
16.5 An Example of Blackboard in RTC System.
16.6 Summary.
Further Reading.
Part IV Textual Description of Architectures.
17 Textually Representing Software Architectures.
17.1 Introduction.
17.2 Textual Notation.
17.2.1 Properties and Data.
17.2.2 Components and Ports.
17.2.3 Connectors.
17.2.4 Compositions and Architecture.
17.2.5 Activities.
17.2.6 Executable Advanced Examples.
17.2.7 Protocols.
17.2.8 Actions.
17.2.9 Constraints.
17.2.10 Executables.
17.2.11 Executable Advanced Examples.
17.3 Summing up.
17.4 Summary.
Further Reading.
Glossary.



Бесплатно скачать электронную книгу в удобном формате, смотреть и читать:
Скачать книгу Software Architecture in Action, Oquendo F., Leite J., Batista T., 2016 - fileskachat.com, быстрое и бесплатное скачивание.

Скачать pdf
Ниже можно купить эту книгу, если она есть в продаже, и похожие книги по лучшей цене со скидкой с доставкой по всей России.Купить книги


Скачать - pdf - Яндекс.Диск.




Теги: учебник по информатике :: информатика :: компьютеры :: Oquendo :: Leite :: Batista