E-Book, Englisch, 165 Seiten
Khalid Software Architecture for Business
1. Auflage 2019
ISBN: 978-3-030-13632-1
Verlag: Springer International Publishing
Format: PDF
Kopierschutz: 1 - PDF Watermark
E-Book, Englisch, 165 Seiten
ISBN: 978-3-030-13632-1
Verlag: Springer International Publishing
Format: PDF
Kopierschutz: 1 - PDF Watermark
This book illustrates the role of software architecture and its application in business. The author describes enterprise architecture along with business architecture to show the role of software architecture in both areas. The place of software architecture in business is outlined from many perspectives in this context. The book outlines quality attributes and how managers can use software architecture to build high quality products. Topics include business software architecture, dealing with qualities, achieving quality attributes, managing business qualities, software product line, Internet of Things (IOT), and Service Oriented Business Architecture. The book is intended to benefit students, researchers, software architects, and business architects. Provides quick and easy access to all the important aspects of software architecture in business;
Highlights a wide variety of concepts of software architecture in a straightforward manner, for students, practitioners, or architects;
Presents different applications of software architecture in business.
Dr. Lina Khalid received a master's degree in Computer Science in (2000) and a PhD. in Computer Science (2004) from The University of Technology, Iraq. Her academic experience includes working as an instructor in The University of Baghdad (1992-1995), an assistant professor at The University of Technology in Iraq (2001-2005), an assistant professor at Israa Private University in Jordan (2005-2007), and an assistant professor at Zarqa Private University in Jordan (2007-2015). Dr. Lina has taught classes in Software Engineering, Software Architecture, Software Design, Economic of Software, Software Verification and Validation, Human Computer Interaction, Software Fault Tolerance, E-Commerce, System Analysis and Design, Programming in Visual Basic and C++ and database in addition to supervision of many undergraduate projects. Her research includes Software Requirement, Software Design, and Component-Based Software Engineering. She concentrates on building systems with a high level of quality. During the past 3 years, she has been focusing on Software Architecture and how to build high quality products through it. She has done 10+ researches on Software Architecture and Software Architecture in Business. She was a keynote speaker in WORLDCOMP'16 titled 'Software Architecture: Comprehensive Study'. Lina is also an editor in the Journal of Communications and Information Science, which is related to the Advanced Institute of Convergence IT.
Autoren/Hrsg.
Weitere Infos & Material
1;Preface;5
2;Acknowledgment;6
3;Contents;7
4;Chapter 1: Introduction;11
4.1;1.1 Architecture Definition;11
4.2;1.2 Basic Types of Architecture;12
4.2.1;1.2.1 Software Architecture;12
4.2.1.1;1.2.1.1 Modern Software Architecture;14
4.2.2;1.2.2 System Architecture;15
4.2.3;1.2.3 Enterprise Architecture;15
4.2.3.1;1.2.3.1 Business Architecture;16
4.2.4;1.2.4 Modern App Architecture for the Enterprise;17
4.3;1.3 Architecture Life Cycle;20
4.3.1;1.3.1 Architecture and Requirements;21
4.3.2;1.3.2 The Life Cycle of Architecture;21
4.3.3;1.3.3 Documenting Architecture;23
4.4;1.4 Architecture and Technology;24
4.4.1;1.4.1 Influence of Architecture on Systems;24
4.5;1.5 Architecture’s Role in Business;26
4.5.1;1.5.1 What Makes Good Architecture in Business?;27
4.6;1.6 Architectural Pattern;28
4.7;1.7 Summary;29
4.8;References;30
4.8.1;Further Reading;30
5;Chapter 2: Business Software Architecture (BSA);31
5.1;2.1 Business Software Architecture;31
5.1.1;2.1.1 Software Architects Need Business Education;32
5.1.2;2.1.2 Roles of Software Architects and Business Managers in Business Software Architecture;33
5.2;2.2 Defining Requirements for Business Architecture;34
5.3;2.3 Pragmatic Architecture Today;37
5.4;2.4 Business Architecture’s Roles in Management;37
5.5;2.5 Summary;40
5.6;References;41
5.6.1;Further Reading;41
6;Chapter 3: Understanding and Dealing with Qualities;43
6.1;3.1 Definition of Quality;44
6.2;3.2 Software Qualities for the Product;44
6.2.1;3.2.1 Architecture Quality Attribute and Business Quality Attribute;46
6.3;3.3 Architecture and Quality;47
6.3.1;3.3.1 Architecturally Significant Requirement (ASR);48
6.3.1.1;3.3.1.1 Interviewing Stakeholders;48
6.3.1.2;3.3.1.2 Gathering by Business Goals;49
6.3.1.3;3.3.1.3 Gathering Requirements Through Utility Tree;50
6.3.1.4;3.3.1.4 Gathering ASR Through Requirement Document;50
6.3.2;3.3.2 Qualities and Trade-Offs;51
6.4;3.4 Gathering Quality Attribute Information;52
6.4.1;3.4.1 Quality Attribute Scenario (QAS);52
6.4.1.1;3.4.1.1 Example on QAS;55
6.4.2;3.4.2 Quality Attribute Workshop (QAW);55
6.4.2.1;3.4.2.1 QAW Steps;56
6.4.2.2;3.4.2.2 Advantages of QAW;58
6.5;3.5 Summary;58
6.6;References;60
6.6.1;Further Reading;60
7;Chapter 4: Achieving Quality Attribute;61
7.1;4.1 Introduction;61
7.2;4.2 Architectural Pattern;62
7.2.1;4.2.1 Patterns and Their Roles in Building Architecture;63
7.3;4.3 Tactics and Quality Attributes;73
7.3.1;4.3.1 Achieving Quality Through Tactics;74
7.3.2;4.3.2 The Relationship Between Tactics and Patterns;77
7.4;4.4 Business Pattern;78
7.4.1;4.4.1 Pattern for Enterprises;78
7.5;4.5 Importance of Patterns in Business;79
7.6;4.6 The SEI Attribute-Driven Design (ADD) Method;80
7.7;4.7 Summary;83
7.8;References;84
7.8.1;Further Reading;85
8;Chapter 5: Managing Business Qualities;86
8.1;5.1 Business Quality Definition;86
8.2;5.2 Business Goals;87
8.2.1;5.2.1 The Role of the Architect in Achieving the Quality;90
8.3;5.3 Definition of Total Quality Management (TQM);91
8.3.1;5.3.1 Principles of TQM;92
8.3.1.1;5.3.1.1 Customer Focus;92
8.3.1.2;5.3.1.2 Continuous Improvement;92
8.3.1.3;5.3.1.3 Employee Empowerment;93
8.3.1.4;5.3.1.4 Product Design;93
8.3.1.5;5.3.1.5 Process Management;94
8.3.1.6;5.3.1.6 Managing Supplier Quality;94
8.3.1.7;5.3.1.7 Use of Quality Tools;94
8.4;5.4 Stakeholders;95
8.4.1;5.4.1 Stakeholders and Business Goals;96
8.5;5.5 Process Improvement;97
8.5.1;5.5.1 Process and Product Quality;97
8.5.2;5.5.2 The Process Improvement Life Cycle;98
8.6;5.6 Important Qualities in Business;100
8.7;5.7 Summary;100
8.8;References;101
8.8.1;Further Reading;102
8.8.2;Journal Papers;102
9;Chapter 6: Software Product Line (SPL);103
9.1;6.1 SPL Definition;103
9.2;6.2 A Framework for Software Product Line Engineering;105
9.3;6.3 Architecture and Software Product Line;107
9.3.1;6.3.1 What Makes a Software Product Line Succeed?;108
9.4;6.4 The Quality Attribute of SPL (Variability Quality);109
9.4.1;6.4.1 The Goal of Variability;110
9.4.2;6.4.2 Variation Mechanism;111
9.5;6.5 Evaluating a Product Line Architecture;112
9.6;6.6 Summary;113
9.7;References;114
9.7.1;Further Reading;114
10;Chapter 7: Internet of Things (IoT);115
10.1;7.1 IoT Definition;115
10.2;7.2 Architecture and IoT;119
10.3;7.3 Basic Qualities of IoT;119
10.3.1;7.3.1 Interoperability Quality;120
10.3.2;7.3.2 Modifiability Quality;123
10.4;7.4 DYAMAND: Case Study;125
10.4.1;7.4.1 DYAMAND Requirement;127
10.4.2;7.4.2 DYAMAND Architecture;128
10.5;7.5 Evaluating IoT Architecture;131
10.6;7.6 Summary;135
10.7;References;135
10.7.1;Further Reading;135
11;Chapter 8: Service-Oriented Business Architecture (SOBA);136
11.1;8.1 Definition of Service-Oriented Business Architecture (SOBA);137
11.2;8.2 Basic Qualities in SOBA;139
11.2.1;8.2.1 Availability;140
11.2.2;8.2.2 Scalability;142
11.3;8.3 The Impact of Service-Oriented Architecture on Quality Attribute and Business Goals;143
11.4;8.4 Service-Oriented Business Architecture and the Evaluation Method;144
11.5;8.5 Summary;149
11.6;References;149
11.6.1;Further Reading;150
12;Conclusion Thoughts;151
13;Appendix A;153
13.1;General Scenario for Modifiability;153
13.2;Concrete Scenario for Modifiability;153
13.3;Role of General Scenario for Performance;154
13.4;Concrete Scenario for Performance;154
13.5;General Scenario for Security;154
13.6;Concrete Scenario for Security;155
13.7;General Scenario for Testability;155
13.8;Concrete Scenario for Testability;156
13.9;General Scenario for Usability;156
13.10;Concrete Scenario for Usability;156
14;Appendix B;157
15;Appendix C;158
15.1;ATAM (Architecture Trade-off Analysis Method);158
15.2;SAAM (the Software Architecture Analysis Method);159
15.3;ARID (Active Reviewers for the Intermediate Design);160
15.3.1;Phase 1: Rehearsal;160
15.3.2;Phase 2: Review;161
16;Index;162




