DOCSLIB.ORG

Modern Software Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Modern Software Architecture Roni Jumpponen Modern Software Architecture Metropolia University of Applied Sciences Bachelor of Engineering Mobile Solutions Bachelor’s Thesis 5 May 2021 Abstract Author Roni Jumpponen Title Modern software architecture Number of Pages 54 pages Date 5 May 2021 Degree Bachelor of Engineering Degree Programme Information and Communications Technology Professional Major Mobile Solutions Instructors Mikael Lindblad, Site Project lead Peter Hjort, Senior Lecturer The aim of the thesis was to research the necessity of software architecture in modern soft- ware development. Another aim was to find out how much architecture and documentation should be done in agile development, and what should be the points of focus. The idea was to use this gathered knowledge to deliver a solid software architecture and design for the partner corporation’s internal use application. The application connected to the thesis is an experimental product utilizing modern sensor and data analysis technologies measuring fill rates based on various metrics. The current experiments include measuring the usage of restaurant, its line queues and the usage of parking lots around the corporation’s campus. The application is meant to be a living product with a long lifespan including collaboration with various third-party organizations such as universities. This thesis builds on the key principles and concepts of traditional software architecture fo- cusing on more modern agile view and considerations on how they could still be beneficial for modern software development. Incremental architecture and design were the themes of this study as the partner company wanted something that would stand the test of time and could be built piece by piece. Ease of expandability and modularity are key concepts for the thesis. The practical part focuses on the decision making which helped to reach the conclusions leading to the project team’s final version of the architecture and the connected cloud solution design. As the architecture is meant to be incremental, it will continue to change and evolve in future. As a result of this study, a cloud solution on MS Azure was built. Also, this study compares different cloud service options for certain areas and cost analysis. Additionally, throughout the thesis there are mentions of different technologies for implementing various mechanisms used for enabling certain architectures and other key implementation details. Keywords Software Architecture, Cloud, System, Design, Agile Tekijä Roni Jumpponen Otsikko Moderni ohjelmistoarkkitehtuuri Sivumäärä 54 sivua Aika 5.5.2021 Tutkinto Insinööri (AMK) Tutkinto-ohjelma Tieto- ja viestintätekniikka Ammatillinen pääaine Mobile Solutions Ohjaajat Projektipäällikkö Mikael Lindblad Lehtori Peter Hjort Insinöörityön tarkoituksena oli selvittää ohjelmistoarkkitehtuurin tarpeellisuus ja paikka mo- dernissa ohjelmistokehityksessä ja vastata kysymykseen, kuinka paljon arkkitehtuuria ja dokumentaatiota tarvitaan ketterässä ohjelmistokehityksessä. Tarkoituksena oli käyttää hankittu tietämys laadukkaan ohjelmistoarkkitehtuurin ja suunnitelman tuottamiseen työn tilaajayrityksen sisäiseen ohjelmistoprojektiin. Insinöörityössä kehitetty sovellus on kokeellinen tuote, joka hyödyntää moderneja sensori- ja data-analyysiteknologioita, jotka mittaavat käyttöasteita käyttäen erilaisia mittaustapoja. Tämänhetkiset kokeet sisältävät yrityksen kampuksen ravintolan käyttöasteen, jonotusajat ja pysäköintipaikkojen käyttöasteen. Sovelluksen tarkoituksena on olla pitkän elinkaaren tuote, jota kehitetään yhteistyössä eri tahojen kanssa, kuten yliopistojen ja ammattikorkea- koulujen. Insinöörityö rakentui perinteisen ohjelmistoarkkitehtuurin avainsääntöjen ja -konseptien va- raan tavoitellen modernimpaa ja ketterämpää näkökulmaa sekä tarjoaa ajatuksia siitä, kuinka ne voisivat vieläkin olla hyödyllisiä modernin ohjelmistokehityksen kannalta. Inkrementaalinen arkkitehtuuri ja suunnittelu olivat vahvoja teemoja työssä, koska työn ti- lannut yritys halusi pitkän aikavälin ratkaisua, jonka ympärille voisi rakentaa asioita pikkuhil- jaa. Laajennuksen helppous ja modulaarisuus olivat avainkonsepteja insinöörityössä, ja työn käytännön osuus keskittyi projektiryhmän päätöksentekoon, joka johti arkkitehtuurin viimei- seen versioon ja siihen yhdistettävään pilvipalveluratkaisuun. Arkkitehtuuri tehtiin helposti muokattavaksi ja sen on tarkoitettu muuttuvan vielä tulevaisuudessa. Työn tekninen näkökulma sisälsi pilvipalveluratkaisun rakentamisen MS Azuressa ja eri pal- veluiden välisiä vertailuja sekä hinta-analyysin. Tämän lisäksi insinöörityöraportti sisältää paljon viitteitä erilaisiin teknologioihin, joita käytetään erilaisten arkkitehtuurien mahdollista- miseen tai muihin oleellisiin toteutuksiin. Avainsanat ohjelmistoarkkitehtuuri, pilvi, järjestelmä, suunnittelu, ketterä kehitys Contents List of Abbreviations 1 Introduction 1 2 Software Architecture 2 2.1 Structures 2 2.2 The purpose of software architecture 4 3 Quality attributes 5 3.1 System requirements 6 3.2 Scenarios 6 3.3 Tactics 7 3.4 Availability 7 3.5 Interoperability 8 3.6 Modifiability 10 3.7 Performance 11 3.8 Security 13 3.9 Testability 15 3.10 Usability 18 3.11 Other quality attributes and customized quality attributes 19 4 Software architecture patterns 19 4.1 Layered architecture and monoliths 20 4.2 Microkernel architecture 23 4.3 Microservices 25 5 Agile software architecture 29 5.1 Evolutionary software architecture 31 6 Documenting and visualizing the architecture 32 6.1 Architectural views and notations 33 6.2 C4 Architecture model 33 7 Project background 35 8 Initial project requirements 36 8.1 Functional requirements for the product 36 8.2 Quality attributes 37 8.3 Constraints 37 9 Project infrastructure and early design choices 38 9.1 Toolkit 38 9.2 Early design choices and observations 39 10 Project architecture and pattern choices 40 10.1 First pattern consideration, the microservices 40 10.2 Microkernel style frontend speculations and research 42 10.3 Meet the micro frontends 43 11 Creating a cloud solution design 45 12 Further development and complications 48 13 Azure environments and Cost estimations 49 14 Conclusion for the project, but not for the product 51 References 53 List of Abbreviations C4 Model Context, Container, Component, Code IPC Inter-process communication 1 1 Introduction Software development is evolving at a rapid rate and new concepts and technologies are created on a daily basis. Software architecture follows suite and there are new patterns, methods and principles being created to match the evolution and creation of technolo- gies and methods such as Agile development, new frontend and backend frameworks, public cloud platforms and emergence of edge cloud systems. Software architecture is at the heart of every software application’s development and should never be neglected. This thesis covers how software architecture should be uti- lized in modern agile way of working and what is “just enough” of planning and designing before development can begin and how the architecture and the design evolves during the project’s lifespan. This thesis was done in collaboration with a global technology company and both the software architecture, and the system design being created and evaluated are connected to a real-world project. In the thesis we will go through the principles of software archi- tecture and analyze with examples how these design decisions impacted the develop- ment of the project team’s architecture and the actual software system. Practical work and examples will include creating the documentation and visualization of the architecture along with cloud solution design and implementation on MS Azure. Practical work will cover the key design decisions of translating the software architecture into a cloud solution architecture, process of creating the right design using the cloud native services and implementing the design in practice. The study also includes com- parisons between the different options for services and solutions to certain aspects of the system and includes detailed analysis on the reasoning why the development team chose one solution over the other options when choosing the implementation. The purpose of the thesis is to transmit the conceptual ideas behind software architec- ture, the analytical processes and how modern systems are designed using these pro- cesses and built both on the premises and on the public cloud. 2 This study aims to streamline and compress the information into easily understandable and cohesive package with more practical outlook using real-world examples and rele- vant information towards software engineers looking to start creating their own architec- ture and building their own software systems. ISO/IEC/IEEE International Standard - Systems and software engineering—Vocabulary [1] will be used as a reference for standard software engineering and architecture termi- nology. 2 Software Architecture Software architecture in essence is a set of structures comprised of software elements, their relations to each other and properties of elements and relations. These structures and their combinations are often represented as “views”. Views or viewpoints offer dif- ferent levels of abstraction for representation and visualization. This is important, be- cause stakeholders have different interests and needs that need to be represented and visualized when describing the architecture of a system to them. Stakeholders of the system can be anyone who would be interested in the architecture
Load more

