ADOPTING RUP (RATIONAL UNIFIED PROCESS) ON A SOFTWARE DEVELOPMENT PROJECT A THESIS SUBMITTED TO THE GRADUATE SCHOOL OF NATURAL AND APPLIED SCIENCES OF ÇANKAYA UNIVERSITY BY TUFAN TAŞ IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN THE DEPARTMENT OF COMPUTER ENGINEERING SEPTEMBER 2009 Title of the Thesis : Adopting RUP (Rational Unified Process) on a Software Development Project Submitted by Tufan TA~ Approval of the Graduate School of Natural and Applied Sciences, <;ankaya University Pro~ Acting Director I certify that this thesis satisfies all the requirements as a thesis for the degree of Master of Science. Prof.tvz'f{'Dr. Mehmet-/~R. TOLUN Head of Department This is to certify that we have read this thesis and that in our opinion it is fully adequate, in scope and quality, as a thesis for the degree of Master of Science. ftJrr.7~ Prof.Z--A~Dr. a Ai<.TA~,1\ ~\-qk Prof. Dr. MehmetR. TOLUN Co-Supervisor Supervisor Examination Date 03.09.2009 Examining Committee Members Prof. Dr. Mehmet R. TOLUN «;ankaya Univ.) ltti1' 7~ Prof. Dr. Ziya AKTA~ (Ba~kent Univ.) .~~ Asst. Prof. Dr. AbdUlKadir GOROR «;ankaya Univ.) Instructor Dr. Ali RIza A~KUN «;ankaya Univ.) \. AA~~ STATEMET OF O PLAGIARISM I hereby declare that all information in this document has been obtained and presented in accordance with academic rules and ethical conduct. I also declare that, as required by these rules and conduct, I have fully cited and referenced all material and results that are not original to this work. Name, Last Name : Tufan TAŞ Signature : Date : 03/09/2009 iii ABSTRACT ADOPTING RUP (RATIONAL UNIFIED PROCESS) ON A SOFTWARE DEVELOPMENT PROJECT TAŞ, Tufan M.Sc., Department of Computer Engineering Supervisor: Prof. Dr. Mehmet R. TOLUN CoSupervisor: Prof. Dr. Ziya AKTAŞ September 2009, 218 pages This thesis analyzes the process of applying Rational Unified Process (RUP) successfully on a software development project step by step. Many software development projects today have a tendency to fail on some level. Even though they may not fail entirely, they might be completed with schedule delays, budget overrun or with poor quality that do not meet the requirements of customers because of poor management and lack of necessary documentation of the project. Applying RUP avoids these major problems in a project by developing set of work products which depict the essentials of the system from requirements to detailed design before the system could be implemented. However, software development teams have an overall attitude that RUP becomes less agile and too rigid as the size of projects get smaller. The thesis will also try to prove that this opinion is not true by using tools Rational Method Composer (RMC) and Rational Software Modeler (RSM) to successfully complete the project. iv ÖZ RUP YÖNTEMĐNĐN BĐR YAZILIM GELĐŞTĐRME PROJESĐ ÜZERĐNDE UYGULANMASI TAŞ, Tufan Yüksek Lisans, Bilgisayar Mühendisliği Anabilim Dalı Tez Yöneticisi: Prof. Dr. Mehmet R. TOLUN Ortak Tez Yöneticisi: Prof. Dr. Ziya AKTAŞ Eylül 2009, 218 sayfa Bu tez Rational Unified Process (RUP) yönteminin bir yazılım geliştirme projesinde başarıyla uygulanma sürecini adım adım incelemiştir. Günümüzde birçok yazılım geliştirme projesi bazı düzeylerde başarısız olma eğilimindedir. Projeler tamamen başarısız olmasa bile, projenin kötü yönetimi ve gerekli dökümantasyonun eksik olması nedeniyle takvim gecikmeleriyle, bütçe aşımıyla ya da müterilerin gereksinimlerini karşılamayan düük kalitede yazılım ürünleri görülmektedir. Bir projede, sistemin uygulanmasından önce gereksinimlerden detaylı tasarımına kadar esaslarını gösteren bir seri iş ürünü geliştirilerek RUP’nin uygulanması ile bu tür sorunların oluumu engellenir. Bununla birlikte, yazılım geliştirme gruplarının proje boyutları küçüldükçe RUP’nin daha az çevik ve çok katı bir hal aldığına dair genel bir kanı vardır. Bu çalışma, başarıyla bir projeyi tamamlamak için Rational Method Composer (RMC) ve Rational Software Modeler (RSM) araçlarını kullanarak bu görüün de doğru olmadığını kanıtlamaya çalışmıştır. v ACKOWLEDGEMETS I would like to express my deepest gratitude to my supervisor Prof. Dr. Mehmet R. TOLUN and cosupervisor Prof. Dr. Ziya AKTAŞ for their guidance, advices, criticism, encouragements, and insight throughout the research. Thanks are also extended to Dr. Alan Brown, Mrs. Jale Akyel and Mr. Erkan Özkan, all IBM members, for their encouragement and support they provided to cosupervisor Prof. Dr. Ziya Aktaş during the supervision of the Thesis. The last, but not the least, support of IBM Turkey by providing Rational Method Composer (RMC), Rational Software Modeler (RSM) and Rational Rose software packages during the thesis is also acknowledged. vi TABLE OF COTETS STATEMENT OF NON PLAGIARISM .................................................................. iii ABSTRACT .............................................................................................................. iv ÖZ…. ........................................................................................................................... v ACKNOWLEDGEMENTS ....................................................................................... vi TABLE OF CONTENTS ......................................................................................... vii LIST OF TABLES ..................................................................................................... xi LIST OF FIGURES ................................................................................................. xiii CHAPTERS: 1. INTRODUCTION ............................................................................................. 1 1.1 Background of the Problem .................................................................... 1 1.2 Statement of the Problem ........................................................................ 3 1.3 Objective of the Study ............................................................................ 3 1.4 Organization of the Study ....................................................................... 4 2. UNIFIED MODELING LANGUAGE (UML) ................................................. 5 2.1 Modeling Principles ................................................................................ 5 2.2 What is UML? ........................................................................................ 6 2.3 UML 2.0 ................................................................................................. 7 2.4 UML Diagrams ....................................................................................... 8 2.4.1 Class Diagram ............................................................................. 8 2.4.2 Object Diagram ......................................................................... 10 2.4.3 Composite Structure Diagram .................................................. 10 2.4.4 Deployment Diagram ................................................................ 11 2.4.5 Component Diagram ................................................................. 12 vii 2.4.6 Package Diagram ...................................................................... 13 2.4.7 Activity Diagram ...................................................................... 14 2.4.8 Use Case Diagram .................................................................... 15 2.4.9 State Machine Diagram ............................................................ 16 2.4.10 Interaction Overview Diagram ................................................. 18 2.4.11 Sequence Diagram .................................................................... 19 2.4.12 Communication Diagram .......................................................... 20 2.4.13 Timing Diagram ........................................................................ 21 2.5 The Concept View of a System ............................................................ 22 3. RATIONAL UNIFIED PROCESS (RUP) ...................................................... 24 3.1 Overview of the Rational Unified Process ........................................... 24 3.2 RUP Lifecycle ...................................................................................... 27 3.2.1 Inception Phase ......................................................................... 27 3.2.2 Elaboration Phase ..................................................................... 28 3.2.3 Construction Phase ................................................................... 29 3.2.4 Transition Phase ........................................................................ 31 3.3 RUP Disciplines.................................................................................... 32 3.3.1 Business Modeling Discipline .................................................. 32 3.3.2 Requirements Discipline ........................................................... 33 3.3.3 Analysis and Design Discipline ................................................ 34 3.3.4 Implementation Discipline ........................................................ 34 3.3.5 Test Discipline .......................................................................... 35 3.3.6 Deployment Discipline ............................................................. 35 3.3.7 Project Management Discipline ................................................ 36 3.3.8 Configuration and Change Management Discipline ................. 37 3.3.9 Environment Discipline ............................................................ 37 3.4 Iteration in Rational Unified