DOCSLIB.ORG

Lean Architecture for Agile Software Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lean Architecture for Agile Software Development 1 Agile has long shunned up-front design. When Agilists force themselves to do up-front work, it usually is limited to a symbolic use of User Stories for requirements and metaphor for architecture, with much of the rest left to refactoring. Experience and formal studies have shown that incremental approaches Lean Architecture for to architecture can possibly lead to poor structure in the long term. This talk shows how to use domain analysis in a Lean way to build an architecture of form that avoids the mass of structure that usually Agile Software accompanies big up-front design, using only judicious documentation. It will also show how Development architecture can accommodate incremental addition of features using Trygve Reenskaug's new DCI (Data, Context and Interaction) approach, and how it maps elegantly onto C++ implementations. The Taking Architecture into the talk is based on the forthcoming Wiley book of the same title. Agile World 7 Platform hours (9:00 - 16:00), 82 Slides. James O. Coplien Gertrud&Cope, Mørdrup, Denmark Copyright ©2010, ©2011, ©2012, ©2013, ©2014, ©2015 James O. Coplien. All rights reserved. No Scrum Foundation portions of this material may be reproduced or redistributed in any form without prior written permission from James O. Coplien. In general you will find that I am generous about giving permission for use of these materials at no charge as long as the source is acknowledged. 2 In this course you will learn Lean architecture — not just as a pop phrase, but in terms of the Seminar Objectives grounding of the term "Lean" in the principles of the Toyota Way. You will lean the importance of mental models in software architecture, particularly as the concept underlies the Model-View-Controller architecture that has been the foundation of most interactive programs since the 1980s. You will learn • To be able to apply Lean principles of the basics and several advanced concepts of the DCI (Data-Collaboration-Interaction) architecture. domain architecture • To learn about the place of mental models in architecture • NOTE: This is a seminar, not a tutorial LeanArchitecture-DCI-OneDay-Master.key - 15 Sep 2015 3 Here is an outline for the day. Outline I. Definitions: Lean, Agile, Architecture... 4–7 II. The Agile Architecture Allergy 8–15 III. Mental Models & MVC 16–20 IV. More than that: Overall form 21–23 V. What the System Is, ABCs, Dictionary 24–36 VI. What-the-system-Does 37–38 VII. The OO Crisis and DCI 41–48 VIII. Roles and DCI Implementation 49–63 IX. DCI Advantages 65–66 X. The Process 67–73 XI. Advanced Topics (time permitting) 74–81 XII. Conclusion 82–84 4 Lean is a complicated framework of values and practices that has been proven in building complicated I. What is Lean? systems. It has been refined by Toyota in Japan and has spread to other companies like Canon and Honda in Japan. It is the main foundation of the Scrum production framework. ! A collection of principles and approaches A comprehensive treatment of Lean would be impossible here, and the concept is difficult for the – Value Stream Western world. Here, we list some of the popular trappings of Lean as understood in the West. – Reducing waste (time, material) – Reducing inconsistency (with communication) The goals are reduced waste and higher value. – Reducing unevenness (planning & process) – Up-front planning – Single-piece continuous flow – Reduce inventory – Kaizen ! Results in – Reduced inventory – Reduced waste – Higher Value LeanArchitecture-DCI-OneDay-Master.key - 15 Sep 2015 5 In this course, by the term "Agile" we mean it as defined by the Agile Manifesto, above. What is Agile? We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: – Individuals and interactions over processes and tools – Working software over comprehensive documentation – Customer collaboration over contract negotiation – Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. • Kent Beck • James Grenning • Robert Cecil Martin • Mike Beedle • Jim Highsmith • Steve Mellor • Arie van Bennekun • Andrew Hunt • Ken Schwaber • Alistair Cockburn • Ron Jefries • Jef Sutherland • Ward Cunningham • Jon Kern • Dave Thomas • Martin Fowler • Brian Marick © 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice. 6 This is a seminar about Lean and Agile architecture. What is architecture? Throughout the ages and even in the field of building construction, architecture has always been about form. Form is the What is Architecture? essence of structure. The word in English for a piece of material, into which molten metal or plastic are poured or injected to make a new something, is called a form. We focus on form because if we look at ! Architecture is the essence of structure: form structure, it actually makes it difficult to understand the essence by adding a lot of detail which is – Structure obfuscates form! irrelevant early in design. ! Lean architecture: just-in-time delivery of functionality, just-in-time pouring material into What, then, is Lean Architecture? The principles of Lean include just-in-time delivery, careful the forms organization, up-front planning, avoiding waste, and overall consistency. Architecture is in principle – Reduces long-term cost – Increases harmony: remove muri about consistency. If we have a consistent system early on that is stable over time, it avoids rework ! Agile architecture: one that supports change, and waste. That takes up-front planning and careful organization. That in place, we have a guide — a end-user interaction, discovery, and ease of form — into which we can write code when the need comes along. comprehension (of functionality) – Rapid delivery A good architecture supports Agile development. A good architecture is Agile if it supports change and – Increased revenues has just enough documentation to do the job — the documentation that really makes a difference. Good architecture supports the Agile values: support for change, a good model that supports the end user’s mental model of the system and that helps the developer’s discovery process. Here, we will focus on helping the developer reason about functionality in the code — functionality that reflects the end user wishes. LeanArchitecture-DCI-OneDay-Master.key - 15 Sep 2015 7 There are very few fundamental activities in software development; here they are. Analysis is about Architecture in the understanding the system, and is rather independent of the problems we want to solve. Problem Development Process definition sets the direction for design in the context of the analysis. Design solves the problem, and testing evaluates the degree to which we have solved the problem. We build a product called software, Analysis and most of that is code. The software has a form that we call its architecture. Understanding the System Architecture Design Solving the Problem(s) Code Problem Definition Articulating the Problem(s) Testing Did we solve the problem? 8 In an XP world, the air is full of singing User Stories and there is a beautiful and simple landscape. All II. YAGNI...? is well and the future looks bright. User Stories Tacit LeanArchitecture-DCI-OneDay-Master.key - 15 Sep 2015 9 The problem is that most of the system mass comes not from the explicit knowledge of system II. YAGNI...? functionality, but from the tacit knowledge about the form of the implementation and of the assumptions behind its functioning. These are often the realm of architecture. We often call it domain knowledge. Image by Ralph Clevenger, 1999. User Stories Tacit Knowledge 10 Mads Thiessen of Nordija relates that his project failed to do an up-front architecture, and used YAGNI The Agile Allergy to techniques to create a set-top box architecture based on channel services. When the architecture had Architecture to be converted to accommodate video on demand, it required a major re-work of the interface code and business logic. Marko Taipale of European Game and Entertainment Technology Ltd. Related (23 November, 2007, Helsinki, Finland) that they consciously started a project from scratch to use TDD to create an architecture — even though they thought they knew what the architecture would be. Six months later, “Because we had no up- “We spent 6 months their effort proved their initial hunch to be correct. front architecture, we didn’t doing TDD and ended foresee the need for video- on-demand services and with the architecture we originally knew that Long-term Cost incurred a great cost implementing it” — Mads we would get” — Thiessen, Nordija Marko Taipale, EGET Architectural Effort LeanArchitecture-DCI-OneDay-Master.key - 15 Sep 2015 11 Test-driven development is a design technique, intended to replace big up-front design in XP. The Architecture driven by Tests? historic progression started with an article by Kent Beck [Bec1994] that described how Smalltalk had suffered because it lacked a testing culture, and the article proposed how to solve the problem with a test framework. That framework evolved into the form it took in an article joint with Eric Gamma in ! The XP approach: Test-Driven Design 1998, which today we know as jUnit. [BeGa1998] Test-first was part of XP in 1999 [Bec1999], and TDD – First, write the test; then run it; then write the techniques matured by 2002 [Bec2002]. code; then run the test again; “refactor” until it works The idea is that tests shape your architecture. That could be true in the days when function — which is – No code without a test first what tests are about — dominated system structure. That was true in the day of batch programming ! This worked fine in the days when the system shape followed the imperative flow and card readers.
Load more

