Slide1 l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 10

RUP PowerPoint PPT Presentation


  • 126 Views
  • Uploaded on
  • Presentation posted in: General

RUP. The Rational Unified Process. SDLC. The Standard Development Life Cycle (SDLC) - Making implementations a breeze utilizing an iterative development approach. THE RIGHT DOCUMENTATION FOR THE PROJECT. The Problem Statement – Extracted from the Vision Document for the purposes of Scoping

Download Presentation

RUP

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Slide1 l.jpg

RUP

The Rational Unified Process


Slide2 l.jpg

SDLC

The Standard Development Life Cycle (SDLC) - Making implementations a breeze utilizing an iterative development approach


The right documentation for the project l.jpg

THE RIGHT DOCUMENTATION FOR THE PROJECT

  • The Problem Statement – Extracted from the Vision Document for the purposes of Scoping

  • Glossary – List of terms utilized in the project and across the organization.

  • Supplementary Requirements Specification (SRS) – Houses the non functional requirements of the system

    - Objectives- Scope

    - References- Functionality

    - Usability- Reliability

    - Performance- Supportability

    - Security- Design Constraints

  • Use Case Model


Uml diagrams l.jpg

UML DIAGRAMS

  • Actors – Depict the system or person performing the action

  • Use Cases – Describe the action the actor is performing


Use case model elements l.jpg

USE CASE MODEL- ELEMENTS

  • Objectives

  • Scope

  • References

  • Functionality

  • Usability

  • Reliability

  • Performance

  • Supportability

  • Security

  • Design Constraints


Transforming use case business requirements into functional design spec l.jpg

TRANSFORMING USE CASE BUSINESS REQUIREMENTS INTO FUNCTIONAL DESIGN SPEC

  • The BA will transform the use case requirements documents and business rules into a Functional Design Document that the Developers will use to configure and build the system.


Functional design document elements l.jpg

FUNCTIONAL DESIGN DOCUMENT ELEMENTS

  • Main Flows – This is the Happy Flow defined in RUP as the path taken most frequently where there are no errors or exceptions.

  • Alternate Flows – The path taken for each exception and error.

  • Pre - Conditions – The condition that must exist prior to the execution of the use case

  • Post Conditions – The condition after the use case has been executed or end state

  • CRUD Matrix – Create, Read, Update and Delete.

  • Screen Navigations Flows - How the user navigates from view to view or screen to screen to complete a particular process.

  • Screen Shots - Screen and view used to meet the business requirement

  • Matrix of characters - Field elements

  • LOV’s – List of Values

  • Business Rules – Associated to each use case

  • Assumptions


Technical design document l.jpg

TECHNICAL DESIGN DOCUMENT

  • The technical design document (TDD) will be constructed from the functional design document (FDD) once sign off has occurred. The technical design document (TDD) will be utilized in the construction phase of the SDLC.


Training and testing l.jpg

TRAINING AND TESTING

The testing and training material will be derived from the FDD. This begins the transition phase of the project. More specifically the main flows and alternate flows will be to the level of detail that will allow expeditious creation of the training and testing material.


Implementation of rup l.jpg

IMPLEMENTATION OF RUP

  • The approach that works best is a phased approach starting with the inception phase of the project. I estimate that I will be able to train a class of 4-6 people in two 8 hours sessions. I will need the rational rose enterprise edition software loaded on the desktop applications

  • The elaboration phase - two 8 hour sessions

  • The construction phase - three 8 hour sessions

  • The transition phase - two 8 hour sessions

    In addition, I will need one 8 hour training session on utilizing the req pro tool for constructing the traceability matrix.

    120 additional hours will be needed to construct the training material for distribution to the class.


  • Login