Kooperativer Bibliotheksverbund

UID:

Format: Online-Ressource (XL, 392 S.)

Edition: Online-Ausg.

ISBN: 1306176131 , 9780124078857 , 9781306176132

Content: Focuses on principles of Agile software development and gaps in the requirements of applying architecture-centric approaches. Readers will learn how Agile and architectural cultures can co-exist and support each other according to the context

Content: Agile software development approaches have had significant impact on industrial software development practices. Today, agile software development has penetrated to most IT companies across the globe, with an intention to increase quality, productivity, and profitability. Comprehensive knowledge is needed to understand the architectural challenges involved in adopting and using agile approaches and industrial practices to deal with the development of large, architecturally challenging systems in an agile way. Agile Software Architecture focuses on gaps in the requirements of applying archit

Note: Includes bibliographical references and indexes , Note continued: 12.5.1.Accelerate the Delivery Pipeline By Incorporating Multiple Perspectives12.5.2.Accelerate Delivery By Maximizing Capacity -- 12.5.3.Accelerate Delivery Through Early Integration -- 12.5.4.Accelerate Delivery Via Early and Continuous Testing -- 12.5.5.Accelerate Delivery Via An Automated Deployment Pipeline -- 12.6.Conclusion -- References -- ch. 13 Building a Platform for Innovation: Architecture and Agile as Key Enablers -- 13.1.Introduction -- 13.2.Worlds Collide -- 13.3.An Architecture Heritage -- 13.4.Iterative Development -- 13.5.Along Came Agile -- 13.6.Agile With Discipline -- 13.7.Beyond Architecture and Agile -- 13.7.1.Define a Project Lifecycle Selection Framework -- 13.7.2.Tailor the Method -- 13.7.3.Consider All Elements of a Development Environment -- 13.7.4.Adopt Change Incrementally -- 13.7.5.Implement a Center of Excellence -- 13.8.Summary -- References -- ch. 14 Opportunities, Threats, and Limitations of Emergent Architecture -- 14.1.Introduction -- 14.1.1.A Brief Definition of Emergence -- 14.1.2.The Idea of Emergent Architecture -- 14.2.Purpose, Activities, and Objectives of Architecture -- 14.2.1.Purpose -- the Why of Architecture -- 14.2.2.Activities -- the How of Architecture -- 14.2.3.Objectives -- the What of Architecture -- 14.3.Analysis of Emergent Architecture -- 14.3.1.Alignment -- 14.3.2.Structuring -- 14.3.3.Implementation of Nonfunctional Requirements -- 14.3.4.Design for Understandability -- 14.3.5.Design for Change -- 14.4.Discussion -- 14.4.1.Comparison of Explicit and Emergent Architecture -- 14.4.2.A Joint Approach -- 14.5.Conclusion -- References -- ch. 15 Architecture as a Key Driver for Agile Success: Experiences At Aviva UK -- 15.1.Introduction -- 15.2.Challenges to Agile Adoption At Aviva UK -- 15.3.The Key Role of Architecture in Driving Agile Success -- 15.3.1.Sufficient Up-front Architecture and Design -- 15.3.2.Layered Architecture Enabling Independent Change Agility -- 15.3.3."Change-time" Architecture and "run-time" Architecture -- 15.4.Incremental Agile and Architecture Transformation -- 15.5.Conclusions -- References. , Machine generated contents note: ch. 1 Making Software Architecture and Agile Approaches Work Together: Foundations and Approaches1.1.Introduction -- 1.2.Software Architecture -- 1.2.1.Software Architecture Process and Architecture Lifecycle -- 1.2.2.Architecturally Significant Requirements -- 1.2.3.Software Architecture Design Methods -- 1.2.4.Documenting Software Architecture -- 1.2.5.Software Architecture Evaluation -- 1.3.Agile Software Development and Architecture -- 1.3.1.Scrum -- 1.3.2.Extreme Programming -- 1.4.Making Architectural and Agile Approaches Work -- Acknowledgments -- References -- pt. 1 FUNDAMENTALS OF AGILE ARCHITECTING -- ch. 2 The DCI Paradigm: Taking Object Orientation into the Architecture World -- 2.1.Introduction -- 2.1.1.Agile Apologia -- 2.1.2.Architecture and DCI -- 2.2.The Vision: What is Architecture? -- 2.2.1.Why do we do Architecture? -- 2.2.2.Into Software -- 2.2.3.Why Software Architecture? -- 2.2.4.Architecture and the Agile Agenda -- 2.2.5.DCI as an Integrative View of the Architecture Metaphor -- 2.3.Form and Function in Architectural History -- 2.3.1.Historic Movements and Ideologies -- 2.3.2.Enter Postmodernism -- 2.3.3.Architecture Finds an Object Foothold -- 2.3.4.Software Engineering and Architecture Today -- 2.3.5.Measures of the Vision -- 2.4.What is Object Orientation? Achieving the Vision -- 2.4.1.The Kay Model -- 2.4.2.Mental System Models -- 2.4.3.Model-View-Controller -- 2.4.4.Patterns -- 2.4.5.Use Cases -- 2.4.6.Many Views of Objects and the Boundaries of MVC -- 2.5.Shortcomings of the Models -- 2.5.1.The Network Paradigm -- 2.5.2.Model-View-Controller -- 2.5.3.Patterns -- 2.5.4.Use Cases -- 2.5.5.The Object Canon -- 2.6.DCI as a New Paradigm -- 2.6.1.A DCI Overview -- 2.6.2.Relating DCI to the Original OO Vision -- 2.6.3.DCI and the Agile Agenda -- 2.7.DCI and Architecture -- 2.7.1.DCI and the Postmodem View -- 2.7.2.Patterns and DCI -- 2.7.3.DCI and the Network Computation View -- 2.7.4.Firmitas, Utilitas, and Venustas -- 2.8.Conclusion -- References -- Further Reading -- ch. 3 Refactoring Software Architectures -- 3.1.Introduction -- 3.2.Dealing with Design Flaws -- 3.3.Evolution and Styles of Refactoring -- Code Refactoring -- 3.4.Evolution and Styles of Refactoring -- Refactoring to Patterns -- 3.5.The Motivation for Software Architecture Refactoring -- 3.6.Architectural Smells -- 3.7.A Real-World Example -- 3.8.Quality Improvement -- 3.9.The Process of Continuous Architecture Improvement -- 3.10.Shallow and Deep Refactoring -- 3.11.Additional Examples of Architecture Refactoring Patterns -- 3.11.1.Breaking Dependency Cycles -- 3.11.2.Splitting Subsystems -- 3.12.Known Obstacles to Architecture Refactoring -- 3.13.Comparing Refactoring, Reengineering, and Rewriting -- 3.14.Summary -- References -- ch. 4 Driving Architectural Design and Preservation From a Persona Perspective in Agile Projects -- 4.1.Introduction -- 4.2.Personas in the Design Space -- 4.3.Discovering ASRs -- 4.3.1.From Features to Architectural Concerns -- 4.3.2.Embedding Architectural Concerns Into Personas -- 4.4.Personas for Driving Architectural Design -- 4.4.1.Goal Analysis -- 4.4.2.Generating and Evaluating Architectural Solutions -- 4.4.3.Examples -- 4.5.Personas and Architectural Preservation -- 4.5.1.Trace By Subscription -- 4.5.2.Generating Persona-centric Perspectives -- 4.5.3.Examples -- 4.6.ASPs in Other Project Domains -- 4.6.1.Mechatronics Traceability -- 4.6.2.Online Trading -- 4.6.3.Bond, James Bond -- 4.7.Conclusions -- Acknowledgments -- References -- ch. 5 Architecture Decisions: Who, How, and When? -- 5.1.Introduction -- 5.2.Research Methodology -- 5.3.The Agile Architecture Axes Framework -- 5.3.1.Who Makes the Architectural Decisions? -- 5.3.2.What Artifacts Are Used to Document the Decision? -- 5.3.3.What Is the Feedback Loop of An Architectural Decision? -- 5.3.4.Summary of the Axes -- 5.4.Industrial Cases -- 5.4.1.Case Alpha -- 5.4.2.Case Beta -- 5.4.3.Case Gamma -- 5.4.4.Case Delta -- 5.4.5.Case Epsilon -- 5.4.6.Overview -- 5.5.Analysis -- 5.5.1.Mapping the Cases to the Triple-A Framework -- 5.5.2.Identified Problems -- 5.5.3.Summary -- 5.6.Reflection -- 5.6.1.Findings -- 5.6.2.Questions of Validity -- 5.7.Related and Future Work -- 5.8.Conclusions -- Appendix -- A Visual Representation of the Case Studies Mapped on the Triple-A Framework -- References -- pt. 2 MANAGING SOFTWARE ARCHITECTURE IN AGILE PROJECTS -- ch. 6 Supporting Variability Through Agility to Achieve Adaptable Architectures -- 6.1.Introduction -- 6.2.Background -- 6.2.1.Variability -- 6.2.2.Agility -- 6.3.Related Work -- 6.4.Challenges when Combining Variability and Agility -- 6.5.Arguments for Combining Variability and Agility -- 6.6.Agile-Inspired Variability Handling -- 6.6.1.Industrial Context: Dutch e-Government -- 6.6.2.Step 1: Conduct Initial Variability Analysis -- 6.6.3.Step 2: Create Initial Architecture Variability Profile -- 6.6.4.Step 3: Create Architecture -- 6.6.5.Steps 4a and 4b: Evaluate Architecture -- 6.6.6.Step 5: Implement Initial Architecture -- 6.6.7.Step 6: Elicit New Variability Requirements -- 6.6.8.Step 7: Revise Architecture Variability Profile -- 6.6.9.Step 8: Refactor Architecture -- 6.7.Summary and Conclusions -- Acknowledgments -- References -- ch. 7 Continuous Software Architecture Analysis -- 7.1.Introduction -- 7.2.Software Architecture Analysis -- 7.3.Approaches to Software Architecture Analysis -- 7.3.1.Architecture Reviews -- 7.3.2.Scenario-Based Evaluation Methods -- 7.3.3.Architecture Description Languages -- 7.3.4.Dependency Analysis Approaches and Architecture Metrics -- 7.3.5.Architecture Prototyping -- 7.3.6.Ad Hoc Analysis -- 7.4.Continuous Software Architecture Analysis -- 7.4.1.CSAA and Different Kinds of Architecture Analysis -- 7.4.2.Approaches for Continuous Quality Control (CQC) -- 7.4.3.Characteristics of CQC Approaches -- 7.4.4.CSAA Process -- 7.5.CSAA in Existing Approaches -- 7.6.CSAA and Analysis Goals -- 7.7.Experiences With An Approach to CSAA -- 7.7.1.Validation -- 7.8.Findings and Research Challenges -- 7.9.Conclusion -- References -- ch. 8 Lightweight Architecture Knowledge Management for Agile Software Development -- 8.1.Introduction -- 8.2.Challenges of Agile Architecture Documentation -- 8.3.Supporting Techniques for AKM in Agile Software Development -- 8.3.1.Architecture Evaluation Methods, Agility, and AKM -- 8.3.2.Advanced Techniques for Managing Architectural Repositories -- 8.4.Architecture Practices in Agile Projects -- 8.4.1.Scrum Framework -- 8.4.2.Architecting While Using Scrum -- 8.5.Architectural Information Flow in Industry -- 8.5.1.Interview Setup -- 8.5.2.Results -- 8.5.3.General Comments From Interviewees -- 8.5.4.Limitations -- 8.6.AKM in Scrum -- 8.6.1.Big-up-front-Architecture and Sprint-Zero Architecting Approaches -- 8.6.2.In-sprints Architecting Approach -- 8.6.3.Separated-architecture-team Architecting Approach -- 8.7.Related Work -- 8.8.Conclusions -- Acknowledgments -- References -- ch. 9 Bridging User Stories and Software Architecture: a Tailored Scrum for Agile Architecting -- 9.1.Introduction -- 9.2.Agile Architecting -- 9.3.Case Study: Metering Management System in Electrical Power Networks -- 9.4.Agile Architecting Mechanisms -- 9.4.1.Feature Pool and Feature Tree of User Stories -- 9.4.2.Flexibility in Software Architecture Design -- 9.4.3.Agile Design Decisions: CIA Support -- 9.5.A Tailored Scrum for Agile Architecting -- 9.6.Agile Architecting in Practice -- 9.7.Findings About Agile Architecting -- Acknowledgments -- References -- pt. 3 AGILE ARCHITECTING IN SPECIFIC DOMAINS -- ch. 10 Architecture-Centric Testing for Security: An Agile Perspective -- 10.1.Introduction -- 10.2.Research Motivation -- 10.3.Overview of Limitations in Current Post-implementation Methods -- 10.3.1.Functional Testing of Security Apparatuses -- 10.3.2.Penetration Testing -- 10.3.3.Threat Modeling -- 10.3.4.Discussion -- 10.4.Introducing Implied Scenarios -- 10.4.1

Additional Edition: ISBN 9780124077720

Additional Edition: ISBN 0124077722

Additional Edition: ISBN 9780124077720

Additional Edition: Erscheint auch als Druck-Ausgabe Agile software architecture Amsterdam [u.a.] : Elsevier/MK, Morgan Kaufmann, 2014 ISBN 9780124077720

Language: English

Subjects: Computer Science

Keywords: Agile Softwareentwicklung ; Softwarearchitektur ; Electronic books ; Aufsatzsammlung

URL: Volltext

Author information: Ali Babar, Muhammad