Recommended publications
  • Presentación De Powerpoint
    Software Architecture of Oviedoof University Software Architecture Documentation Science Computer of of Course 2018/2019 Jose E. Labra Gayo School Software Architecture Contents of Oviedoof Communicating software architecture University Goal of documentation Documentation stakeholders Views Documentation and agile projects Guidelines Documentation approaches Kuchten 4+1 views Science Views and beyond C4 model Computer of of Arc42 School Software Software School of Computer Science University of Oviedo Architecture Software Architecture of Oviedoof Architecture is more than code University The code doesn't tell the whole story Questions the code doesn't answer How the software fits into existing system landscape? Why the technologies were chosen? What's the overall structure of the system? Where the components are deployed at runtime? How do the components communicate? How and where to add new functionality? What common patterns and principles are used? Science How the interfaces with other systems work? Computer How security/scalability/… has been achieved? of of . School Software Architecture of Oviedoof Goal of documentation Main goal: communicate the structure University Understand the big picture Create a shared vision: team and stakeholders Common vocabulary Describe what the sofware is and how is being built Focus for technical conversations about new features Provide a map to navigate the source code Justify design decisions Science Help new developers that join the team Computer of of School Software Architecture Documentation
    [Show full text]
  • Software Architecture Addresses the Challenge of Communicating and Navigating Large and Complex Systems to Stakeholders, Both Technical and Non-Technical
    SEDT 24 Transcript EPISODE 24 [INTRODUCTION] [0:00:00.0] JM: Software architecture addresses the challenge of communicating and navigating large and complex systems to stakeholders, both technical and non-technical. Over the years, software architecture has gone in and out of fashion. Today we discuss why software architecture is important, what it means to have software architecture and how to properly structure teams and incorporate architecture. Today’s shows guest hosted by David Curry. David sits down with Simon Brown to discuss the importance of having a common language for software systems. Simon is an independent consultant specializing in software architecture. He's the author of Software Architecture for Developers and the founder of Structurizr. If you're interested in hosting a show yourself like David, who is guest hosting the show. It’s his second show he's guest hosted. Check out softwareengineeringdaily.com/host or you can email [email protected], that's me, to find out more about hosting a show. We'd like to get more external voices and turn Software Engineering Daily into more of a media channel with different voices, different types of content, and I’d love to hear your ideas. Send me an email, [email protected]. [SPONSOR MESSAGE] [0:01:29.0] JM: For years when I started building a new app, I would use MongoDB. Now, I use MongoDB Atlas. MongoDB Atlas is the easiest way to use MongoDB in the cloud. It’s never been easier to hit the ground running. MongoDB Atlas is the only database as a service from the engineers who built MongoDB.
    [Show full text]
  • Dashboard Meta-Model for Knowledge Management in Technological Ecosystem: a Case Study in Healthcare †
    Proceedings Dashboard Meta-Model for Knowledge Management in Technological Ecosystem: A Case Study in Healthcare † Andrea Vázquez-Ingelmo 1,*, Alicia García-Holgado 1, Francisco José García-Peñalvo 1 and Roberto Therón 2 1 GRIAL Research Group, Computer Science Department, University of Salamanca, 37008 Salamanca, Spain; [email protected] (A.G.-H.); [email protected] (F.J.G.-P.) 2 VisUSAL, GRIAL Research Group, Computer Science Department, University of Salamanca, 37008 Salamanca, Spain; [email protected] * Correspondence: [email protected]; Tel.: +34-923294500 (ext. 3433) † Presented at the 13th International Conference on Ubiquitous Computing and Ambient Intelligence UCAmI 2019, Toledo, Spain, 2–5 December 2019. Published: 20 November 2019 Abstract: Informal caregivers play an important role in healthcare systems in many countries. They have a high impact on reducing care costs related to dependent persons because their support prevents institutionalization. A technological ecosystem has been defined to support informal caregivers using psychoeducation techniques. This ecosystem should include a dashboard to support decision-making processes related to the wellbeing of patients and caregivers. A dashboard meta-model was used to obtain a concrete model for the presented context. This meta-model allows defining dashboards adapted to the users’ needs and specific data domains. Keywords: model-driven development; dashboard; meta-model; knowledge management; healthcare; technological ecosystem 1. Introduction Nowadays, knowledge is the driver for development in any context. It has become the most important strategic factor in corporate operations [1] because it is associated with the capabilities of companies to achieve a competitive advantage [2,3]. Within an organization, knowledge is not only electronic or printed documents; the employees’ own knowledge and the implicit knowledge within the organization’s processes are part of the assets related to knowledge [4].
    [Show full text]
  • MIRROR Architecture and Integration Plan
    Co‐funded by the Horizon 2020 programme of the European Union h2020mirror.eu MIRROR Migration‐Related Risks caused by misconceptions of Opportunities and Requirements Grant Agreement No. GA832921 Deliverable D7.1 Work‐package WP7: Architecture and Information Model Deliverable D7.1: MIRROR Architecture and Integration Plan Deliverable Leader EURIX Quality Assessor FOI Dissemination level Public Delivery date in Annex I M6, November 30, 2019 Actual delivery date November 30, 2019 Revisions 1 Status Final Keywords MIRROR Architecture, Components, Continuous Integration MIRROR Deliverable 7.1 Disclaimer This document contains material, which is under copyright of individual or several MIRROR consortium parties, and no copying or distributing, in any form or by any means, is allowed without the priorwritten agreement of the owner of the property rights. The commercial use of any information contained in this document may require a license from the propri‐ etor of that information. Neither the MIRROR consortium as a whole, nor individual parties of the MIRROR consortium warrantthat the information contained in this document is suitable for use, nor that the use of the information isfree from risk, and accepts no liability for loss or damage suffered by any person using this information. This document reflects only the authors’ view. The European Community is not liable for any use thatmay be made of the information contained herein. © 2019 Participants in the MIRROR Project Page 2 (of 35) h2020mirror.eu Deliverable 7.1 MIRROR List of Authors Partner Acronym Authors EURIX Francesco Gallo, Germano Russo LUH Erick Elejalde, Miroslav Shaltev SAIL Gerhard Backfried, Erinc Dikici CERTH Vasileios Mezaris, Alexandros Pournaras RUG Jeanne Pia Mifsud Bonnici © MIRROR Page 3 (of 35) MIRROR Deliverable 7.1 Table of Contents Executive Summary 6 1 Introduction 7 1.1 Relationship with Other Deliverables ............................
    [Show full text]
  • Microservices Vs. Service-Oriented Architecture
    Exploring interactive application landscape visualizations based on low-code automation Nick Jansen First supervisor: dr. ir. J.M.E.M van der Werf, UU Second supervisor: prof. dr. S. Brinkkemper, UU External supervisor: ir. A. Koelewijn, Mendix B.V. INTRODUCTION .................................................................... 3 RESEARCH APPROACH .......................................................... 5 2.1 Research Questions ...................................................................... 5 2.2 Research Methods ....................................................................... 7 LITERATURE STUDY ............................................................ 11 3.1 Context ...................................................................................... 11 3.2 Documentation problems .......................................................... 16 3.3 Documentation solutions ........................................................... 19 3.4 Conclusions ................................................................................ 22 THE APPLICATION LANDSCAPE MAP REQUIREMENTS ....... 24 4.1 Interview information ................................................................ 24 4.2 Results ....................................................................................... 24 THE APPLICATION LANDSCAPE MAP SPECIFICATION .......... 33 5.1 Introduction ............................................................................... 34 5.2 Language Structure ...................................................................
    [Show full text]
  • Latest Ubuntu LTS Or Newer, Arch, Debian Testing, SUSE Tumbleweed, Or Similar
    Gaphor Documentation Release 2.6.1 Arjan J. Molenaar Sep 29, 2021 INSTALLATION 1 Gaphor on Linux 3 2 Gaphor on macOS 7 3 Gaphor on Windows 9 4 Framework 15 5 Service Oriented Architecture 17 6 Event System 21 7 Modeling Languages 23 8 Style Sheets 27 9 Transaction support 33 10 Items and Elements 37 11 Modeling Language Core 39 12 Unified Modeling Language 41 13 Systems Modeling Language 47 14 Risk Analysis and Assessment Modeling Language 51 15 C4 Model 59 16 Saving and Loading models 61 17 Undo Manager 63 18 UML and SysML Data Model 65 19 Stereotypes 67 20 Data Model 69 21 Connection Protocol 71 22 External links 73 i Index 75 ii Gaphor Documentation, Release 2.6.1 Gaphor is a UML and SysML modeling application written in Python. It is designed to be easy to use, while still being powerful. Gaphor implements a fully-compliant UML 2 data model, so it is much more than a picture drawing tool. You can use Gaphor to quickly visualize different aspects of a system as well as create complete, highly complex models. This documentation is aimed at those who would be interested in making contributions to Gaphor. For download instructions, tutorials and how-to’s, please visit the Gaphor Website. If you’re into writing plug-ins for Gaphor you should have a look at our fabulous Hello world plug-in. INSTALLATION 1 Gaphor Documentation, Release 2.6.1 2 INSTALLATION CHAPTER ONE GAPHOR ON LINUX 1.1 Development Environment To set up a development environment with Linux, you first need a fairly new Linux distribution version.
    [Show full text]
  • Contents.Pdf
    Software architecture Study guide Software architecture Study guide Author: Jose Emilio Labra Gayo Course: 2020-21 Date: 25 May 2021 Web page: https://arquisoft.github.io/course2021.html 1.1 Presentation ...................................................................................................................... 3 1.2 Software Architecture – definitions .................................................................................... 4 1.3 Communicating software architecture ............................................................................... 5 1.4 Role of Software architect and stakeholders .................................................................... 7 1.4.1 Role of software architect ............................................................................................ 7 1.4.2 Stakeholders ............................................................................................................... 8 1.5 Quality attributes/architecture characteristics ................................................................... 9 1.5.1 Types of requirements................................................................................................. 9 1.5.2 Specifying quality attributes ........................................................................................ 9 1.5.3 Measuring quality attributes ...................................................................................... 10 1.6 Achieving software architecture .....................................................................................
    [Show full text]
  • Software Engineering Im Unterricht Der Hochschulen
    16. Workshop Tagungsband SEUH 2019 Software Engineering im Unterricht der Hochschulen 21. und 22. Februar 2019 Hochschule Bremerhaven Qualität im Fokus der Software Engineering Ausbildung Herausgeberschaft Veronika Thurner, Hochschule München Oliver Radfelder, Hochschule Bremerhaven Karin Vosseberg, Hochschule Bremerhaven Inhaltsverzeichnis Vorwort Veronika Thurner.............................................2 Software-Tests automatisch erzeugen - Frische Ansätze für Forschung, Praxis und Lehre Andreas Zeller, CISPA Helmholtz-Zentrum für Informationssicherheit, Saarbrücken........4 Meine Lehren aus 10 Jahren Forschung und Lehre als Säulen unseres Firmenwachstums Elmar Jürgens, CQSE GmbH, Garching b. München.........................5 Test Architects at Siemens Peter Zimmerer, Siemens AG, München................................6 Agile is real - Alltag in einem XP Office Eleonora Scherl, Volkswagen AG....................................7 UML in der Hochschullehre: Eine kritische Reflexion Jürgen Anke und Stefan Bente, HFT Leipzig & TH Köln.......................8 Formale Methoden in der Softwaretechnik-Vorlesung Bernd Westphal, Uni Freiburg...................................... 21 Stager: Simplifying the Manual Assessment of Programming Exercises Christopher Laß, Stephan Krusche, Nadine von Frankenberg und Bernd Bruegge, TU München 34 Software-Projektmanagement lernen ohne Projekt Mario Winter, TH Köln.......................................... 44 Future Skills: How to strengthen computational thinking in all software project roles Gudrun Socher,
    [Show full text]
  • High Level Documentation Software
    High Level Documentation Software Filarial and gynecological Heywood unknotted some demoralisation so warningly! Phyllotactical and stimulating Colin bestrewn, but Wolfgang experimentally boohooing her orthotone. Beamier Son caballed, his shammies predisposes outstripped bewilderingly. Below we want and high level design documentation! Documentation provides value is used to your entire system, you can expect more details pertaining to level software currently various user. In traditional software development projects there as comprehensive. High lounge is like architecture type designs where things like IPs are everything It's a 10k foot view Low quality is detailed network with IP addresses basically it's a sh run kinda detailed diagram. First imagine all they want to emphasize this camp about high-level design These kinds. I bring have a drawing tool like LucidChart and build the diagram on most fly from have. Requirements and attack Level Design HLD Document Shodor. 5 Development services handover the System Description Document to. Continuing performance problems into high level. Pathway to his degree Architectural Design Technology Architectural. Introduction to Software Development Life Cycle Documentation. CSE 331 Documenting a disease System Washington. All software documentation is that tells them better ways by tech advancements, everybody to level software components, both for regional manager already registered trademark of agile. Create simply beautiful professional software or infrastructure diagram in. Vision statement sometimes also referred to policy a Vision project Scope Document is best piece the software documentation containing a high-level. This is yes very high-level blueprint of your application such simply an. Slicing up its dynamics and high level software documentation.
    [Show full text]
  • A Model-Driven Architecture Based Evolution Method and Its Application in an Electronic Learning System
    A Model-Driven Architecture based Evolution Method and Its Application in An Electronic Learning System PhD Thesis Yingchun Tian Software Technology Research Laboratory De Montfort University October, 2012 To my husband, Delin Jing and my mum, Ning Zhang for their love and support Declaration Declaration I declare that the work described in this thesis was originally carried out by me during the period of registration for the degree of Doctor of Philosophy at De Montfort University, U.K., from October 2008 to December 2011. It is submitted for the degree of Doctor of Philosophy at De Montfort University. Apart from the degree that this thesis is currently applying for, no other academic degree or award was applied for by me based on this work. I Acknowledgements Acknowledgements For many years I had been dreaming about receiving a PhD, I would like to thank many people who helped me in achieving this dream in different ways since I undertook the work of this thesis. My deepest gratitude goes to my supervisor, Professor Hongji Yang, for his guidance, support and encouragement throughout my PhD career. He always provided me with many invaluable comments and suggestions for the improvement of the thesis. I am grateful for his leading role fostering my academic, professional and personal growth. Many thanks go to Professor Hussein Zedan and Doctor Wenyan Wu, for examining my PhD thesis and providing many helpful suggestions. My research career will benefit tremendously from the research methodologies to which Professor Zedan and Doctor Wu introduced me. I would like to thank colleagues in Software Technology Research Laboratory at De Montfort University, for their support and feedback, and for providing such a stimulating working atmosphere, Professor Hussein Zedan, Doctor Feng Chen, Doctor Amelia Platt, Doctor Antonio Cau, and many other colleagues.
    [Show full text]
  • José Miguel Mendes Canelha
    ndesCanelha é Miguel Me Miguel é Jos ITY EAL R IRTUAL V OR F José Miguel Mendes Canelha ENSATIONS S PROGRAMMABLE VIBROTACTILE SENSATIONS FOR VIRTUAL IBROTACTILE REALITY V ROGRAMMABLE ROGRAMMABLE P Dissertation in the context of the Master in Informatics Engineering, Specialization in Software Engineering, advised by Professor Jorge Cardoso and presented to Faculty of Sciences and Technology / Department of Informatics Engineering. March 2021 Faculty of Sciences and Technology Department of Informatics Engineering Programmable Vibrotactile Sensations for Virtual Reality José Miguel Mendes Canelha Dissertation in the context of the Master in Informatics Engineering, Specialization in Software Engineering, advised by Prof. Jorge Cardoso and presented to the Faculty of Sciences and Technology / Department of Informatics Engineering. March 2021 This page is intentionally left blank. Acknowledgments First of all, I would like to begin by expressing my deep gratitude to Professor Jorge Cardoso for the opportunity to participate in this exciting project and especially for the availability that he always had during the whole semester. Secondly, I would like to extend my gratitude to André Perrotta, not only for the opportunity to participate in the TherTactExo project but also for his availability to clarify any doubts that arose. To all my colleagues that I now have the pleasure to call friends, a big thank you for everything. Without you, this journey would not be the same. Finally, I want to thank from the bottom of my heart my parents, grandmother, and sister for always supporting me during this long journey. It is to you that I dedicate this work. Thank you! iii This page is intentionally left blank.
    [Show full text]
  • META for Microservices Getting Your Enterprise Migration in Motion Matt
    META for microservices Getting your enterprise migration in motion Matt McLarty, Chief Architect, Islay Bank @mattmclartybc Agenda Dealing with Complexity in the Digital Age META: Microservice-based Enterprise Transformation Approach Program Design System Design Service Design Foundation Design Practice Design Next Steps The Digital Age Digital Transformation • A movement to make every business a software business – Not just a business that uses software • The primary goals are innovation and optimization • Cloud computing, microservices, and APIs are technology enablers Digital Transformation Information Operationalization Process Optimization Data Digitization Digital Transformation Information Operationalization API Process Optimization API Data Digitization Barriers to Digital Transformation Highly-integrated applications and data Legacy technology, packaged solutions, skill gaps Large, hierarchical organizations Outsourcing, geographical distribution Industry regulations, shareholder/public scrutiny Complexity Dealing with Complexity Essential vs. Accidental Complexity Essential Complexity • The complexity of the software’s functional scope and the problems it solves (e.g. correlating and analyzing large amounts of data in real time) Accidental Complexity • The complexity of the software’s implementation details (e.g. the languages, processes and messages used to do the work) The Truth About Software Complexity “Many of the classical problems of developing software products derived from this essential complexity and its nonlinear increase with size.” - Fred Brooks, No Silver Bullet—Essence and Accident in Software Engineering Dealing with Complexity • Lesson #1 – Differentiate the complexity Abstraction, Hierarchy and Modularization • Herbert Simon, The • Edsger Dijkstra, Structure of • David Parnas, On the Architecture of Complexity, the “THE”-multiprogramming Criteria To Be Used in 1962 language, 1968 Decomposing Systems into Modules, 1972 Modularity “Modularity … is to a technological economy what the division of labor is to a manufacturing one.” - W.
    [Show full text]