100 likes | 179 Views
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. Introduction Project Settings Some Results Conclusions and Future Work. Contents.
E N D
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
Introduction Project Settings Some Results Conclusions and Future Work Contents
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 1. Introduction
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 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 2. … Project Settings
2. … Project Settings XP 1st Iteration 2nd Iteration 3rd Iteration 1st Iteration Construction 2st Iteration Construction Inception Elaboration RUP 1 week 2 weeks 3 weeks 3 weeks
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 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 3. … Some results
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 4. Conclusions and Future Work
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