1 RUP Workshop By George Merguerian Senior Partner Business Management Consultants

Slides:



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

National Database Templates for the Biosafety Clearing-House Application (NDT-nBCH) Overview of the US nBCH Applications.
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--
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
1 The Database Application Development Process The Database Application Development Process.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
GAI Proprietary Information
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Computer Science 162 Section 1 CS162 Teaching Staff.
Nu Project Management Office A web based tool to Manage Projects.
Chapter 3: The Project Management Process Groups
COMP 350: Object Oriented Analysis and Design Lecture 2
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
AJAC Systems Hotel Reservation System
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
“This presentation is for informational purposes only and may not be incorporated into a contract or agreement.”
RUP Requirements RUP Artifacts and Deliverables
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
ABSTRACT Zirous Inc. is a growing company and they need a new way to track who their employees working on various different projects. To solve the issue.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.
Business Analysis and Essential Competencies
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Software Process Models.
An Introduction to Progress Arcade ™ June 12, 2013 Rob Straight Senior Manager, OpenEdge Product Management.
Object-Oriented Analysis & Design Subversion. Contents  Configuration management  The repository  Versioning  Tags  Branches  Subversion 2.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
By Matt Baker Eric Sprauve Stephen Cauterucio. The Problem Advisors create a sign-up sheet to be posted on the door of their office. These sign-up sheets.
Project 2003 Presentation Ben Howard 15 th July 2003.
Chapter 7 Applying UML and Patterns Craig Larman
Project Presentation eProcurement System. M.TECH S16- Team S03 Institute of Systems Science Table of Content Project Background Project Requirement User.
Software Engineering Saeed Akhtar The University of Lahore Lecture 6 Originally shared for: mashhoood.webs.com.
Project management.  To explain the main tasks undertaken by project managers  To introduce software project management and to describe its distinctive.
MSE Presentation 1 By Padmaja Havaldar- Graduate Student Under the guidance of Dr. Daniel Andresen – Major Advisor Dr. Scott Deloach-Committee Member Dr.
Module 1 – Lesson 6 Ms. Tracy. Bell Ringer What is the typical useful life for a personal computer?
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
CSE 436—Software Development Models Ron K. Cytron 10 October 2005.
CSE 436—Software Development Models Ron K. Cytron 16 October 2006.
MIS 7003 MBA Core Course in MIS Professor Akhilesh Bajaj The University of Tulsa Introduction to S/W Engineering © All slides in this presentation Akhilesh.
Project Management Inspections and Reviews 1 February.
The principles of an object oriented software development process Week 04 1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Software Engineering Principles Practical Advice and Steps for Managing Your Project.
Introduction TO Network Administration
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook
Proctor Caching Overview. 2 Proctor Caching Diagram.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Class 5 – Planning IT Projects
TK2023 Object-Oriented Software Engineering
Introduction to CAST Technical Support
Office 365 Security Assessment Workshop
Netscape Application Server
Project Center Use Cases Revision 2
Multilevel Marketing Tree Viewer
Systems Analysis and Design
Project Center Use Cases Revision 3
Project Center Use Cases Revision 3
Requirements and the Software Lifecycle
COMP 350: Object Oriented Analysis and Design Lecture 2
Object Oriented Analysis and Design
Presentation transcript:

1 RUP Workshop By George Merguerian Senior Partner Business Management Consultants

© BMC 2006 Business Management Consultants 2 Workshop – 20 Minutes 1. My Time is a simple one person project applying RUP approach 2. Read the contents on each slide and respond to the questions asked Work in teams of 6 per group and assign roles for each team member and agree on what artifact each member produces: Work in teams of 6 per group and assign roles for each team member and agree on what artifact each member produces: Suggested Roles Suggested Roles A Project Manager Facilitates the discussion A Project Manager Facilitates the discussion A Time keeper keeps the team on time A Time keeper keeps the team on time A Reporter describes to the seminar the artifacts produced A Reporter describes to the seminar the artifacts produced

© BMC 2006 Business Management Consultants 3 Project My Time 1.Problem: In a small company owned by Gary, Gary’s team is unable to capture effort spent on various software development projects. As a result the team cannot monitor progress against estimates. This makes it difficult to charge customers correctly, and estimate effort required for future projects. 2.Vision statement: A software tool that measures time spent, gathers data and allows its extraction would solve the above problems. 3.Stakeholders: Gary’s team, your organisation which is specialised in PM software, Administration people in Gary’s organisation 4.You meat Gary and after an interview you are back in the office and do the following: 1.Make a plan to deliver a solution to the above problem in one week. Use the terminology you learned – when will you do inception, etc. etc Draw a table indicating each day of the week and your planned activities 2.List 4 Use Cases bearing in mind the above points 3.Draw a basic architecture of the system 4.When do you mitigate business risks? And Technical risks?

