DOCSLIB.ORG

Deriving Best Practices from Development Methodology Base (Part 1)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Deriving Best Practices from Development Methodology Base (Part 1) International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 6, August - 2012 Deriving Best Practices from Development Methodology Base (Part 1) Bhushan Thakare Bhushan Bhokse Laxmi Thakare Assistant Professor Assistant Professor Assistant Professor STES Sinhgad Academy of MAEER Maharashtra Academy MAEER Maharashtra Academy Engineering, Kondhwa, Pune, of Engineering, Alandi (D), of Engineering, Alandi (D), Maharashtra, India Pune, Pune, Maharashtra, India Maharashtra, India ABSTRACT abstract form, a process is a sequence of steps—sometimes deprecatingly called a recipe—that aims to guide its users in There are abundant methodologies for the product applying the modelling language for accomplishing a set of development. Out of which only few could have renowned software development tasks. The process thus acts as the because for their universal importance. But some system or dynamic, behavioural component of the methodology, process cannot follow general methodology. Hence some governing the technical development and management sub process follows specific methodology e.g., XP follows Agile processes, and therefore encompassing the phases, methodology. Hence we surveyed a detailed review of procedures, rules, techniques, and tools prescribed by the existing software development methodologies in which methodology, as well as the issues pertaining to mainly on their development processes. The descriptions of documentation and project management.. methodologies fashioned aimed to provide an abstract and structured description in a way that facilitates their elaborate And in the next paper named Deriving Best Practices from analysis for the purposes of improving understanding, and Development Methodology Base (Paper 2) will see ASD making it easier to tailor, select, and evaluate the processes. (Adaptive Software Development), BON (Business Object Notation), Catalysis, Coad and Yourdon, Crystal, Doors General Terms (Design of Object Oriented Real Time Systems), DSDM We are providing a comprehensive review of the processes of (Dynamic Systems Development Method), EROOS (Entity a selection of methodologies. The methodologies reviewed in this article are: Relationship based Object-Oriented Specification), FDD (Feature Driven Development) , FOOM (Functional and Booch, CBD/e (Component Based Development), CRC Object Oriented Methodology) , Hodge-Mock, ICONIX, (Class-Responsibility-Collaborator), Demeter, dX, EUP IDEA (Intelligent Database Environment for Advanced (Enterprise Unified Process), Fusion, HOOD (Hierarchical Object-Oriented Design), Octopus, OMT (Object Modeling Applications), MOSES (Modeling Software and Platform Technique), OOBE (Object-Oriented Business Engineering), Architecture in UML-2 for Simulation-based Performance OOram, OOSE (Object-Oriented Software Engineering), Analysis), MERODE (Model Driven, Existence Dependency OPEN (Object-Oriented Process, Environment and Notation), Relation, Object-Oriented Development), Object COMX OSA (Object-Oriented System Analysis), RDD (Object Communicating X-Machines), Objecteering, OEP (Responsibility-Driven Design), ROPES (Rapid Object- (Object Engineering Process), OOIE (Object-Oriented Oriented Process for Embedded Systems), Scrum, Syntropy and XP (Xtreme Programming) etc. Information Engineering), OOHDM (Object-Oriented Hypermedia Design Model),OOSC (Object-Oriented Keywords Software Construction),OOSP (Object-Oriented Software Methodology, Phases, Software Development, Object Process), OPM (Object-Process Methodology), RAD (Rapid Oriented, Design, Management, Software Engineering. Application Development), RUP (Rational Unified Process)/ 1. INTRODUCTION UML, SDL (Specification and Description Language) / A Software Development Methodology is a framework for SOMT (SDL-oriented Object Modeling Technique), applying software engineering practices to develop software- Shlaer and Mellor methodologies. intensive systems. Software development methodologies provide the means for timely and orderly execution of the 2. LITERATURE SURVEY various finer-grained techniques and methods of software 2.1 Booch: engineering. A software development methodology can be defined as ―a recommended collection of phases, procedures, Booch has modeled object-oriented design as a repeating rules, techniques, tools, documentation, management, and process (referred to as ―The Micro Process‖) within a training used to develop a system‖. lifecycle-level repeating process (referred to as ―The Macro Whereas the modelling language provides developers with a Process‖). means to model the different aspects of the system, the a) Macro Process (Booch). The macro process serves as a process determines what activities should be carried out to controlling framework for the micro process. The macro develop the system, in what order, and how. In its most process tends to follow these steps: www.ijert.org 1 International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 6, August - 2012 (1) Conceptualization: Establish core requirements for CRC cards characterize objects by class name, software; responsibilities, and collaborators, as a way of giving learners a direct experience of objects. Three dimensions which (2) Analysis: Develop a model of the system’s desired identify the role of an object in a design: class name, behavior; responsibilities, and collaborators. The class name of an (3) Design: Create architecture for the implementation; object creates a vocabulary for discussing a design. Responsibilities identify problems to be solved. The solutions (4) Evolution: Evolve the implementation through successive will exist in many versions and refinements. A responsibility refinements; serves as a handle for discussing potential solutions. (5) Maintenance: Manage post-delivery evolution. Collaborators objects will send or be sent messages in the course of satisfying responsibilities. b) Micro Process (Booch). The micro process tends to follow these steps: Classes are created that describe real world objects that exist in a system. These classes are assigned responsibilities, i.e., (1) Identify the classes and objects at a given level of data and actions that the class is required to support. A class abstraction. may fulfill a responsibility by itself, or it may collaborate with some other class to fulfill the responsibility. The advantage is (2) Identify the semantics of classes and objects. that the design team can easily move the cards around to (3) Identify the relationships among classes and objects. visualize the design, and modifications to the design can be made quickly by simply replacing cards. (4) Specify the interface and implementation of classes and objects. 2.4 Demeter: 2.2 CBD/e: (Component Base Development) Adaptive programming deals with specifying the connections between objects as loosely as possible and this is called CBD/e is a methodology for allowing organizations to begin "structure-shy" programming. The Demeter system and tools component-based development quickly. CBD/e consists of are all about "Adaptive" programming. two major parts Process and Analysis and Design (A&D) methodology. Law of Demeter (LoD) for functions says that: A method "M" of an object "O" should invoke only the methods of the 1. The CBD/e Process following kinds of objects: The CBD/e process is based on repeating plan which is 1. Itself follows: 2. Its parameters a) Assessment: To decide what your organization wants from CBD. 3. Any objects it creates/instantiates b) Planning: Planning takes place, including selecting the 4. Its direct component objects project that will be executed and the participants for this The basic idea is to avoid invoking methods of a member particular program. object that is returned by another method. When you do this, c) Education: Fundamental training that is required to go you make structural assumptions about the container object to CBD. that may be likely to change. The container may later need to be modified to contain a different number of the contained d) Infrastructure: Your organization’s infrastructure is objects, or it may end up being changed to contain another adjusted to enable component-based development. object which contains the original component object. If the e) Execution: This is where the start of implementation "returned" object isn't a subpart of the object whose method occurs. was invoked, nor of some other object, then it typically is not a violation of LoD to invoke a method of the returned object. f) Improvement: This is where to review the results. Using the LoD you instead ask the container to invoke a 2) The CBD/e Analysis and Design Methodology method on its elements and return the result. The details of A&D methodology uses behavioral analysis and design how the container propagates the message to its elements are techniques to facilitate building components. Behavioral encapsulated by the containing object. analysis and design is based on the concept that the pieces of A side-effect of this is that if you conform to LoD, while it your system are not just chunks of data that are there to be may quite increase the maintainability and adaptiveness of worked by whatever processes you develop. your software system, you also end up having to write lots of The first steps design the specification, which describes the little wrapper methods to propagate methods calls to its solution without any implementation details. The specification components. This problem is addressed by the Demeter tools,
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]