國立高雄大學圖資館 |

Language: English

Back

Software architecturestopics usually missed in textbooks /

Record Type:	Electronic resources : Monograph/item
Title/Author:	Software architecturesby Manfred Nagl, Bernhard Westfechtel.
Reminder of title:	topics usually missed in textbooks /
Author:	Nagl, Manfred.
other author:	Westfechtel, Bernhard.
Published:	Cham :Springer Nature Switzerland :2024.
Description:	xii, 332 p. :ill. (some col.), digital ;24 cm.
Contained By:	Springer Nature eBook
Subject:	Software architecture.
Online resource:	https://doi.org/10.1007/978-3-031-51335-0
ISBN:	9783031513350$q(electronic bk.)

Software architecturestopics usually missed in textbooks /
Nagl, Manfred.

Software architecturestopics usually missed in textbooks /[electronic resource] :by Manfred Nagl, Bernhard Westfechtel. - Cham :Springer Nature Switzerland :2024. - xii, 332 p. :ill. (some col.), digital ;24 cm.

Part 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.

This 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.

ISBN: 9783031513350$q(electronic bk.)

Standard No.: 10.1007/978-3-031-51335-0doiSubjects--Topical Terms:

230927
Software architecture.

LC Class. No.: QA76.754

Dewey Class. No.: 005.12

Software architecturestopics usually missed in textbooks /
LDR:04415nmm a2200325 a 4500 001 664478
003 DE-He213
005 20240426130335.0
006 m d
007 cr nn 008maaau
008 241219s2024 sz s 0 eng d
020 $a 9783031513350$q(electronic bk.)
020 $a 9783031513343$q(paper)
024 7 $a 10.1007/978-3-031-51335-0 $2 doi
035 $a 978-3-031-51335-0
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.754
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
072 7 $a UMZ $2 thema
082 0 4 $a 005.12 $2 23
090 $a QA76.754 $b .N149 2024
100 1 $a Nagl, Manfred. $3 285683
245 1 0 $a Software architectures $h [electronic resource] : $b topics usually missed in textbooks / $c by Manfred Nagl, Bernhard Westfechtel.
260 $a Cham : $b Springer Nature Switzerland : $b Imprint: Springer, $c 2024.
300 $a xii, 332 p. : $b ill. (some col.), digital ; $c 24 cm.
505 0 $a Part 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 $a This 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 $a Software architecture. $3 230927
650 1 4 $a Software Engineering. $3 274511
700 1 $a Westfechtel, Bernhard. $3 344855
710 2 $a SpringerLink (Online service) $3 273601
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-3-031-51335-0
950 $a Computer Science (SpringerNature-11645)