000 05113nam a22004695i 4500
001 978-3-031-51335-0
003 DE-He213
005 20240730171941.0
007 cr nn 008mamaa
008 240426s2024 sz | s |||| 0|eng d
020 _a9783031513350
_9978-3-031-51335-0
024 7 _a10.1007/978-3-031-51335-0
_2doi
050 4 _aQA76.758
072 7 _aUMZ
_2bicssc
072 7 _aCOM051230
_2bisacsh
072 7 _aUMZ
_2thema
082 0 4 _a005.1
_223
100 1 _aNagl, Manfred.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_9101076
245 1 0 _aSoftware Architectures
_h[electronic resource] :
_bTopics Usually Missed in Textbooks /
_cby Manfred Nagl, Bernhard Westfechtel.
250 _a1st ed. 2024.
264 1 _aCham :
_bSpringer Nature Switzerland :
_bImprint: Springer,
_c2024.
300 _aXII, 332 p. 102 illus., 29 illus. in color.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
505 0 _aPart 1 Importance of Software Architectures -- 1 The Architecture is the Center of the Software Development Process -- 2 An Integrative Language Approach for Software Architectures -- 3 Sequences of Software Architectures from Abstract to Details -- Part 2 Important Topics on Architecture Level -- 4 Embedded Systems: Simple Rules to Improve Adaptability -- 5 Architectural Styles: Do they Need Different Notations? -- 6 Process Interaction Diagrams are more than Chains or Transport Networks -- 7 Characterization of Shallow and Deep Reuse -- 8 The Software Architecture is the Glue to Deal with Variety and Integration -- 9 Reverse and Reengineering for Old Systems is seldom Complete -- Part 3 Relations to Surrounding Activities -- 10 Process and Model Transformations on Different Levels -- 11 The Transformation from Requirements to Architectures is not Automatic -- 12 Software Architectures and Programming in the Small -- 13 Project Management and Architectures -- 14 Quality Assurance and DocumentationRelated to Architectures -- Part 4 Summaries, Conclusions, Open Problems, Index -- 15 Summary, Lesssons Learned, Messages, Open Problems.
520 _aThis textbook concentrates on processes, activities and results related to software architectures. It describes the separation of architecture artefacts corresponding to their nature, their logical or their modeling level on one hand and at the same time emphasizes their integration based on their mutual relations. Design or development processes demand for integration, as different artifacts must be elaborated, which are mutually dependent and need to be in a consistent form. The book is structured in four parts. The introductory Part I deals with the relevance of architectures, the central role of the design subprocess both in development or maintenance, and the importance of the decisions and artefacts in the overall result. Another topic is the spectrum of views an architecture language has to offer, and that there are different architectures to be regarded, from abstract and static to detailed, technical, and specific. Part II then discusses "important topics" on the architecture level. It deals with adaptability especially for embedded systems, with integrating styles/ pattern notations, with different reuse forms and how to find them, with the role of architectures for integrating different existing systems, and with reverse and reengineering of legacy systems. Next, Part III covers architecture modeling and its relation to surrounding activities, as well as architectures to surrounding other results. The single chapters are on transformation between requirements and architectures, architectures and programming, architectures and project management and organization, as well as architectures and their relations to quality assurance or documentation. Eventually, Part IV summarizes the main messages and presents open problems, both for every single chapter and across chapters. Every chapter focuses on a specific problem it addresses, a question it answers, the attention it demands, a message it conveys, and further open questions it raises. The chapters are mostly independent, which implies a certain redundancy, yet it allows lecturers (and their students) to either use the book as the basis of teaching software architecture or design, or to just pick those aspects that need special attention in a more advanced course.
650 0 _aSoftware engineering.
_94138
650 1 4 _aSoftware Engineering.
_94138
700 1 _aWestfechtel, Bernhard.
_eauthor.
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
_9101077
710 2 _aSpringerLink (Online service)
_9101079
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783031513343
776 0 8 _iPrinted edition:
_z9783031513367
856 4 0 _uhttps://doi.org/10.1007/978-3-031-51335-0
912 _aZDB-2-SCS
912 _aZDB-2-SXCS
942 _cEBK
999 _c87912
_d87912