© BMC 2006 Business Management Consultants 4 Project My Time - Plan MondayTuesdayWednesdayThursdayFridaySaturday Inception Vision Plan Bus. Case Risks Prototype (elaborate on reqts, Use a database already in hand, use Java applet to interface DB, user guide for the API) Construction Finish Design Code and Test on laptop Design Code Test – initial operation capability Delivery LCO: Get OKGet OKShow Beta Version Elaboration Prototype (demo prototype) Use Cases Tests LCO: Architecture Design Code Test Transition Improvements

© BMC 2006 Business Management Consultants 5 Project My Time 1.Problem: In a small company owned by Gary, Gary’s team is unable to capture effort spent on various software development projects. As a result the team cannot monitor progress against estimates. This makes it difficult to charge customers correctly, and estimate effort required for future projects. 2.Vision statement: A software tool that measures time spent, gathers data and allows its extraction would solve the above problems. 3.Stakeholders: Gary’s team, your organisation which is specialised in PM software, Administration people in Gary’s organisation 4.Use Cases –Measure time for an activity –Extract weekly time sheets –Consolidate data for project –Set up tool and database for project

© BMC 2006 Business Management Consultants 6 A simplified example– Project My Time – Architecture Sketch Applet Browser Developer Computer CGI Server Database Company System

© BMC 2006 Business Management Consultants 7 5.Gary wants all the developers to input the time data in the DB over their LAN 6.The Developers do not always work from the same machines (especially during testing) The above information (the network part) will impact the architecture. Also there is now need for an administrator to maintain the DB  To mitigate Architecture risk – shift the LCA Milestone to end of Tuesday 7.Old Risks: Dbase is expensive, Connection via internet of all PCs (some not possible) 8.New Risks: Synchronisation of updates to the DB; Can the same user be connected from 2 different machines – if yes the impact, what if dialogue with one user dies and locks off the others 9.Revised Budget – extra day of work A simplified example– Project My Time – Revised Vision

© BMC 2006 Business Management Consultants 8 A simplified example– Project My Time – Progress (Elaboration) 11.Two Major Use cases: –Timing an Activity –Getting a Tally of the Data 12. Draw Sequence Diagram prompts new questions – are the activities pre- defined? The code shall run on Unix or Windows NT 13.Develop an Applet for the product Interface 14.Test the system – Applet on laptop and DB on Desktop. Occasionally its crashing – why? 15. Develop more use cases for system administration 1.Clean up Database 2.Add a user 3.Clean up the Activity list

© BMC 2006 Business Management Consultants 9 A simplified example– Project My Time – Plan (Revised during Elaboration) MondayTuesdayWednesdayThursdayFridaySaturday Inception Vision Plan Bus. Case Risks Prototype (elaborate on reqts, Use a database already in hand, use Java applet to interface DB, user guide for the API) Mitigate Risks (Dbase, connection via internet of all PCs) Construction Finish Design Code and Test on laptop (single-person version) Design (client- server version) Code Test Show Beta Version LCO: Get OKGet OKTransition Improvements Elaboration Prototype (demo prototype) Use Cases Tests LCO: Architecture Design Code Test – initial operation capability Design Code Test Delivery

© BMC 2006 Business Management Consultants 10 A simplified example– Project My Time – Progress (Construction) 16.Resolve system crash problem (database version issue) 17.Develop a Configuration Management Plan – take a snapshot of each iteration 18.Make complete tests of all use cases 19.Make a dialogue for extracting data into Excel sheet with graphs 20.Customer calls and says a person may work on more than one activity and wants to keep several time counters active at the same time  Change the Vision, Do a Risk Analysis  Renegotiate requirements  Delivery Friday evening 21.Based on Use Cases build web based user’s guide 22.More testing - fix bugs 23.Capacity testing 24.Test concurrency – update database from two machines at once errors 26.Test same user from two machines updating – one entry missing 27.Fix problems 28.Run Beta version at client’s side, record needed improvements – 12 improvements needed 29.Prepare next release – CM version Finish release notes 31.Ready to ship Version With the processes documented it would be easy to go for a version 2.0 when the client asks for it

© BMC 2006 Business Management Consultants 11 A simplified example– Project My Time – Plan (Revised during Construction) MondayTuesdayWednesdayThursdayFridaySaturday Inception Vision Plan Bus. Case Risks Prototype (elaborate on reqts, Use a database already in hand, use Java applet to interface DB, user guide for the API) Mitigate Risks (Dbase, connection via internet of all PCs) Construction Configuration Management Finish Design Code and Test on laptop (single-person version) New requirement comes in – delay delivery to Saturday morning Design in New Requirement Design (client- server version) Code Test Design code test Delivery LCO: Get OKGet OKShow Beta Version Elaboration Prototype (demo prototype) Use Cases Tests LCO: Architecture Design Code Test – initial operation capability Design Code Test – fix bugs Build User Guide Transition Improvements