Introduction to OOAD & Rational Rose cyt

2 Outline RUP OOAD Rational Rose

3 RUP Product

4 Rational Unified Process (RUP)

5 Inception Phase

6 Requirements Discipline Workflow Detail: Analyze the Problem

7 Use Case Realization Architectural Design OOAD Process Vision Problem Statement Use Case Model Design Model Analysis Model RequirementsAnalysis & Design

8 Architectural Blueprints The 4+1 View Model of Software Architecture

9 Diagram window Diagram toolbar (unique to each type of diagram) Browser window (used to organize and navigate) Documentation window Standard toolbar Standard menu Rational Rose Environment Status bar Can be hidden, docked or floating

10 Use Cases are Employed Throughout the Process

11 Use Case View Use case model Logical View Analysis model Design model Use case realization Process View Component View Deployment 4+1 View Software architecture consists of 5 concurrent views Rational Rose provides 5 different perspectives/views ViewTarget Audience Use-Case ViewEnd User Logical ViewAnalyst/Designer Process ViewSystem Integrator Deployment ViewSystem Engineer Implementation View Programmer

12 The Use-Case View From end-users' perspective Use Case Model Captures system's intended functions and interactions with environment  use case diagrams  use case flow of events (file)  supplemental documentation (file)  activity diagrams (optional)

13 The Logical View Concerned with functional requirements of the systems From analyst/designer perspective Includes use case realization diagrams class diagrams interaction diagrams Collaboration and Sequence Diagram statechart diagrams (optional) activity diagrams (optional)

14

15 The Process View Presents a perspective for the System Integrators Non-functional requirements Include:  Performance  Scalability  Availability  Fault Tolerance  Throughput  Concurrency and synchronization  threads  processes Note: Not necessarily a single processing environment

16 The Implementation View Called Component View in Rational Rose Aimed at Programmers Captures organization of static software modules:  packaging, layering, and configuration management  source code files  data files  components  executable, etc. Concerned with derived requirements:  ease of development  software management  reuse  constraints imposed by programming language and development tools  sub-contracting  off-the-shelf components

17 The Deployment View For System Engineers Used only for distributed systems Captures how executables and other run-time components are to be mapped to platforms or computer nodes Includes:  Performance – Delivery  Scalability – Installation  Availability  Fault Tolerance  Deployment Diagram

18 Demo

19 範例 & Tutorial er_v2003_Java_platform_edition_tutorial.rarhttp:// /~cyt/temp/IBM_Rational_XDE_Develop er_v2003_Java_platform_edition_tutorial.rar nMSWordV1_1_3rdn.rarhttp:// /~cyt/temp/eStoreRDASampleApplicatio nMSWordV1_1_3rdn.rar