Recommended publications
  • The Role of “Roles” in Use Case Diagrams
    Lecture Notes in Computer Science 1 The Role of “Roles” in Use Case Diagrams Alain Wegmann1, Guy Genilloud1 1 Institute for computer Communication and Application (ICA) Swiss Federal Institute of Technology (EPFL) CH-1015 Lausanne, Switzerland icawww.epfl.ch {alain.wegmann, guy.genilloud}@epfl.ch Abstract: Use cases are the modeling technique of UML for formalizing the functional requirements placed on systems. This technique has limitations in modeling the context of a system, in relating systems involved in a same busi- ness process, in reusing use cases, and in specifying various constraints such as execution constraints between use case occurrences. These limitations can be overcome to some extent by the realization of multiple diagrams of various types, but with unclear relationships between them. Thus, the specification ac- tivity becomes complex and error prone. In this paper, we show how to over- come the limitations of use cases by making the roles of actors explicit. Interest- ingly, our contributions not only make UML a more expressive specification language, they also make it simpler to use and more consistent. 1 Introduction The Unified Modeling Language (UML), standardized by the Object Management Group (OMG) in 1996, aims at integrating the concepts and notations used in the most important software engineering methods. UML is today widely used by the software development community at large. While the bulk of the integration of the concepts is completed, there are still improvements to be made in their consistency. Such im- provements could increase the expressive power of UML while reducing its complex- ity. System design frequently starts with business modeling, i.e.
    [Show full text]
  • APPLYING MODEL-VIEW-CONTROLLER (MVC) in DESIGN and DEVELOPMENT of INFORMATION SYSTEMS an Example of Smart Assistive Script Breakdown in an E-Business Application
    APPLYING MODEL-VIEW-CONTROLLER (MVC) IN DESIGN AND DEVELOPMENT OF INFORMATION SYSTEMS An Example of Smart Assistive Script Breakdown in an e-Business Application Andreas Holzinger, Karl Heinz Struggl Institute of Information Systems and Computer Media (IICM), TU Graz, Graz, Austria Matjaž Debevc Faculty of Electrical Engineering and Computer Science, University of Maribor, Maribor, Slovenia Keywords: Information Systems, Software Design Patterns, Model-view-controller (MVC), Script Breakdown, Film Production. Abstract: Information systems are supporting professionals in all areas of e-Business. In this paper we concentrate on our experiences in the design and development of information systems for the use in film production processes. Professionals working in this area are neither computer experts, nor interested in spending much time for information systems. Consequently, to provide a useful, useable and enjoyable application the system must be extremely suited to the requirements and demands of those professionals. One of the most important tasks at the beginning of a film production is to break down the movie script into its elements and aspects, and create a solid estimate of production costs based on the resulting breakdown data. Several film production software applications provide interfaces to support this task. However, most attempts suffer from numerous usability deficiencies. As a result, many film producers still use script printouts and textmarkers to highlight script elements, and transfer the data manually into their film management software. This paper presents a novel approach for unobtrusive and efficient script breakdown using a new way of breaking down text into its relevant elements. We demonstrate how the implementation of this interface benefits from employing the Model-View-Controller (MVC) as underlying software design paradigm in terms of both software development confidence and user satisfaction.
    [Show full text]
  • Software Architecture Bertrand Meyer Lecture 7: Patterns, Observer, MVC
    References Last update: 18 April 2007 Erich Gamma, Ralph Johnson, Richard Helms, John Software Architecture Vlissides: Design Patterns, Addison-Wesley, 1994 Bertrand Meyer Jean-Marc Jezequel, Michel Train, Christine Mingins: Design Patterns and Contracts, Addison-Wesley, 1999 ETH Zurich, March-July 2007 Karine Arnout: From Patterns to Components, 2004 ETH Lecture 7: Patterns, Observer, MVC thesis, http://se.inf.ethz.ch/people/arnout/patterns/ Patterns in software development Benefits of design patterns Design pattern: ¾ Capture the knowledge of experienced developers ¾ A document that describes a general solution to a ¾ Publicly available repository design problem that recurs in many applications. ¾ Common pattern language ¾ Newcomers can learn & apply patterns Developers adapt the pattern to their specific application. ¾ Yield better software structure ¾ Facilitate discussions: programmers, managers Some design patterns A pattern is not a reusable solution Creational Behavioral Solution to a particular recurring design issue in a ¾ Chain of Responsibility ¾ Abstract Factory particular context: ¾ Builder ¾ Command (undo/redo) ¾ Interpreter ¾ Factory Method ¾ “Each pattern describes a problem that occurs over ¾ Iterator ¾ Prototype and over again in our environment, and then describes ¾ Singleton ¾ Mediator ¾ Memento the core of the solution to this problem in such a way Structural ¾ Observer that you can use this solution a million times over, ¾ Adapter ¾ State without ever doing it the same way twice.” ¾ Bridge ¾ Strategy Gamma et al.
    [Show full text]
  • The Unified Modeling Language Reference Manual
    The Unified Modeling Language Reference Manual The Unified Modeling Language Reference Manual James Rumbaugh Ivar Jacobson Grady Booch ADDISON-WESLEY An imprint of Addison Wesley Longman, Inc. Reading, Massachusetts • Harlow, England • Menlo Park, California Berkeley, California • Don Mills, Ontario • Sydney Bonn • Amsterdam • Tokyo • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial caps or all caps. Unified Modeling Language, UML, and the UML cube logo are trademarks of the Object Management Group. Some material in this book is derived from the Object Management Group UML Specification documentation. Used by permission of the Object Management Group. The authors and publisher have taken care in the preparation of this book but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers discounts on this book when ordered in quantity for special sales. For more information, please contact: AWL Direct Sales Addison Wesley Longman, Inc. One Jacob Way Reading, Massachusetts 01867 (781) 944-3700 Visit AW on the Web: www.awl.com/cseng/ Library of Congress Cataloging-in-Publication Data Rumbaugh, James. The unified modeling language reference manual / James Rumbaugh, Ivar Jacobson, Grady Booch. p. cm. — (The Addison-Wesley object technology series) Includes bibliographical references and index.
    [Show full text]
  • 1 Introduction We Introduce a New Paradigm for the Understanding and Coding of Computer Programs That We Call DCI - Data, Context, Interaction
    DCI as a New Foundation for Computer Programming Trygve Reenskaug, James O. Coplien Dept. of Informatics, Gertrud & Cope University of Oslo Copenhagen Norway Denmark (“Trygve”) (“Cope”) ver.1.3 - Last modified FrameMaker version: November 23, 2013 2:48 pm draft.1.4.2 - FrameMaker version: Updated and edited from “ver1.3.1.bvs.fdbk.docx” draft.1.4.5 - Minor updates. (.fm + .pdf) draft 1.5.1 - Incorporate comments from Risto draft 1.6.1 - 24.01.07-’Data’ names a kind of projection, not a set of objects. ‘base object’ has been renamed to ‘root object’. draft 1.7 - 14.01.09 - Updated 'an object is … ' and minor changes. Abstract After more than 60 years with computers, hundreds of millions of people are dexterous at using them. Yet, the source code for a simple app is incomprehensible to almost all. We claim this is wasteful and passé -- Wasteful, because many valuable opportunities are lost; passé because computer programming is rapidly becoming an essential part of primary and secondary education. We introduce a new paradigm for computer programming called DCI - Data, Context, Interaction. DCI brings programming to the level of everyday concepts and activities. The professional programmer can attack complex problems without undue additional complexity. The software maintainer can preserve system integrity by understanding and honoring the system architecture long after the originators have moved on to other projects. DCI can be embedded in different programming languages that are specialized for different purposes. The DCI concepts can become a unifying foundation for programming in school curricula. DCI specifies a program as seen in two orthogonal projections; the Data projection describes system state and the Context projection system behavior.
    [Show full text]
  • An Empirical Study on Code Comprehension: DCI Compared to OO
    Rochester Institute of Technology RIT Scholar Works Theses 8-3-2016 An empirical study on code comprehension: DCI compared to OO Hector A. Valdecantos [email protected] Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Valdecantos, Hector A., "An empirical study on code comprehension: DCI compared to OO" (2016). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. ROCHESTER INSTITUTE OF TECHNOLOGY MASTER THESIS An empirical study on code comprehension: DCI compared to OO Author: Supervisor: Héctor A. VALDECANTOS Dr. Mehdi MIRAKHORLI A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Software Engineering in the B. Thomas Golisano College of Computing and Information Sciences Department of Software Engineering Rochester, New York August 3, 2016 i The thesis “An empirical study on code comprehension: DCI compared to OO” by Héctor A. VALDECANTOS, has been examined and approved by the following Exami- nation Committee: Dr. Mehdi Mirakhorli Thesis Committee Chair Assistant Professor Dr. Meiyappan Nagappan Assistant Professor Dr. Scott Hawker SE Graduate Program Director Associate Professor ii ROCHESTER INSTITUTE OF TECHNOLOGY Abstract B. Thomas Golisano College of Computing and Information Sciences Department of Software Engineering Rochester, New York Master of Science in Software Engineering An empirical study on code comprehension: DCI compared to OO by Héctor A. VALDECANTOS Comprehension of source code affects software development, especially its main- tenance where reading code is the most time consuming performed activity.
    [Show full text]
  • The Common Sense of Object Oriented Programming
    The Common Sense of Object Oriented Programming Trygve Reenskaug Department of Informatics, University of Oslo, Norway Home: http://folk.uio.no/trygver E-mail: Abstract. The essence of object orientation is that networks of collaborating objects work together to achieve a common goal. Surely, the common sense of object oriented programming should reflect this essence with code that specifies how the objects collaborate. Our industry has, unfortunately, chosen differently and code is commonly written in terms of classes. A class tells us everything about the properties of the individual objects that are its instances. It does not tell us how these instances work together to achieve the system behavior. The result is that our code does not reveal everything about how a system will work. This is clearly not satisfactory, and we need a new paradigm as the foundation for more expressive code. We propose that DCI (Data-Context-Interaction) is such a paradigm. DCI separates a program into different perspectives where each perspective focuses on certain system properties. Code in the Data perspective specifies the representation of stand-alone objects. Code in the Context perspective specifies runtime networks of interconnected objects. Code in the Interaction perspective specifies how the networked objects collaborate to achieve the system behavior. BabyIDE is an interactive development environment that supports the DCI paradigm with specialized browsers for each perspective. These browsers are placed in overlays within a common window so that the programmer can switch quickly between them. DCI with BabyIDE marks a new departure for object oriented programming technology. It opens up a vista of new and interesting product opportunities and research challenges.
    [Show full text]
  • Introducing the Smalltalk-80 System, August 1981, BYTE Magazine
    Introducing the Sntalltalk-80 Systelll Adele Goldberg Manager, Learning Research Group Xerox Palo Alto Research Center 3333 Coyote Hill Rd Palo Alto CA 94304 It is rare when one can indulge in one's prejudices with relativ e impunity, poking a bit of good humored fun to make a point. ith this statement, W Carl Helmers opened his remarks in the · "About the Cover" section of the August 1978 issue of BYTE. The issue was a special on the language Pascal, so Helmers took of the opportunity to present Pascal's triangle as drawn cover design presents by artist Robert Tinney. ust such an opportuni­ The primary allegory of t depicts the clouds the cover was' the inver­ clearing from around sion of the Bermuda the kingdom of Small talk, Triangle myth to show and, with banners stream­ smooth waters within the ing, the Small talk system area labeled " Pascal's is taking flight into the Triangle ." In explaining mainstream of the com­ the allegory, Helmers puter programming com­ g uided the traveler munity. This cover was through the FORTRAN also executed by Robert Ocean, the BASIC Sea, Tinney, to the delight of around the Isle of BAL, and up to the Land of Small talk. the Learning Research Group (LRG ) of the Xerox Palo Alto Research Center. LRG is the group that has de­ Trav eling upward (in the picture) through heavy seas signed, implemented, and evaluated several generations w e come to the pinnacle, a snow white island rising like of Small talk over the past ten years.
    [Show full text]
  • Domain Engineering Methodologies Survey Cordet
    DOMAIN ENGINEERING METHODOLOGIES SURVEY CORDET Internal Code: GMVSA 20580/07 Versión: Issue 1 Date: 26/07/2007 GMV AEROSPACE AND DEFENCE S.A.. © GMV, 2007; all rights reserved. Isaac Newton 11, PTM Tres Cantos, 28760 Madrid Tel. +34 918072100, Fax. +34 918072199 www.gmv.com . THIS PAGE IS INTENTIONALLY LEFT IN BLANK Code: GMV-CORDET-WP202-RP-001 Date: 26/07/2007 Version: Issue 1 Page: 3 de 38 Prepared by: Elena Alaña Ana Isabel Rodríguez Approved by: Ana Isabel Rodríguez Project Manager Authorized by: Ana Isabel Rodríguez Project Manager Code: GMV-CORDET-WP202-RP-001 Date: 26/07/2007 Version: Issue 1 Page: 4 de 38 DOCUMENT STATUS SHEET Version Date Pages Changes Issue 1 Draft A 29/05/2007 29 First draft version Issue 1 Draft B 13/06/2007 29 Second draft version Issue 1 Draft C 21/06/2007 30 Third draft version. Issue 1 Draft D 03/07/2007 30 Fourth draft version. Issue 1 26/07/2007 38 First issue of the report. Updated according to MoM "CORDET-MoM-DKMR- 06072007“, [RD.64]. CORDET © GMV, 2007; all rights reserved. Domain Engineering Methodologies Survey Code: GMV-CORDET-WP202-RP-001 Date: 26/07/2007 Version: Issue 1 Page: 5 de 38 TABLE OF CONTENTS 1. INTRODUCTION................................................................................................................................7 1.1. PURPOSE AND SCOPE 7 1.2. APPLICABLE DOCUMENTS 7 1.3. REFERENCE DOCUMENTS 7 2. METHODOLOGIES...........................................................................................................................11 2.1. DOMAIN ENGINEERING PROCESS 11 2.1.1. DOMAIN ANALYSIS .........................................................................................................................11 2.1.2. DOMAIN DESIGN ............................................................................................................................12 2.1.3. DOMAIN IMPLEMENTATION .............................................................................................................12 2.2. DOMAIN ENGINEERING METHODS 12 2.2.1.
    [Show full text]
  • Mastering-Javascript
    www.allitebooks.com Mastering JavaScript Design Patterns Discover how to use JavaScript design patterns to create powerful applications with reliable and maintainable code Simon Timms BIRMINGHAM - MUMBAI www.allitebooks.com Mastering JavaScript Design Patterns Copyright © 2014 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: November 2014 Production reference: 1151114 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78398-798-6 www.packtpub.com www.allitebooks.com Credits Author Project Coordinator Simon Timms Rashi Khivansara Reviewers Proofreaders Amrita Chaturvedi Simran Bhogal Philippe Renevier Gonin Lawrence A. Herman Pedro Miguel Barros Morgado Elinor Perry-Smith Mani Nilchiani Indexer Commissioning Editor Hemangini Bari Kunal Parikh Graphics Acquisition Editor Sheetal Aute Meeta Rajani Ronak Dhruv Valentina D'silva Content Development Editor Disha Haria Sweny M.
    [Show full text]
  • The DCI Architecture
    The DCI Architecture Lean and Agile at the Code Level James O. Coplien Gertrud&Cope, Mørdrup, Denmark Scrum Training Institute The misguided, CASE-heavy practices of the 1980s fueled the proto-Agile rhetoric of the 1990s and survived full-force into the advent of Agile practices such as Scrum and XP in the past decade. Part of that rhetoric has been to go as far from the sins of the 1980s as possible by discarding up-front requirements (instead we have a promise for a future conversation between a developer and a customer) and architecture (instead, we have had a succession of short-lived ideas including "metaphor" and TDD). Experience and recent research have both borne out the value of architecture in software development in general, as well as its value in sustaining high velocity and change resiliency in Agile projects. In this talk, Agile expert Jim Coplien will provide tips for putting architecture back into your Agile project without dragging it back into the dark ages -- and all within the framework of the Agile Manifesto. 1 hour -- 4 minutes per slide, 15 slides Copyright ©2008, ©2009 Gertrud&Cope. All rights reserved. E-mail: [email protected] What is architecture? Architecture is the essence of structure: form – Structure obfuscates form! Lean architecture: just-in-time delivery of functionality, just-in-time pouring material into the forms Agile architecture: one that supports change, end-user interaction, discovery, and ease of comprehension (of functionality) 2 Let’s start with a few basic definitions to establish common ground. This is a talk about Lean and Agile architecture.
    [Show full text]
  • M´Aster Universitario En Ingeniería De
    MASTER´ UNIVERSITARIO EN INGENIER´IA DE TELECOMUNICACION´ TRABAJO FIN DE MASTER´ INTEGRACION´ DIGITAL DE PROCESOS ADMINISTRATIVOS Y ACADEMICOS´ DE LA E.T.S.I.T JAVIER CONDE D´IAZ 2020 MASTER´ UNIVERSITARIO EN INGENIER´IA DE TELECOMUNICACION´ TRABAJO FIN DE MASTER´ T´ıtulo: Integraci´ondigital de procesos administrativos y acad´emicos de la ETSIT Autor: D. Javier Conde D´ıaz Tutor: D. Gabriel Huecas Fern´andez-Toribio Departamento: Departamento de Ingenier´ıade Sistemas Telem´aticos MIEMBROS DEL TRIBUNAL Presidente: D. |{ Vocal: D. |{ Secretario: D. |{ Suplente: D. |{ Los miembros del tribunal arriba nombrados acuerdan otorgar la calificaci´onde: Madrid, a ...... de .............. de 2020 UNIVERSIDAD POLITECNICA´ DE MADRID ESCUELA TECNICA´ SUPERIOR DE INGENIEROS DE TELECOMUNICACION´ MASTER´ UNIVERSITARIO EN INGENIER´IA DE TELECOMUNICACION´ TRABAJO FIN DE MASTER´ INTEGRACION´ DIGITAL DE PROCESOS ADMINISTRATIVOS Y ACADEMICOS´ DE LA E.T.S.I.T Javier Conde D´ıaz 2020 Resumen En la ´ultimad´ecada,la evoluci´onde la tecnolog´ıaha permitido una profunda transformaci´ondigital en las empresas e instituciones que han visto como los datos se han convertido en una de las principales fuentes de valor y ventaja competitiva. Como consecuencia, la digitalizaci´onse ha convertido en uno de los principales objetivos actuales. Muestra de ello es la iniciativa \Una Agenda Digital para Europa", recogida en la Estrategia Europa 2020, en la que la Comisi´onEuropea aboga por la digitalizaci´onen todos los ´ambitos de la sociedad. El Trabajo de Fin de M´asterse centrar´aen contribuir a la transformaci´ondigital de la Escuela T´ecnicaSuperior de Ingenieros de Telecomunicaci´on(ETSIT). Partiendo de un estudio realizado en el a~no2018 en la escuela, se dise~nar´ae implementar´auna soluci´oncompleta en la que el resultado es un sistema de portales web y un conjunto de aplicaciones, accesibles desde dichos portales, que representan la digitalizaci´onde procedimientos llevados a cabo en la ETSIT.
    [Show full text]