Download as PDF, PPTX
Uploaded byAbhilash Gopalakrishnan
Software Architecture in an Agile World
The document provides an overview of software architecture in an agile world. It discusses the need for speed in software development driven by factors like scaling, heterogeneous systems, and reduced infrastructure costs. It then covers foundations of software architecture including definitions, skills, deliverables, and examples of great reference architectures. The remainder outlines an agile approach to software architecture, including preparing an architecture vision, early decisions, decomposition, identifying significant elements, a risk-based roadmap, measuring progress, and communicating. The summary emphasizes that architects now play a continuous role on development teams.
More Related Content
Similar to Software Architecture in an Agile World
Software Architecture in an Agile World
- 1. Source: Picture - Software Architecture| In An Agile World Presentation Agenda Need for Speed | Foundations| Roadmap| Agile Approach | Summary Abhilash G, Principal Engineer, ABB/IDC/EPDA, 7 July 2018
- 2. Software Architecture| Needfor Speed The Need Forces from across the world driving revolutions! Need for Scale Need for Speed Heterogeneous Systems How can I scale? How can we combine heterogeneous systems? Key Number 8.4 BillionConnected"Things"Will Be in Use in 2017 More devices than people- More M2M Technology is often like fashion-Distributed Architectures are back! How to reduce my inventory costs? How can we get to market faster? The shift from centralized to more distributed styles is evident in the evolution happening in Smart Grids, Industry 4.0, Industrial internet and IoT, Society 5.0. Need for reduced infra. Sources: Gartner, Japan.go.jp http://www.independent.co.uk/life-style/gadgets-and-tech/news/there-are-officially- more-mobile-devices-than-people-in-the-world-9780518.html https://www.japan.go.jp/abenomics/_userdata/abenomics/pdf/society_5.0.pdf 1 of 20 Digital Transformation, Agile Transformation Drive speed by Industrialization Drive Speed through R&D Cycle time reduction How can we reskill ourselves?
- 3. Who else canchart the roadmap like an Architect! “ And with a lot of arrogance and even more ignorance, I thought, Who better to fix it than me? This is something I need to do” “What we need is an entrepreneurial society in which innovation and entrepreneurship are normal, steady and continuous.” — Peter F. Drucker “ Software Systems have passed through five ages corresponding to each decade starting from 1980 towards Intelligent, Connected system in 2020 ” – Eoin Woods, CTO at Endava (prev Software Architect) Software Architecture| Need for Speed In new society https://hbr.org/2016/10/6-signs-youre-living-in-an-entrepreneurial-society Survey among 49 projects Reported by Raymond Slot,PhDThesis,2010. Budget predictabilityis 2-3x better with architecture practices. While Budget overrun 7 x less lesser, Time overrun 6 x less, Troubledprojects3x less and Customer satisfaction1-2 pointsbetter 2 of 20
- 4. Software Architecture ofa system is the structure of structures of a system with its externally visible properties and relationships Software Architecture| Foundations Definitions and Standards ‘Architecture is about the important stuff. Whatever that is’ – Martin Fowler A system is built to address the needs, concerns, goals and objectives of its stakeholders. The architecture of system comprises of its architectural elements and their interrelationships. Architecture is documented in Architecture Description and demonstrates that it has met their needs. IEC/ISO/IEEE 42010 3 of 20 Depth of involvement of architect could vary across phases in the life cycle. Architect uses programming skills to build demonstrators showing how requirements are met.
- 5. Software Architecture| Foundations Skills,Steps Deliverables Why •The System is built - Need What •The System accomplishes - Goals How •The System acts - Function When •The elements are - Form Who •Does them – Operator How much •Does it cost? The deliverables span across the phases and many are early decisions!4 of 20 1. A clear complete, consistent and attainable set of goals (stress functional goals) 2. A description of the broader context of the system including global standards. 3. A concept of the system 4. A concept of operations of the system including contingency & emergency operations 5. A functional decomposition of the system with at least 2 layers of decomposition with primary and secondary functions, process flow , supporting and interface processes 6. The decomposition of form to two levels of detail and allocation of functions to form with details of all external interfaces and interface control process and a notion of development cost, schedule and risk Deliverables Business Case for System Understand Requirements Create/Select Suitable Architecture Analyse or Evaluate Architecture Document and Communicate Architecture Implement Architecture Stability and Conforming to Vision
- 6. HallofFameSoftware Architecture| Foundations AGreat Reference Architecture Performance •Network Performance •User Perceived Performance •Network Efficiency Scalability •Ability to support large number of components and transactions Simplicity •Complexity, Understandabi lity •Verifiability Modifiability •Evolvability •Extensibility •Customization •Configuration •Reusability Visibility •Ability of componentto monitoror mediate between two components Portability •Can run in different environments Reliability •Degree of susceptibility to failurein case of partial failure from components Reference Architecture of Internet WWW The Internet – HTTP Specification – Apache HTTP Server Project Berners-Lee “Web’s major goal was to be a shared information space through which people and machines could communicate.” What was needed was a way for people to store and structure their own information, whether permanent or ephemeral in nature, such that it could be usable by themselves and others, and to be able to reference and structure the information stored by others so that it would not be necessary for everyone to keep and maintain local copies. The intended end-users of this system were located around the world, at various university and government high-energy physics research labs connected via the Internet. Their machines were a heterogeneous collection of terminals, workstations, servers and supercomputers, requiring a hodge podge of operating system software and file formats. The information ranged from personal research notes to organizational phone listings. The challenge was to build a system that would provide a universally consistent interface to this structured information, available on as many platforms as possible, and incrementally deployable as new people and organizations joined the project. Low Entry Barrier HYPERMEDIA Relationships Links DISTRIBUTED HYPERMEDIA Presentation Control AnarchiacScalability IndependentDeployment URI, HTTP, HTML 5 of 20
- 7. Architecting on theGo! - A Road Map to Architecting in Agile! “ Who wants an Architect” – Martin Fowler “Architecting as Risk and Cost Discipline.” — Eltjo Poort “R&D As Experimentation System”— Jan Bosch Software Architecture| RoadMap The Approach “ A fairly recent evolution is -Architect acts less upfrontdesign of structures i.e., Significant decisions made just in time -Architect deals with more probability than certainty - Large Systems Policy Driven Automation - Architecture is still very much art of possible – financial constraints like cloud pricing in consideration - Radical intelligence , Dynamic Components, Cloud Platform Deployment, Connection to things in mainstream” -Eoin Woods Architecting On the Go 6 of 20 ‘There's speed work, and then there's speed work. When most runners talk about doing speed work, they mean things like mile repeats at 10K race pace, or a set of fast 200s, or maybe even a 5-mile tempo run. Such workouts, of course, are integral to becoming a faster runner. But they're not really speed work, if by "speed" we mean the fastest you can run for a very short distance. When I talk about speed, I mean your maximalvelocity— your top speed—whicheven world-classsprinterscan sustain for no more than 30-40m.’ Jay Johnson inhttps://www.runnersworld.com/advanced/a20788111/speed-development/
- 8. Software Architecture| Agile Foundations UsingRisk and Cost to Drive Architecting Risk and Cost Based Architecting Principles 1. Decisions are your main deliverable. 2. Keep a backlog of architectural concerns. 3. Let economic impact determine your focus. 4. Keep it small. 5. Use Just Enough Anticipation. Applying RCDA in our context we have arrived at : 1. Prepare an Architecture Vision 2. Prepare a Decomposition 3. Identify the Most Significant Elements 4. Arrive at Risk and Cost Based Roadmap 5. Feedback, Analyzing Progress 6. Communicating the Progress Architecting On the Go 7 of 20 “The best architectures, requirements, and designs emerge from self-organizing teams.”
- 9. Software Architecture| AgileApproach Insights into Scope Need some insights into scope One day Alice came to a fork in the road and saw a Cheshire cat in a tree. ‘Which road do I take?’ she asked. ‘Where do you want to go?’ was his response. ‘I don’t know’, Alice answered. ‘Then’, said the cat, ‘it doesn’t matter’. Overview of Scope Reference Standard Simulation Interoperability Standards Organization (SISO) SISO-STD-003-2006: Standard for Base Object Model (BOM) Template Specification (8 May 06) SISO-STD-007-2008: Standard for Military Scenario Definition Language (MSDL) (reaffirmed 11 May 2015) Architecting On the Go 8 of 20
- 10. Software Architecture| AgileApproach Prepare an Architecture Vision A Target State is required to start ! Domain Model Reference Architectures Business & Technology Trends Architecture Vision An Architecture Vision is arrived at using inputs from early understanding of Scope coming from Domain Model, Reference Architectures and the Business and Technology Trends. SISO STANDARD Reference Architectures Business &Technology Trends Architectural Vision includes Models, Ref Architectures & Trends MODEL ELEMENT SCENARIO NASA VIDEOS BOEING STUDIO LITERATURE PORTABILITY OPEN ARCH LIFECYCLE CONTINOUS Architecting On the Go 9 of 20
- 11. Software Architecture| AgileApproach Early Decisions Early Decisions have major impact! Some early decisions on Infrastructure need to be taken in the very beginning Element Selection Rationale Source Control GITHUB Lifecyle Language and Framework C++, QT, XML Portability Standardized SISO Open Architecture Build System Cmake, Jenkins, CPPUTest Open , Easy to Use Architecting On the Go 10 of 20
- 12. Software Architecture| AgileApproach Decomposition and Layered View Decomposition based on Reference Architectures Based on the Domain Model and Reference Architecture and Prepare a Decomposition as much as we know Architecting On the Go 11 of 20
- 13. Software Architecture| AgileApproach Most Significant Elements Identify the Most significant elements The Most significant elements identified considering the Key Interfaces, Key Interactions and based on experience and proven knowhow which elements are risky and could be costly to make a change later. This should guide us on performing architecture evaluation or checking fulfillment of functional and non functional requirements later. ToolBox Graphical Scene Commn Engine Format Format Communication Stack Current State Target State Step1 Step2 Architecting On the Go 12 of 20
- 14. Software Architecture| AgileApproach Risk Based Roadmap Roadmap Based on Target Architecture Vision, Decomposition and elements The dependencies are controlled. Architectural Elements, Features and Technical Debt Handling all go into the Backlog Sprint 1 Sprint 2 Sprint 3 Sprint 4 ToolBox with No Graphic ToolBox with Graphic Scenario Creation & Save STABILIZE F A 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load F A T 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load F A T 1. Scenario Format 2. Information Flow 3. Connection & Save F A T 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load 4. Scenario Save Architecting On the Go 13 of 20
- 15. Software Architecture| AgileApproach Measuring Progress Feedback Loop to Measure Progress Measuring the Progress is done by pulling the Iteration result, performing Structure 101 analysis Performing Integration Testing and Demo testing and then marking it as ready. Sprint 1 Sprint 2 ToolBox with No Graphic ToolBox with Graphic F A 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load F A T 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load 1 2 1 2 Architecting On the Go 1 14 of 20 Unit Testing & Integration Testing using CPPUTest
- 16. Software Architecture| AgileApproach Communicating the Progress Continuous Communication of Progress! Communicating Involves again Sprint on Sprint Measurement and Results including the interfaces updated, Architecture Updates all updating in Wiki as part of Continuous Communication Strategy. Sprint 1 Sprint 2 ToolBox with No Graphic ToolBox with Graphic F A 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load F A T 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load 1 2 Wiki T Technical Debt B Bugs Demo Captures Architecting On the Go 15 of 20 UML Model update & Architecture Documentation
- 17. Software Architecture| AgileApproach Architectural elements Grooming Architectural elements analysis as part of grooming Architectural elements get continuously groomed as well as part of Grooming of Backlog items. The idea Is to check the Goals and System Objectives and based on the analysis of progress as well as Architectural Document updates, Keep analyzing the Gaps. Sprint 1 Sprint 2 ToolBox with No Graphic ToolBox with Graphic F A 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load F A T 1. BOM Def Format 2. ToolBox Read 3. Toolbox Load 1 2 CAFFEA Framework involving Chief Architect, Governance Architects Refactoring Architecting On the Go 16 of 20 Structure 101 Architecture Action Items in BackLog
- 18. Originally Architect isCustomer’s Person. Journey Maps and Innovation to delight customer is important! Software Architecture| Summary Architecting on the Go! Architect is a development team’s person when involved in design. Teams need Architects support for boosting morale, end to end execution, since they model themselves on servant leadership.. Depth of involvement of architect is higher and continuous. Need to drive a Continuous Integration and Continuous Test Strategy in addition to support to team wherever required. “Good programmers know what to write. Great ones know what to rewrite (and reuse)..” – Eric S. Raymond‐ The Cathedral & The Bazaar Architecting On the Go 17 of 20
- 19. Software Architecture| Summary Architectingon the Go! Future Software Engineering Seems to look forward to combining machine learning algorithm development, data driven development, model driven development and their validation involved over a continuous chain. Architecting On the Go 18 of 20 Automotive SPICE 3.0 http://www.automotivespice.com/fileadmin/software- download/Automotive_SPICE_PAM_30.pdfStairway to Heaven – R&D as Innovation System SW Reqt Analysis Arch & Design Detailed Design & Construction Unit Verification Integration & Test Qualification Test
- 20. SW Architecture| References Booksand Material 1. Eon Woods, “Software Architecturein A Changing World”, IEEE Software Nov 2016. 2. Eltjo Poort, “Adapting ArchitecturePractices to Changing Times to Why and Back Again”, SATURN, May 2016. 3. Martin Fowler, “Who Needs an Architect?”, IEEE Software , 2003. 4. Dave Hendricksen, “12 Essential Skills for Software Architects”. 5. ISO/IEC/IEEE 42010:2011(E) - ISO/IEC/IEEE Systemsand software engineering -- Architecture description. 6. Nick Rozanski and Eoin Woods, “Software Systems Architecture:Working with Stakeholders Using Viewpoints .” 7. Bruce Cameron, Edward Crawley, Daniel Selva, “System Architecture,Global Edition”. 8. Roy Fielding, ‘Architectural Styles and the Design of Network-based Software Architectures’,Dissertation, 2000. 9. Agile Manifesto, http://agilemanifesto.org/ 10. Stephen Denning, “The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done”. 11. Len Bass, Paul Clements, Rick Kazman, “Software Architecture in Practice” 3rd Edition. 12. Antonio Martini, Lars Pareto, Jan Bosch, “Towards introducing Agile Architecting in Large Companies: the CAFFEA framework”. 13. Jan Bosch, “The Three Layer Product Model:An Alternative View on SPLs and Variability”, Keynote, VAMOS 2018, February 2018. 14. Mathias Traub, Alexander Maier, Karl Barbehon, “Future Automotive Architectureand the Impact of IT Trends”, IEEE Software, June 2017. Architecting On the Go
- 21. “Be the changeyou want to see in the world!” Architecting On the Go MAHATMA GANDHI