DOCSLIB.ORG

OBJECT-ORIENTED Development and the UNIFIED PROCESS " This Chapter Also Introduces the Unified Process As a Comprehensive System Deve.!­ Opment Methodology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OBJECT-ORIENTED Development and the UNIFIED PROCESS chapter OBJECT-ORIENTED DEVELOPMENT AND THE • UNIFIED PROCESS LEARNING OBJECTIVES After reading this chapter, you should be able to: • Explain the purpose and various phases of the traditional systems development life cycle (SOLe) • E)(plain when to use an adaptive approach to the SOLe in place of the more predictive traditional SOLe • Describe how the more adaptive Unified Process (UP) life cycle uses iterative and incremental development • Explain the differences between a model, a tool, a technique, and a methodology • Describe the Unified Process as a comprehensive system development methodology that combines proven best practices with the iterative UP life cycle • Describe the disciplines used in a UP development project • Oescribe the key features of the object-oriented approach • E)(plain how automated tools are used in system development 36 PART 1 SYSTEM DEVELOPMENT AND THE UNIFIED PROCESS DEVELOP MENT APPROACHES AT AJAX <:> CORPORATION , CONSOLIDATED CONCEPTS, AND PINNACLE MANUFACTURING Kim, Mary, and Sob, two graduating seniors and a junior applying for an and on about th ings like OMG, UML, and UP and some people named internship, well' discussing tlltil f!Cenl interviews at different companies 800ch, Rumbaugh, and Jacobson. But then it turned out that they were us· that recruited computer information system (CIS) majors on their campus. ing the object·oriented approach to develop systems. and they liked the fact All agreed that they had learned a 10\ by visiting the companies. but they thai I knew Java and VB .NET. No problem once I got past all of the termi· also all felt somewhat overwhelmed at first. nology they used. I just haven't studied analysis and design yet, so they ~id "At first I wasn't sure I knew what they were talking about,' Kim cau­ they'd send me out for training on Rational XDE, a CASE tool for the object· tiOusly volunteered. During her on-campus interview, Kim had impressed oriented approaCh, 10 gel me ilarted: Ajax Corporation with her knowledge of object-oriented modeling. When Bob had a different story, "A few people said analysis and design she visited the Ajax home ollice data cenler for lhe s«ond interview, the were no longer a big deal. I'm thinking, 'Knowing Ihat would have saved interviewers spent quite a lot of lime dl'!oCribillg the company's system me some time in school:" Bob had visited Pinnacle Manufacturing, which development methodology. had a small system development group supporting manufacturing and "A. few people said to forget everything I learned in sdlool," (ontin· inventory conllol. "They said they try to just jump in and gel 10 the code as ued Kim. Ajax Corporation had purch<lsed a complete development method· soon as possible. Little documentation, Not much of a project plan. Then ology cal led 1M One from a small consulting firm. Most employees agreed it they showed me some booh on their desh, and it looked like they had worked fairly well. The people who had worked for Ajax for quite a while been doing a lot of read ing about analysis and deSign, I could see they were thought 1M One was unique, and they were very proud of it. They had using eXtreme Programm ing and agile modeling techniques and focusing Inrnted a lot 01 time and money learning and adapting to it. only on best practices needed iOf their small projecrs.1t turns oUlthey jusl "Well. that got my aUention when !hey ~id to lorget what I learned organize their work differently by looking al ,isk and building prototypes, in school." noted Kim, "but then they started telling me about their SOlC I recognized some sketches of class diagrams and sequence diagrams on phases. about iterations, about development disdplines. about use cases. the boss's whiteboard, so I felt fairly comfortable," and things like that." Kim had recognized that many of the key concepts in Kim, Mary, and Bob all agreed that there was much to learn in these the 1M One methodology were fairly standard models and tec:hniques from work environments but also that many different terms and points of view the Unified Process system development methodology but packaged under are used to describe the ~me key concepts and techniques they lea rned in a different name. school. They were all glad they focused on the fundamentals in their CIS "I mow what you mean," said Mary, a very talented programmer who dasses and that they had been exposed to some leading.edge concepts and knew just about every new programming language available but !ladn'! yet techniques like UMl, the Unified Process. and some 01 the lighter, mOfe completed her analysis and design course. "Consolidated Concepts wenl on agile methodologies. Overview As the experiences of Kim, Mary, and Bob demonstrate, IOday's businesses and their employees are extremely interested in object·oriented system development-and specifically in object·oriented analysis and design techniques based on the Unified Process (U P), Project managers rely on a variety of aids to help them wi th every step of the development process. The traditional systems deve:lopmentlife cycle (SDLC) intro­ duced in this chapter provides a backdrop for understanding the predictive: approach to system development. The more recent Unified Process life cycle uses iterative: and incremental development practices that have: proven to be useful when an adaptive approach is required. But within that framework, the system developer relies on many mOTe concepts, induding methodologies, models, tools, and techniques. It is very imponant fo r you to u nderstand what these concepts are before exploring system development in any detail. CHA PTER 2 OBJECT-ORIENTED DEVElOPMENT AND THE UNIFIED PROCESS " This chapter also introduces the Unified Process as a comprehensive system deve.!­ opment methodology. It includes guidelines fo r completing every step in the system development process, and it defines six system development disciplines that system developers need to master. The development disciplines include business modeling. requirements, design, implementation, testing. and deployment. Additional suppon disciplines must also be mastered, most imponandy project management. The Unified Process and these. disciplines are emphasized throughout this text. Because. this text emphasizes object-orientE'd (00) development. objw-orienled concepts are briefly reviewed in this chapter. You probably firs tleamed about object­ orienled development in a programming course, so most of the.se conceptS should be familiar to you. We will discuss them throughout the text. One of the benefitS of object-orienled development is that the same conceptS use.d in 00 programming are used to define the requi rements and specify the design of the software. In other words, what you learned in 00 programming should be useful to you when learning 00 analysis and 00 design, and what you learn in analysis and design should be useful to you when programming. Fi nally, system deve.!opers need computer suppan tools to complete work tasks, including drawing tools and speciall y designed computer-aided system engineering (CASE) tools. This chapter presentS some examples of these software tools. At Rocky Mounlain Outfitters, one of Barbara Halifax's initial jobs as the project manager for the rustomer suppon system project is to make decisions about how best to apply the Unified Process to the development projecl. THE SYSTEMS DEVELOPMENT LIFE CYCLE Chapt~ I explained that systems analysts solve business problems. Fo r problem­ solving wo rk to be productivE', it needs to be organized and goal oriented. AnalystS project achievE' these results by organizing the work into projects. A projed is a planned under­ a planned undertaking that has taking that has a beginning and an end and that produces a desired result or product. a begmning and an end and The term syslem development project describes a planned undenaking that produces that produces a desired result or product a new info rmation system. Some system development projectS are very large. requiring thousands of hours of work by many people and spanning several calendar years. In the RMO case study introduced in Chapter I, the system being developed will be a moderately sized computer.based information system, requiring a moderately sized projecr lasting less than a year. Many system development projects are smaller, lasting a month or two. For a system development project to be successful, the people devel­ oping the system must have a detailed plan to follow. Success depends heavily on hav­ ing a plan that indudes an organized, methodical sequence of tasks and activities that rulminate with an information system that is reliable. robust. and efficient. One of the key, fundamental concepts in information system development is the systems developmenl life cycle. Businesses and organizations use information systems to support all the many, varied processes that a business needs to carry out its fu nc­ tions. As explained in Chapter I, there are many di fferent kinds of information sys­ tems, and each has itS own focus and purpose in supponing business processes. Each one of these information systems has a life of itS own, and we, as system developers, refer to th is idea as the lifl! cyde of Ii $)'Scem. During the life of an information system, it is fi rst conceived as an idea; then it is designed, built. and deployed during a develop­ ment project; and fi nally it is put into production and used to support the business. However, evE'n during itS productive use, a system is stit! a dynamic, living entily that is updated, modified, and rE'paired during smaller upgrading projects. This entire process of bui ld in g. deploying, using. and updating an information system is called " PART 1 SYSTEM DEVELOPMENT AND THE UNIFIED PROCESS "te-ms developm@nt life the 1fT /i ,or om .
Load more

