XP2003, May 25-29, 2003, Genova, Italy  www.dsic.upv.es/~letelier/pub An Experiment Working with RUP and XP Patricio Letelier, José H. Canós and Emilio.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

How to Transfer from Waterfall to Iterative Te Bai, Ji Qi.
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Ch 3: Unified Process CSCI 4320: Software Engineering.
Waterfall Model, RUP, Agile Methodologies & Extreme Programming
RUP/UP Software Development Method Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
INFO 638Lecture #81 Software Project Management Cycle plan and build INFO 638 Glenn Booker.
Alternate Software Development Methodologies
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Software Life Cycles ECE 417/617: Elements of Software Engineering
Agile
1 RUP Workshop By George Merguerian Senior Partner Business Management Consultants
Agile Requirements Methods CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 26, 2004.
Permeation of RUP and XP on Small and Middle-Size Projects KREŠIMIR FERTALJ University of Zagreb Faculty of Electrical Engineering and Computing Department.
BORIS MILAŠINOVIĆ FACULTY OF ELECTRICAL ENGINEERING AND COMPUTING UNIVERSITY OF ZAGREB, CROATIA Experiences after three years of teaching “Development.
2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
1 CMSC 132: Object-Oriented Programming II Nelson Padua-Perez William Pugh Department of Computer Science University of Maryland, College Park.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXPERT Best practices.
Using IBM Rational Unified Process for software maintenance
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Extreme Programming Practices The Planning Game Small Releases System Metaphor Simple Design Continuous Testing Refactoring Pair Programming Collective.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Presenter: 陳秋玉 1.  Extreme programming Extreme programming  On-site customer On-site customer  Benefit Benefit  Characteristics of a good customer.
TEACHER FEEDBACK WEBSITE HTVN TEAM. AGENDA 1.TEAM INTRDUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT.
CPSC 2150 August 21, Chapter 1 Object Oriented Software Development This is an introductory course In this chapter we will look at 3 topics Challenges.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
EXtreme Programming: Test-First Copyright Rick Mugridge UoA Rick Mugridge Department of Computer Science University of Auckland
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Extreme Programming.
XP – Extreme Programming
(1) Vito Baggiolini & Laia Mateos Experiences with a Software Process in the CESAR Project Vito Baggiolini, SL/CO Laia Mateos Miret, SL/EA.
Sofia Bulgaria Summer School IST eXPERT: Best Practice on e-Project Development 30 June - 2 July 2003 eXPERT Best practices.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
December Using Software Development Methodology (SDM) in the Third Teaching Unit (laboratory) CS Teachers Conference Dr. Orit Hazzan & Yael Dubinsky.
Software Design: Principles, Process, and Concepts Getting Started with Design.
Virtual Company By: Aiman Erbad Dung Nguyen Dung Nguyen Khalil El Haitami Khalil El Haitami.
Extreme Programming Based on and
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Agile Methods Presentation By: Jason Abbett. Definition A process to rapidly develop software Many kinds of agile methods but few are practiced.
EXtreme Programming and Open Source engineering paradigm A comparison
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Software Development Life Cycle. The Software Life Cycle  Encompasses all activities from initial analysis until end of work  Formal process for software.
Software Development.
Requirements Engineering Lecture 4
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Planning User stories are written.
Jeliot 3 Spring 2004 Andrés Moreno García Niko Myller
9/18/2018 Department of Software Engineering and IT Engineering
Introduction to Software Engineering
Teaching slides Chapter 1.
Coming up: What is Agile?
Agile Development – a new way of software development?
Presentation transcript:

XP2003, May 25-29, 2003, Genova, Italy  An Experiment Working with RUP and XP Patricio Letelier, José H. Canós and Emilio A. Sánchez Department of Information Systems and Computation Valencia University of Technology

XP2003, May 25-29, 2003, Genova, Italy  Contents 1. Introduction 2. Project Settings 3. Some Results 4. Conclusions and Future Work

XP2003, May 25-29, 2003, Genova, Italy  1. Introduction An experiment with upper-level students in the subject “Laboratory of Information Systems” at the School of Computer Science Aim: compare RUP and XP regarding how easily they are learned and applied by students

XP2003, May 25-29, 2003, Genova, Italy  2. Project Settings 2 teams using RUP and 4 teams using XP Same case study: Develop the information system of a virtual store Laboratory with 20 PCs 2 hours sessions (x2, a week) 12 hours a week of workload for each student

XP2003, May 25-29, 2003, Genova, Italy  2. … Project Settings Previous knowledge of some tools and notations but they are beginners in process and teamwork experience Basic concepts of RUP and XP were taught by the instructors One instructor acted as client and another acted as coach Each team was composed of: 1 Project Manager, 1 Tester/Tracker, and from 4 to 6 Programmers

XP2003, May 25-29, 2003, Genova, Italy  2. … Project Settings 1st Iteration 2nd Iteration3rd Iteration InceptionElaboration 1st Iteration Construction 2st Iteration Construction XP RUP 1 week2 weeks3 weeks

XP2003, May 25-29, 2003, Genova, Italy  3. Some results XP Simplicity, few artifacts, less traceability and updating efforts First iteration: under estimation of user stories/task and some conflicts among team members Most of XP practices were easy to learn and apply. Only some troubles with “test first”, refactoring, coding standards and metaphor Our typical laboratory facilities were fine for teaching and working on XP

XP2003, May 25-29, 2003, Genova, Italy  3. … Some results RUP Project ran smoothly during the first two phases (inception and elaboration) but problems came after Precise definition of the different artifacts Artifact updating and requirements management need an important effort Customization of RUP to the proyect is not a simple task

XP2003, May 25-29, 2003, Genova, Italy  4. Conclusions and Future Work The success (quality and productivity) of the project can be reached independently of the process Teams using RUP needed more mentoring XP needs and generates stronger relationships among team members Open issues: impact on “software maintenance”, impact if some XP practices were discarded, etc. “Customers on-site” was not a big dificulty Next step: a more controlled (and maybe specific) experiment

XP2003, May 25-29, 2003, Genova, Italy  An Experiment Working with RUP and XP Patricio Letelier, José H. Canós and Emilio A. Sánchez Department of Information Systems and Computation Valencia University of Technology