DOCSLIB.ORG

A Software Modeling Language for the Model-View-Controller Design Pattern

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Software Modeling Language for the Model-View-Controller Design Pattern MVCLang: A Software Modeling Language for the Model-View-Controller Design Pattern Mert Ozkaya1 and Irem Fidandan2 1Department of Computer Engineering, Yeditepe University, Istanbul, Turkey 2Eryaz Software, Istanbul, Turkey Keywords: Model-View-Controller (MVC), Software Modeling Language, Model Analysis, Code Generation, ASP.NET. Abstract: The Model-View-Controller (MVC) software design pattern promotes separating software systems into the model, view, and controller elements. The views represent the user-interfaces, the models represent the system data, and the controllers handle the requests sent by the views and coordinate the interactions between views and models. While many software frameworks are available for the MVC-based software developments, no any attempt have been made on increasing the level of abstraction for the MVC developments and provide a model-based approach. Indeed, none of the high-level software modeling languages support the MVC design pattern. So, we propose in this paper a visual, MVC-based modeling language called MVCLang, which enables to model MVC-based software architectures that can be easily analysed and implemented. MVCLang is supported with an Eclipse-based prototype toolset for specifying the visual MVC architectures and analysing them for a number of wellformedness rules. MVCLang’s toolset can further produce ASP.NET MVC code that reflects the architectural design decisions. We evaluated MVCLang on a software company that offers e-commerce solutions. Therein, 5 developers used MVCLang for their e-commerce project developments and provided feedback for a set of pre-determined questions. 1 INTRODUCTION entities that can be used for creating understandable software systems (Burbeck, 1987). Later on, MVC Model-View-Controller (MVC) has been proposed by has gained huge popularity in the area of web applica- Trygve Reenskaug in the late seventies as a software tions development, and many web technologies (e.g., design pattern, which aims at modularising the soft- .NET, JavaScript, and Php) nowadays offer their own ware systems into the model, view, and controller el- frameworks for the MVC-based web developments. ements and maximising their understandability and Moreover, as discussed in Section 6, many researches analysability (Reenskaug, 2003). Models represent have been conducted on extending MVC for various the system data, views represent the pictorial forms domain problems (e.g., secure systems, multi-agent on which the users see the model data, and controllers systems, and service-oriented systems). represent the interactions between the views and mod- However, the current MVC frameworks force els (i.e., how the models need to be used and manipu- practitioners to work on the software implementation lated upon any user requests via the views). Separat- and deal with the coding of the view, model, and ing the software development into different concerns controller units. While the MVC frameworks pro- maximises the cohesion and minimises the coupling, vide many re-usabilities, developers are still expected which is one of the main principals of quality cod- to deal with low-level programming issues that may ing and aids in reducing the development and mainte- require expertise on particular software languages nance cost. Also, separating the views from the busi- and technologies. Therefore, the effort required for ness logic and data enables multiple users (e.g., web developing and testing the model, view, and con- designers and developers) to work in parallel, which troller elements separately may be unexpectedly high. reduces the development time. Besides, other (probably non-technical) stakeholders MVC has first been applied in the Smalltalk 80 (e.g., customers) may not be involved in the develop- language in the late eighties, where the model, view, ment and testing process, which may negatively af- and controller concepts are represented as abstract fect the quality of software systems. To avoid these, 75 Ozkaya, M. and Fidandan, I. MVCLang: A Software Modeling Language for the Model-View-Controller Design Pattern. DOI: 10.5220/0009571400750083 In Proceedings of the 15th International Conference on Software Technologies (ICSOFT 2020), pages 75-83 ISBN: 978-989-758-443-5 Copyright c 2020 by SCITEPRESS – Science and Technology Publications, Lda. All rights reserved ICSOFT 2020 - 15th International Conference on Software Technologies Figure 1: The meta-model of the MVCLang language. one could enhance the level of abstraction by apply- ator translates MVC models into software code using ing software modeling, which promotes specifying the ASP.NET MVC framework. high-level software models that consist of abstract, In the rest of this paper, we initially introduce the explanatory statements without any platform-specific MVCLang language (i.e., syntax and semantics) and implementation details(Seidewitz, 2003). The high- then introduce MVCLang’s prototype toolset (i.e., the level models are potentially useful for the commu- model editor, analyser, and code generator). Next, we nication of the design decisions with different stake- illustrate MVCLang via the sports store case-study holders who can also contribute to the application de- and evaluate the language in industry. Lastly, we pro- velopment and testing despite having very little (or vide the discussions of the related works. no) experience in programming. The models can be useful for the early detection of the design errors that may otherwise go undetected until the system deploy- 2 OVERVIEW OF MVCLang ment and cause huge maintenance cost. The models that are analysed to be correct can be used for gener- MVCLang offers a visual notation set for the model- ating quality code that reflect the modeled design de- ing of MVC-based software architectures, which are cisions. However, as discussed in Section 6, software separated into four packages: model, view, controller, modeling has not yet been systematically employed and MVC. While the model, view, and controller for the development of MVC-based software appli- packages are created for modeling the model, view, cations. While many approaches have extended the and controller elements of the MVC architectures, the MVC design pattern for different needs, no any mod- MVC package is created for establishing the relation- eling platform consisting of a modeling language (i.e., ships between model, view, and controller elements the notation set) and its toolset has been proposed so that are modeled in their own packages. Figure 1 far for the MVC-based modeling, analysis, and im- shows MVCLang’s meta-model, which describes the plementation of software systems. modeling concepts composing each package and their The goal of this paper is to propose a software relationships. The visual symbols that are associated modeling language called MVCLang for the MVC- with the modeling concepts are depicted in Figure 2, based architecture modeling of software systems. Figure 3, Figure 4, and Figure 5, which are for the MVCLang offers a visual notation set for the specifi- model, view, controller, and MVC packages respec- cations of the model, view, and controller elements of tively. In the rest of this section, we discuss for each software systems and their relationships. MVCLang modeling package the syntax and semantics of the is supported with an Eclipse-based prototype toolset. language elements informally. That is, we describe The toolset’s modeling editor enables to create the vi- the visual symbols for the language concepts and their sual MVC architectures and check correctness for a relationships, the constituting parts of the language set of wellformedness rules. The toolset’s code gener- concepts and relationships, and how those concepts 76 MVCLang: A Software Modeling Language for the Model-View-Controller Design Pattern Figure 2: The abstract and concrete syntax for MVCLang’s model package. and relationships can be used and composed together to create meaningful specifications for each package. 2.1 Model Package As depicted in Figure 1, a model package is specified with a set of model elements that have association re- Figure 3: The abstract and concrete syntax for MVCLang’s lationships between each other. Models represent a view package. dataset to be stored and manipulated by the software system, which may be implemented as database ta- a link displayed on the view’s user interface, which bles. Figure 2 displays the concrete symbols that cor- can be clicked by the user. An action-link is spec- respond to the abstract concepts given in Figure 1. So, ified with the (i) name, (ii) request type, and (iii) each model consists of a set of properties that repre- http method.The request type can be an HTTP request sent the model data and are specified with the data that prompts the controller to return with a view or type and its name. The data type can be either inte- an AJAX request that do not prompt for a new view. ger, boolean, string, or double. The association rela- The http method can be GET or POST. A form mes- tionship is used to relate the data of different model sage represents the action that results from a form dis- datasets that are dependent on each other (e.g., the played on the view and transmits the data filled in the company and employee datasets). The association form to the controller. The form messages are speci- relationship is specified with the multiplicities and fied with the (i) form name, (ii) request type, and (iii) roles, where multiplicities can be one-to-one, one-to- http method. many, many-to-one, and many-to-many and role de- scribes the how each dataset acts in the relationship. 2.2 View Package Figure 3 shows the symbols for the view package. The partial view represents any re-usable view con- tent(s) that can be used (or rendered) as part of other view(s). The layout view represents the com- mon user-interface parts (e.g., the footer and header), which are shared among different views for offering a consistent layout appearenace.
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]
  • 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.
    [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]