RUP Analysis - PowerPoint PPT Presentation

1 / 12
About This Presentation
Title:

RUP Analysis

Description:

Help find missing or incomplete information. Help determine quality characteristics (NFR) ... Initiate transfer of money on due date ... – PowerPoint PPT presentation

Number of Views:20
Avg rating:3.0/5.0
Slides: 13
Provided by: robe65
Category:
Tags: rup | analysis | missing | money

less

Transcript and Presenter's Notes

Title: RUP Analysis


1
RUP Analysis
  • CS4320
  • Fall 2005

2
Purpose
  • An intermediate step to
  • Transition from Use Case to Design
  • Help find inconsistency
  • Help find missing or incomplete information
  • Help determine quality characteristics (NFR)

3
Analysis Artifacts
  • Analysis Class representation of 1 or more
    design classes for functional requirements
  • Boundary Class models interactions between
    system and actors
  • Entity Class models information that is
    long-lived and persistent
  • Control Class represents sequencing,
    coordination, complex calculations, and control
    of other objects

4
Analysis Class Diagram ExampleUC Pay Invoice
Order Confirmation
5
Analysis Collaboration DiagramUC Pay Invoice
6 Sched Payment
1 Browse Invoice
7 Schedule Payment
2 Browse
8 New
3 Check Invoice
4 Get
5 Get
Order Confirmation
6
Analysis Class Responsibilities
  • Payment Scheduler
  • Create Payment Request
  • Track Payments that have been scheduled
  • Send notification of when payment effected
  • Initiate transfer of money on due date
  • Notify an invoice that it has been scheduled for
    payment and when it has been paid

7
Basic Activity Diagrams
  • Good for modeling business work flows related to
    a use case

Start Activity
Join
End Activity
Fill Order
Decision
Action
Fork
Merge
8
Activity Sample
Sales
Accounting
Shipping Dept
Receive Order
Send Invoice
Fill Order
rush
else
Receive Payment
Overnite Delivery
Regular Delivery
Close Order
9
Analysis UI Prototype
Invoice No 348u5
  • Widgets 25 _at_ 2.00 50.00
  • Wodget 1 _at_ 9.00 9.00
  • Total 59.00

10
Analysis Packages
  • Group Similar use cases and their realizations
    together
  • A way to organize classes

Pay Invoice
ltlttracegtgt
Buyer Invoice Management
11
Development Team Steps
  • Create Individual Artifacts
  • Structure Use Cases
  • Merge analysis classes to eliminate duplication
  • Group into logical packages (develop logical
    architecture)

12
What are we doing of Friday
  • Iteration Plan
  • Review use cases by classmates
  • Need 2 iterations over semester
  • What are we doing this iteration?
  • Use whatever estimation technique you want.
  • Follow format on UPEDU website for iteration plan
  • Only do as much SDP as necessary
  • Work on analysis-level diagrams
Write a Comment
User Comments (0)
About PowerShow.com