Recommended publications
  • Writing and Reviewing Use-Case Descriptions
    Bittner/Spence_06.fm Page 145 Tuesday, July 30, 2002 12:04 PM PART II WRITING AND REVIEWING USE-CASE DESCRIPTIONS Part I, Getting Started with Use-Case Modeling, introduced the basic con- cepts of use-case modeling, including defining the basic concepts and understanding how to use these concepts to define the vision, find actors and use cases, and to define the basic concepts the system will use. If we go no further, we have an overview of what the system will do, an under- standing of the stakeholders of the system, and an understanding of the ways the system provides value to those stakeholders. What we do not have, if we stop at this point, is an understanding of exactly what the system does. In short, we lack the details needed to actually develop and test the system. Some people, having only come this far, wonder what use-case model- ing is all about and question its value. If one only comes this far with use- case modeling, we are forced to agree; the real value of use-case modeling comes from the descriptions of the interactions of the actors and the system, and from the descriptions of what the system does in response to the actions of the actors. Surprisingly, and disappointingly, many teams stop after developing little more than simple outlines for their use cases and consider themselves done. These same teams encounter problems because their use cases are vague and lack detail, so they blame the use-case approach for having let them down. The failing in these cases is not with the approach, but with its application.
    [Show full text]
  • The Guide to Succeeding with Use Cases
    USE-CASE 2.0 The Guide to Succeeding with Use Cases Ivar Jacobson Ian Spence Kurt Bittner December 2011 USE-CASE 2.0 The Definitive Guide About this Guide 3 How to read this Guide 3 What is Use-Case 2.0? 4 First Principles 5 Principle 1: Keep it simple by telling stories 5 Principle 2: Understand the big picture 5 Principle 3: Focus on value 7 Principle 4: Build the system in slices 8 Principle 5: Deliver the system in increments 10 Principle 6: Adapt to meet the team’s needs 11 Use-Case 2.0 Content 13 Things to Work With 13 Work Products 18 Things to do 23 Using Use-Case 2.0 30 Use-Case 2.0: Applicable for all types of system 30 Use-Case 2.0: Handling all types of requirement 31 Use-Case 2.0: Applicable for all development approaches 31 Use-Case 2.0: Scaling to meet your needs – scaling in, scaling out and scaling up 39 Conclusion 40 Appendix 1: Work Products 41 Supporting Information 42 Test Case 44 Use-Case Model 46 Use-Case Narrative 47 Use-Case Realization 49 Glossary of Terms 51 Acknowledgements 52 General 52 People 52 Bibliography 53 About the Authors 54 USE-CASE 2.0 The Definitive Guide Page 2 © 2005-2011 IvAr JacobSon InternationAl SA. All rights reserved. About this Guide This guide describes how to apply use cases in an agile and scalable fashion. It builds on the current state of the art to present an evolution of the use-case technique that we call Use-Case 2.0.
    [Show full text]
  • Challenges and Opportunities for the Medical Device Industry Meeting the New IEC 62304 Standard 2 Challenges and Opportunities for the Medical Device Industry
    IBM Software Thought Leadership White Paper Life Sciences Challenges and opportunities for the medical device industry Meeting the new IEC 62304 standard 2 Challenges and opportunities for the medical device industry Contents With IEC 62304, the world has changed—country by country— for medical device manufacturers. This doesn’t mean, however, 2 Executive summary that complying with IEC 62304 must slow down your medical 2 Changes in the medical device field device software development. By applying best practices guid- ance and process automation, companies have a new opportunity 3 What is so hard about software? to improve on their fundamental business goals, while getting through regulatory approvals faster, lowering costs and deliver- 4 Disciplined agile delivery: Flexibility with more structure ing safer devices. 4 Meeting the specification: A look at some of the details This paper will explore what IEC 62304 compliance means for manufacturers in some detail, and also describe the larger con- text of systems and software engineering best practices at work 6 Process steps for IEC 62304 compliance in many of today’s most successful companies. 7 Performing the gap analysis Changes in the medical device field 8 Choosing software tools for IEC 62304 The IEC 62304 standard points to the more powerful role that software plays in the medical device industry. Once hardware 11 Conclusion was king. Older systems used software, of course, but it was not the main focus, and there wasn’t much of a user interface. Executive summary Software was primarily used for algorithmic work. Not to overly The recent IEC 62304 standard for medical device software is generalize, but the focus of management was on building causing companies worldwide to step back and examine their hardware that worked correctly; software was just a necessary software development processes with considerable scrutiny.
    [Show full text]
  • The Timeboxing Process Model for Iterative Software Development
    The Timeboxing Process Model for Iterative Software Development Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur – 208016; India Aveejeet Palit, Priya Kurien Infosys Technologies Limited Electronics City Bangalore – 561 229; India Contact: [email protected] ABSTRACT In today’s business where speed is of essence, an iterative development approach that allows the functionality to be delivered in parts has become a necessity and an effective way to manage risks. In an iterative process, the development of a software system is done in increments, each increment forming of an iteration and resulting in a working system. A common iterative approach is to decide what should be developed in an iteration and then plan the iteration accordingly. A somewhat different iterative is approach is to time box different iterations. In this approach, the length of an iteration is fixed and what should be developed in an iteration is adjusted to fit the time box. Generally, the time boxed iterations are executed in sequence, with some overlap where feasible. In this paper we propose the timeboxing process model that takes the concept of time boxed iterations further by adding pipelining concepts to it for permitting overlapped execution of different iterations. In the timeboxing process model, each time boxed iteration is divided into equal length stages, each stage having a defined function and resulting in a clear work product that is handed over to the next stage. With this division into stages, pipelining concepts are employed to have multiple time boxes executing concurrently, leading to a reduction in the delivery time for product releases.
    [Show full text]
  • Descriptive Approach to Software Development Life Cycle Models
    7797 Shaveta Gupta et al./ Elixir Comp. Sci. & Engg. 45 (2012) 7797-7800 Available online at www.elixirpublishers.com (Elixir International Journal) Computer Science and Engineering Elixir Comp. Sci. & Engg. 45 (2012) 7797-7800 Descriptive approach to software development life cycle models Shaveta Gupta and Sanjana Taya Department of Computer Science and Applications, Seth Jai Parkash Mukand Lal Institute of Engineering & Technology, Radaur, Distt. Yamunanagar (135001), Haryana, India. ARTICLE INFO ABSTRACT Article history: The concept of system lifecycle models came into existence that emphasized on the need to Received: 24 January 2012; follow some structured approach towards building new or improved system. Many models Received in revised form: were suggested like waterfall, prototype, rapid application development, V-shaped, top & 17 March 2012; Bottom model etc. In this paper, we approach towards the traditional as well as recent Accepted: 6 April 2012; software development life cycle models. © 2012 Elixir All rights reserved. Keywords Software Development Life Cycle, Phases and Software Development, Life Cycle Models, Traditional Models, Recent Models. Introduction Software Development Life Cycle Models The Software Development Life Cycle (SDLC) is the entire Software Development Life Cycle Model is an abstract process of formal, logical steps taken to develop a software representation of a development process. SDLC models can be product. Within the broader context of Application Lifecycle categorized as: Management (ALM), the SDLC
    [Show full text]
  • Multi Objective Analysis for Timeboxing Models of Software Development
    MULTI OBJECTIVE ANALYSIS FOR TIMEBOXING MODELS OF SOFTWARE DEVELOPMENT Vassilis C. Gerogiannis and Pandelis G. Ipsilandis Department of Project Management, Technological Education Institute of Larissa, Larissa, Greece Keywords: Software Project Management, Iterative Development, Timeboxing, Project Scheduling, Linear Programming, Multi-Objective Optimization. Abstract: In iterative/incremental software development, software deliverables are built in iterations - each iteration providing parts of the required software functionality. To better manage and monitor resources, plan and deliverables, iterations are usually performed during specific time periods, so called “time boxes”. Each time box is further divided into a sequence of stages and a dedicated development team is assigned to each stage. Iterations can be performed in parallel to reduce the project completion time by exploiting a “pipelining” concept, that is, when a team completes the tasks of a stage, it hands over the intermediate deliverables to the team executing the next stage and then starts executing the same stage in the next iteration. In this paper, we address the problem of optimizing the schedule of a software project that follows an iterative, timeboxing process model. A multi objective linear programming technique is introduced to consider multiple parameters, such as the project duration, the work discontinuities of development teams in successive iterations and the release (delivery) time of software deliverables. The proposed model can be used to generate alternative project plans based on the relative importance of these parameters. 1 INTRODUCTION team of experts is usually assigned to each stage, i.e., a team for a stage performs only the activities In iterative and incremental development, software for that stage.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • The Unified Software Development Process and Framework Development
    Doğuş Üniversitesi Dergisi, 2002, (5), 109-122 THE UNIFIED SOFTWARE DEVELOPMENT PROCESS AND FRAMEWORK DEVELOPMENT Abdelaziz Khamis & Ashraf Abdelmonem Department of Computer Science, Institute of Statistics, Cairo University ABSTRACT: Application frameworks are a very promising software reuse technology. The development of application frameworks is a complex process. Many methodologies and approaches have been proposed with the purpose of minimizing the complexities. The Unified Software Development Process directly addresses the complexity challenge of today's software applications. in this paper, we explore the role of the Unified Software Development Process together with a popular CASE tool: Rational Rose, in managing the complexity of developing application frameworks. Keywords: Application Frameworks, The Unified Software Development Process, Model Tracing Tutors, Rational Rose. ÖZET: Uygulama iskelet yapıları çok umut vaadeden bir yeniden kullanım yazılım teknolojisidir. Uygulama iskelet yapılarının geliştirilmesi karmaşık bir süreci gerektirir. Bu karmaşık süreci minimize etmek amacıyla birçok yöntem ve yaklaşım önerilmiştir. Birleşik Yazılım Geliştirme Süreci bugünkü yazılım uygulamalarındaki karmaşıklık engelini direkt olarak hedefleyen bir yöntemdir. Bu yazıda uygulama iskelet yapılarındaki karmaşıklığın yönetimi konusunda Birleşik Yazılım Geliştirme Süreci'nin rolü yaygın olarak kullanılan bir CASE (Bilgisayar Destekli Yazılım Mühendisliği) aracı olan "Rational Rose" ile birlikte araştırılmaya çalışılmıştır. Anahtar Kelimeler: Uygulama Geliştirme Yapıları, Birleşik Yazılım Geliştirme Süreci, Model İzleme Öğretmeni, Rational Rose. 1. Introduction The reuse of software components is recognized as an important way to increase productivity in software development (Jacobson, Griss and Jonsson, 1997). Application frameworks are a very promising softvvare reuse technology. The concept of framevvorks makes it possible to reuse not just code, but also analysis and design (Fayad, Schmidt and Johnson, 1999; Fayad and Schmidt, 1997).
    [Show full text]
  • An Analysis on Waterfall and RUP Models
    Journal of Engineering, Computing and Architecture ISSN NO: 1934-7197 An Analysis on Waterfall and RUP Models Dr. K. Sunil Manohar Reddy Associate Professor, Department of CSE, Matrusri Engineering College, Hyderabad, Telangana. [email protected] Abstract: Two of the vastly used software engineering processes are Waterfall model and Rational Unified Process (RUP) model. The waterfall model is a classical model of software engineering. It is used in governmental projects as well as many major companies associated with software engineering. RUP is a unified model used for large business applications. The main concern in this research is to represent the mentioned models of software development and compare them to show pros and cons of each model. Keywords: Waterfall Model, Unified Process Model, Agile Models 1. Introduction Computer is considered as a time saving mechanism and its progress helps in executing long, complex, repeated processes at a high speed and short time. Noticeably, the number of companies that produce software programs for the purpose of facilitating works of offices, administrations, banks, etc., has increased recently which results in the difficulty of enumerating such companies. During the last five decades, software has been developed from a tool used for solving a problem to a product in itself. Software consists of instructions and programs that contain a collection that has been established to be a part of software engineering procedures [1]. Moreover, the aim of software engineering is to create a suitable work
    [Show full text]
  • The IBM Rational Unified Process for System Z
    Front cover The IBM Rational Unified Process for System z RUP for System z includes a succinct end-to-end process for z practitioners RUP for System z includes many examples of various deliverables RUP for System z is available as an RMC/RUP plug-in Cécile Péraire Mike Edwards Angelo Fernandes Enrico Mancin Kathy Carroll ibm.com/redbooks International Technical Support Organization The IBM Rational Unified Process for System z July 2007 SG24-7362-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (July 2007) This edition applies to the IBM Rational Method Composer Version 7.1 © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this IBM Redbooks publication . .x Become a published author . xii Comments welcome. xii Part 1. Introduction to the IBM Rational Unified Process for System z. 1 Chapter 1. Introduction. 3 1.1 Purpose. 4 1.2 Audience . 4 1.3 Rationale . 4 1.4 Scope . 5 1.5 Overview . 5 Part 2. The IBM Rational Unified Process for System z for Beginners . 9 Chapter 2. Introduction to the IBM Rational Unified Process and its extension to Service-Oriented Architecture. 11 2.1 Overview . 12 2.2 Introduction to RUP. 13 2.2.1 The heart of RUP . 13 2.2.2 The IBM Rational Method Composer (RMC) platform . 13 2.3 Key principles for successful software development.
    [Show full text]
  • A Hybrid Approach Using RUP and Scrum As a Software Development Strategy Dalila Castilla University of North Florida
    UNF Digital Commons UNF Graduate Theses and Dissertations Student Scholarship 2014 A Hybrid Approach Using RUP and Scrum as a Software Development Strategy Dalila Castilla University of North Florida Suggested Citation Castilla, Dalila, "A Hybrid Approach Using RUP and Scrum as a Software Development Strategy" (2014). UNF Graduate Theses and Dissertations. 514. https://digitalcommons.unf.edu/etd/514 This Master's Thesis is brought to you for free and open access by the Student Scholarship at UNF Digital Commons. It has been accepted for inclusion in UNF Graduate Theses and Dissertations by an authorized administrator of UNF Digital Commons. For more information, please contact Digital Projects. © 2014 All Rights Reserved A HYBRID APPROACH USING RUP AND SCRUM AS A SOFTWARE DEVELOPMENT STRATEGY by Dalila Castilla A thesis submitted to the School of Computing In partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences UNIVERSITY OF NORTH FLORIDA SCHOOL OF COMPUTING August, 2014 Copyright (©) 2014 by Dalila Castilla All rights reserved. Reproduction in whole or in part in any form requires the prior written permission of Dalila Castilla or designed representative. ii The thesis “A Hybrid Approach Using RUP and Scrum as a Software Development Strategy” submitted by Dalila Castilla in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences has been Approved by the thesis committee: Date ___________________________________ _____________________ Dr. Robert F. Roggio Thesis Advisor and Committee Chairperson ___________________________________ _____________________ Dr. Ching-Hua Chuan ___________________________________ _____________________ Dr. Sherif A. Elfayoumy Accepted for the School of Computing: ___________________________________ _____________________ Dr.
    [Show full text]
  • Unified Process
    Information Systems Concepts Unified Process Roman Kontchakov Birkbeck, University of London Based on Chapter 3, 5 and 21 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design Using UML, (4th Edition), McGraw Hill, 2010 1 Outline n RUP / USDP n Section 3.4.1 (pp. 77 – 79) n Section 5.4 (pp. 128 – 135) n Section 21.3 (pp. 614 – 618) 2 Unified Process n Unified Software Development Process (USDP) n A public domain development methodology originally proposed by the same team (in Rational Software, 1999) who created UML n brought the Booch method, OMT and Objectory together n Large and complex n significant learning curve involved, or tailor to fit n Rational Unified Process (RUP) n Proprietary methodology owned by IBM (since 2003) n The most mature OO methodology to date n USDP has been largely superseded by RUP (though they are very similar in their main aspects) 3 Underlying Principles n Iterative n Incremental n Requirements (use case) driven n Component based n Architecture centric n Visual modelling techniques 4 UP is Use-Case Driven A use case is a single interaction between user and system. 5 Phases n Phases are organized along time Each phase consists of a number of iterations n Inception Phase n Determining the scope and purpose of the project n Elaboration Phase n Capturing the requirements n Determining the structure of the system n Construction Phase n Building the system n Transition Phase n Product installation and roll-out 6 Milestones n Phases matter to project managers n Phases are sequential and delineated
    [Show full text]