A Framework for Addressing Communication Issues in Agile Model

Total Page:16

File Type:pdf, Size:1020Kb

A Framework for Addressing Communication Issues in Agile Model A Framework for Addressing Communication Issues in Agile Model Thesis submitted in partial fulfillment of the requirements for the award of degree of Master of Engineering in Software Engineering Submitted By Parikshit Joshi (Roll No. 801131016) Under the supervision of: Under the co-supervision of: Mr. Ashish Aggarwal Dr. Shivani Goel Assistant Professor Assistant Professor COMPUTER SCIENCE AND ENGINEERING DEPARTMENT THAPAR UNIVERSITY PATIALA – 147004 July 2013 i Acknowledgement No volume of words is enough to express my gratitude towards my guides Mr. Ashish Aggarwal and Dr. Shivani Goel, Department of Computer Science & Engineering, Thapar University, Patiala, who have been very concerned and have aided for all the materials essentials for the preparation of this thesis report. They have helped me to explore this vast topic in an organized manner and provided me all the ideas on how to work towards a research- oriented venture. I am also thankful to Dr. Maninder Singh, Head of Computer Science & Engineering Department and Mr. Karun Verma, P.G. Coordinator, for the motivation and inspiration that triggered me for the thesis work. I would also like to thank the staff members and my colleagues who were always there at the need of hour and provided with all the help and facilities, which I required, for the completion of my thesis work. Most importantly, I would like to thank my parents and the almighty for showing me the right direction out of the blue, to help me stay calm in the oddest of the times and keep moving even at times when there was no hope. Parikshit Joshi (801131016) ii Abstract There are various software development models are used in software industry. The selection of models is based on the type of software. Agile models are widely used for developing software in industries. Various types of models have been developed time to time and consistent work in the field of agile is going on. Different types of agile models have been developed as extreme programming (xp), adaptive system development, dynamic system development methodology, scrum etc. These methods provide quick response to change request, fast and frequent delivery of software products to customer and immediate feedback. Due to change in market scenario, these factors have made agile methods more popular than traditional software development methods. The problem, in agile methods, arise when distributed team working on different module of same software. And this problem become more crucial when there is less focus on documentation. In order to overcome problem, a framework has been proposed in this thesis. Framework will provide the information that which modules are connected to current module. So if there is any change request in current module then the team leader of other module which are related to current module can be informed immediately. iii Table of Contents Certificate ......................................................................................................................... i Acknowledgement .......................................................................................................... ii Abstract .......................................................................................................................... iii Table of Contents ........................................................................................................... iv List of Figures ................................................................................................................ vi List of Tables ................................................................................................................ vii Chapter 1. Introduction ................................................................................................... 1 1.1 What is Agile Software Development ................................................................ 1 1.1.1 Agile Software Development process ................................................... 1 1.1.2 History of Agile Methods ...................................................................... 2 1.1.3 Agile Manifesto ..................................................................................... 4 1.1.4 Agile Principles .................................................................................... 6 1. .2 Agile Software Development Methodologies ................................................... 8 1.2.1 Agile models ........................................................................................ 10 1.2.1.1 Adaptive software development ............................................... 11 1.2.1.2 Crystal model ............................................................................ 13 1.2.1.3 Scrum model ............................................................................. 14 1.2.1.4 AMD ......................................................................................... 16 1.2.1.5 FDD ................................................................................................... 17 1.2.1.6.Extreme Programming ........................................................... 19 1.2.1.7 ICONIX..................................................................................... 21 1.2.1.8DSDM ........................................................................................ 22 1.2.1.9LSD ............................................................................................ 23 1.2.2 Common properties of Agile methods ................................................ 24 1.2.3 Comparison of some Agile Methods ................................................... 25 1.2.4 TSDM vs ASDM ................................................................................. 28 1.3 Communication problems ................................................................................. 29 1.4 Organization of thesis ....................................................................................... 30 Chapter 2 Literature Survey: Communication Issues In Agile ..................................... 31 2.1 Communication issues in Agile Methods ......................................................... 34 Chapter 3 Problem Statement and objective ................................................................. 40 iv Chapter 4 Work Done .................................................................................................. 41 4.1 Steps for DFD to PERT chart .......................................................................... 41 4.2 PERT chart to Dependency List ...................................................................... 41 4.3 Working ........................................................................................................... 42 Chapter 5 Results .......................................................................................................... 43 5.1 Case Study: Order Processing System ............................................................. 43 5.2 Case Study: Admission Management System ................................................. 48 Chapter 6 Conclusion and Future scope ....................................................................... 53 6.1 Conclusion ........................................................................................................ 53 6.2 Thesis Ccntribution ........................................................................................... 53 6.3 Future scope ..................................................................................................... 53 References .................................................................................................................... 54 List of publications ...................................................................................................... 60 v List of Figures Figure 1.1 Agile Methodologies ..................................................................................10 Figure 1.2 Adaptive Software Development ...............................................................12 Figure 1.3 Agile Crystal Methodology ........................................................................13 Figure 1.4 Scrum Model ..............................................................................................15 Figure 1.5 Agile Model Driven Development Approach ............................................16 Figure 1.6 Feature Driven Development Model ..........................................................17 Figure 1.7 Agile Extreme Programming ......................................................................19 Figure 1.8 Agile ICONIX Model .................................................................................21 Figure 1.9 Dynamic System Development Methodology............................................22 Figure 1.10 Lean software Development .....................................................................24 Figure 2.1 Technology adaptation lifecycle by Moore ................................................31 Figure 2.2 Modes of Communication ..........................................................................35 Figure 5.1 Case Study of Order Processing System ....................................................43 Figure 5.2 PERT Chart of Case Study 1 ......................................................................44 Figure 5.3 Framework ..................................................................................................45 Figure 5.4 Module Info ................................................................................................45
Recommended publications
  • Pengembangan Aplikasi Web Dengan Iconix Process Dan Uml Studi Kasus: Sistem Manajemen Isi
    PENGEMBANGAN APLIKASI WEB DENGAN ICONIX PROCESS DAN UML STUDI KASUS: SISTEM MANAJEMEN ISI Yulianta1 dan Petrus Mursanto2 1Magister Teknologi Informasi, Universitas Indonesia Jl. Salemba Raya 4, Jakarta 12000 Indonesia [email protected] 2Enterprise Computing Lab ± Fakultas Ilmu Komputer, Universitas Indonesia Kampus Baru UI Depok, Jawa Barat, 16424 Indonesia [email protected] Abstrak Situs web sangat kompleks dengan beragam isi dan dinamis karena selalu menampilkan informasi terbaru. Kompleksitas situs web akan bertambah saat situs web tersebut harus dimodifikasi untuk menambahkan halaman-halaman baru dan fitur-fitur baru sesuai permintaan pengunjung. Untuk menghindari kompleksitas tersebut, perlu diciptakan sebuah aplikasi berbasis web yang dapat digunakan untuk mengelola seluruh sumber daya situs web. Aplikasi ini dikenal dengan sistem manajemen isi (content management system). Makalah ini membagikan pengalaman penulis dalam mengembangkan sistem manajemen isi pada PT X yang dinamai dengan xCMS. Metode pengembangan perangkat lunak yang digunakan adalah ICONIX Process. Metode ICONIX Process menggunakan Unified Modeling Language (UML) sebagai notasi utama untuk mengambarkan dan mendokumentasikan sistem yang dibangun. Makalah ini menguraikan secara garis besar aktifitas-aktifitas dan artefak-artefak yang dihasilkan pada setiap fase pengembangan. Hasil akhir adalah sebuah prototipe aplikasi manajemen isi aplikasi web yang diberi nama xCMS. Kata kunci: ICONIX, Software engineering, CMS, UML, Web application. 1. Latar Belakang pada perubahan arsitektur. Masalah yang timbul adalah kompleksitas yang meningkat sehingga Perkembangan Internet yang cukup cepat modifikasi sulit dilakukan dan seandainya pun didorong oleh penggunaannya yang makin meluas. dilakukan, kestabilan sistem aplikasi menjadi Hal ini tidak terlepas dari kemudahan penggunaan terganggu. internet itu sendiri. Banyak aplikasi yang sudah ada Aplikasi sistem manajemen isi (Content ditulis ulang dalam bentuk aplikasi web agar bisa Managemet System) berbasis web dibutuhkan untuk disajikan di internet.
    [Show full text]
  • Agile Modeling: Effective Practices for Extreme Programming and the Unified Process
    Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process Scott Ambler Wiley Computer Publishing John Wiley & Sons, Inc. 72244_FMI 2/27/02 11:34 AM Page iv 72244_FMI 2/27/02 11:34 AM Page i Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process Scott Ambler Wiley Computer Publishing John Wiley & Sons, Inc. 72244_FMI 2/27/02 11:34 AM Page ii Publisher: Robert Ipsen Editor: Theresa Hudson Development Editor: Kathryn A. Malm Managing Editor: Angela Smith New Media Editor: Brian Snapp Text Design & Composition: D&G Limited, LLC Designations used by companies to distinguish their products are often claimed as trademarks. In all instances where John Wiley & Sons, Inc., is aware of a claim, the product names appear in initial capital or ALL CAPITAL LETTERS. Readers, however, should contact the appropriate companies for more complete information regarding trademarks and registration. This book is printed on acid-free paper. Copyright © 2002 by Scott Ambler. All rights reserved. Published by John Wiley & Sons, Inc., New York Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copy- right Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 750-4744. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 605 Third Avenue, New York, NY 10158-0012, (212) 850-6011, fax (212) 850- 6008, E-Mail: PERMREQ @ WILEY.COM.
    [Show full text]
  • Use Case Driven Object Modeling With
    CYAN YELLOW MAGENTA BLACK PANTONE 123 CV BOOKS FOR PROFESSIONALS BY PROFESSIONALS® THE EXPERT’S VOICE® IN UML MODELING Companion eBook Available Use Case Driven Object Modeling with UML: PackedPacked withwith Theory and Practice Object Modeling with UML Use Case Driven examplesexamples andand studentstudent exercisesexercises Dear Reader, In theory you’d like to be using UML and use cases, but in practice it’s often difficult. Here are a few reasons why: Doug Rosenberg, author of • UML is too big. In theory it’s all good, but in practice UML’s size makes it impractical and causes analysis paralysis. We’ll teach you a UML core subset Use Case Driven Object Modeling with UML: A and a minimalist process that’s been proven on hundreds of projects. Practical Approach • Your analysts write vague and ambiguous use cases. In theory the use cases Use Case Driven are abstract, technology-free, and implementation independent, but in Applying Use Case Driven Object Modeling with UML: practice they’re vague and ambiguous, so your programmers ignore them. An Annotated e-Commerce We’ll teach you how to disambiguate them. Example • Your team has difficulty getting from use cases to code. In theory it seems Extreme Programming easy, but in practice something doesn’t quite mesh. The team has difficulty Refactored: The Case crossing the gap between “what” and “how.” We’ll unveil secrets of the Object Modeling Against XP (Apress, 2003) “missing link” between analysis and design that have been closely guarded Agile Development with by goat-herding Druids in darkest Wales for centuries.
    [Show full text]
  • Rational Unified Process • Agile Methods •Overview • Extreme Programming (XP) •Practices • XP Process •Conclusion
    SEG3101 (Fall 2010) Integrating Requirements Engineering into Software Engineering Processes Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) and material from S. Somé 2008 and D. Amyot 2008 Table of Contents • Rational Unified Process • Agile Methods •Overview • Extreme Programming (XP) •Practices • XP Process •Conclusion • La perfection est atteinte non quand il ne reste rien à ajouter, mais quand il ne reste rien à enlever (Perfection is attained not when there is no longer anything to add, but when there is no longer anything to take away).1 [1] Antoine de Saint-Exupéry (1900 - 1944), “Wind, Sand and Stars” 2 SEG3101 (Fall 2010). Integrating Requirements Engineering into Software Engineering Processes. 3 SEG3101 (Fall 2010). Integrating Requirements Engineering into Software Engineering Processes. Rational Unified Process Rational Unified Process Agile Methods Overview Extreme Programming Practices XP Process Conclusion Rational Unified Process (RUP) • One commercial implementation of the Unified Process • Developed by Jacobson, Booch, Rumbaugh • Evolved from the Objectory process and the earlier Ericsson approach • Now an IBM product1 • Vocabulary and concepts • Artefacts, roles, disciplines, activities • Use case-driven, architecture-centered, iterative, incremental, risk management-oriented Use Case-Driven Process • RUP is a process framework (not a process on its own) • Intended to be customized to project needs [1] http://www-01.ibm.com/software/awdtools/rup/ 5 SEG3101 (Fall 2010).
    [Show full text]
  • ICONIX Approach to MVC: Applying Robustness Analysis on the Model–View–Controller Architecture
    Journal of the ACS, Vol. 7, May 2013 ICONIX Approach to MVC: Applying Robustness Analysis on the Model–View–Controller Architecture Ahmed El-Abbassy, Mohamed El-Zeweidy [email protected] , [email protected] Higher Institute of Computer Science & Information Technology, El-Shorouk Academy Abstract ICONIX is a smart lightweight software process that is successfully used in both the academic and commercial software community. ICONIX is a use case driven software development methodology that is well suited to agile development. Due to its success, many adaptations have been proposed to fit with different contexts such as service oriented, embedded software and mobile development. This paper investigates the application of ICONIX to the development of MVC (Model View Controller) applications. MVC is an emerging architectural pattern with objective to promote development of software that is flexible and easy to change. This is a quality requirement for most of software products and especially for web based applications. The paper discusses and presents a proposed adaptation to ICONIX in order to help to fit with the MVC design. The proposed adaptation is illustrated by using a suitable example. Key words: Software Engineering, Software Development Process, MVC Architecture, UML, Object modeling, Robustness Analysis 1. Introduction The traditional Plan-driven methods (such as PSP, TSP and RUP) have been challenged in recent years by the emergence of the Agile methods (such as Extreme Programming, SCRUM and CRYSTAL) [1, 2]. Traditional software development methodologies, usually designated as engineering methodologies, are very bureaucratic, in what documentation and rigid control mechanisms is concerned. Agile methods afford more flexibility compared to traditional plan-driven approaches, which lock in the project details early and are less able to adjust to stakeholders’ evolving needs, market changes, and unplanned technology challenges.
    [Show full text]
  • An Experience of Implementing Iconix, A
    The Online Journal of Science and Technology - January 2021 Volume 11, Issue 1 AN EXPERIENCE OF IMPLEMENTING ICONIX, A SOFTWARE DEVELOPMENT METHODOLOGY, IN A SOFTWARE DEVELOPMENT CLASS DICTATED IN A PRIVATELY MANAGED UNIVERSITY FROM ARGENTINA, VIRTUALLY, DUE TO THE QUARANTINE Rodrigo DE LATORRE Centro de Altos Estudios en Tecnología Informática - Universidad Abierta Interamericana, Buenos Aires, Argentina [email protected] Marcelo VAQUERO Centro de Altos Estudios en Tecnología Informática - Universidad Abierta Interamericana, Buenos Aires, Argentina Marcelo.Vaquero,@uai.edu.ar Guillermo LEALE Centro de Altos Estudios en Tecnología Informática - Universidad Abierta Interamericana Buenos Aires, Argentina [email protected] Alejandro SARTORIO Centro de Altos Estudios en Tecnología Informática - Universidad Abierta Interamericana Buenos Aires, Argentina [email protected] ABSTRACT Due to the mandatory quarantine implemented in most countries, and especially where this investigation is taking place, Argentina, most Academic organizations, either public or privately managed, needed to reinvent themselves in order to be able to teach courses in a completely remote environment. In this context, one class, which has the objective of develop a specific software and where this research took place, will use ICONIX, a software development methodology that is one of the latest technology standards used in the software industry, and flipped classroom, where instead of professors teaching students, they provide them
    [Show full text]
  • Improvement of Human Resources Performance Through Online Presence Applications Based on Android Using UML - Iconix Process
    Improvement of Human Resources Performance Through Online Presence Applications Based on Android Using UML - Iconix process Amirul Mustofa1, Achmad Muzakki2, Slamet Kacung3, Eny Haryati4 {[email protected], achmad [email protected], [email protected]} 1,4Lecturer in the public Administration Study Program-Faculty of Administrative Sciences, Dr. Soetomo University, Indonesia 2,3Lecturer in the informatics Engineering Study Program-Faculty of Engineering, Dr. Soetomo University, Indonesia Abstract: This study aims to build and design an online presence system based on Android using the Unified Modeling Language (UML) Iconix Process. This modeling is designed using: domain models, use case diagrams, robustness diagrams, sequence diagrams, and graphical user interface (GUI) storyboards. To implement this modeling, software requirements specification (SRS) is needed, so that the modeling design is in accordance with user needs. this is the modeling of the performance of human resources in universities using UML software - Iconix Process, which produces software requirements specifications. With this SRS, it can reduce the time and cost of building an online android presence application. Keywords: Human resources, online presence application, UML. 1. Background The implementation of the present application through fingerprint technology in universities still leaves some obstacles, including the limited number of fingerprint tools that do not compare with the number of human resources (lecturers, employees, and students); there is no transparency in attendance, because lecturers, employees, and students cannot monitor attendance at all times; and authorized leaders cannot monitor and evaluate the presence of resources quickly and in real-time. The application of attendance at universities that use finger print with computerized assistance, also still encounters several issues, including not being able to answer accuracy, the presence and recapitulation of data every month, so that to attend attendance is still often wrong, late, and less effective.
    [Show full text]