Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified...

Rational Unified Process Fundamentals

Module 4: Core Workflows II - Concepts

Rational Unified Process Fundamentals

Module 4: Core Workflows II - Concepts

Rational Unified Process Fundamentals, v. 2000.02.10Copyright © 2000 Rational Software, all rights reserved 2

ObjectivesObjectives

Understand Core Workflow Concepts for Implementation Test Deployment Configuration & Change Management Environment Business Modeling


Where Are We?Where Are We?

Core Workflows - II Implementation Test Deployment Configuration & Change Management Environment Business Modeling


ImplementationModel

Core Workflow: ImplementationCore Workflow: Implementation

The purposes of Implementation are: To implement classes and objects in terms of

components. To define the organization of the components in

terms of implementation subsystems. To test the developed components as units. To create an executable system.

Implementation results in an Implementation Model.


What Is an Implementation Model?What Is an Implementation Model?

Trading Services

Telephone Banking

A

B

<<import>> <<compilation>>

Components and implementationsubsystems in a Telephone Banking System.

An implementation model consists of: Components Implementation

Subsystems Components include:

Deliverable components, such as executables.

Components from which the deliverables are produced, such as source code files.


Concept: BuildConcept: Build

Operational version of a system or part of a system

Demonstrates a subset of the capabilities provided in the final product

Integral part of the iterative lifecycle Provides review points Helps uncover integration problems as soon

as they are introduced


Core Workflow: TestCore Workflow: Test

Purpose: To assess the level of quality of the product To verify the interaction between objects,

components. To verify the proper integration of all

components of the software. To verify that all requirements have been

correctly implemented. To identify and ensure defects are

addressed prior to the deployment of the software.


What Is a Test Model?What Is a Test Model?

Initiate

withdrawal

Finalize withdrawal

of custom amount

A test model consists of:Test CasesTest Procedures

A test case can be implemented by one or more test procedures.A test procedure may implement (the whole or parts of) one or more test cases.Use cases are the primary input to identifying test cases. Test cases and test procedures

in an ATM System.

Withdrawal of

a pre-set amount

Withdrawal of

custom amount

Finalize withdrawal

of pre-set amount

Test cases

Test procedures


Use Cases Drive the Test ModelUse Cases Drive the Test Model

SupplementarySpecifications

Use-Case ModelTest

Test Model


Testing Use CasesTesting Use Cases

The complete behavior of a use case is tested using test cases and test procedures

Test Procedure

Test Case

Test Case

Test Procedure


Concept: Test Automation ToolsConcept: Test Automation Tools

Data acquisition Static measurement Dynamic measurement Simulators or Drivers Test management tools


Core Workflow: DeploymentCore Workflow: Deployment

Purpose: Describe the activities associated with ensuring that the software product is available for its end users Describes three modes of product deployment

• Custom install• ‘Shrink wrap’• Access via the Internet

Testing at the installation and target sites Beta testing Release to customer


Use Cases and End-User DocumentationUse Cases and End-User Documentation

Use-Case ModelDeployment

End User Support Material•User’s Guide•On-line Help•Demos•Tutorials•Training Material


Core Workflow: Configuration & Change ManagementCore Workflow: Configuration & Change Management

Purpose: track and maintain integrity of project artifacts change control configuration identification and management configuration status accounting change tracking version selection software manufacture workspace management


The Configuration and Change Management (CCM) CubeThe Configuration and Change Management (CCM) Cube


Configuration Management (CM) -Configuration Management (CM) -

Describes the product structure and identifies its constituent configuration items that are treated as single versionable entities in the configuration management process.

Deals with defining configurations, building and labeling, and collecting versioned artifacts into constituent sets and maintaining traceability between these versions.


Change Request Management (CRM)Change Request Management (CRM)

Addresses the organizational infrastructure required to assess the cost and schedule impact of a requested change to the project.

Addresses the workings of a Change Review Team or Change Control Board.


Configuration Status Accounting Configuration Status Accounting

Describes the 'state' of the product based on the type, number, rate, and severity of defects found and fixed during the course of product development.

Metrics derived under this aspect, either through audits or raw data, are useful in determining the overall completeness status of the project.


Core Workflow: EnvironmentCore Workflow: Environment

Purpose: Support the development organization, both with process and tools Process configuration Process implementation Process improvement Managing organizational change Development environment


Development CaseDevelopment Case

Describes the development process that you have chosen to follow in your project

Created early in Inception Updated during project

Development Case

Select from RUP knowledge base

Minimize cost of process definition


Development Case ExampleDevelopment Case Example

Brief Outline 1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms

and Abbreviations 1.4 References 1.5 Overview 2. Overview of the

Development Process 3. Iteration Workflows 4. Business Modeling 5. Requirements 6. Analysis & Design 7. Implementation 8. Test 9. Deployment

10. Configuration &

Changes Management


Core Workflow: Business ModelingCore Workflow: Business Modeling

Purpose Understand structure and dynamics of the

organization in which the system is to be deployed

Understand and improve target organization Ensure customer/end user common

understanding of target organization Derive system requirements to support the

target organization Uses an approach very similar to that of

system development


Two business models

What a Business Models ShowsWhat a Business Models Shows

Customers Business processes Organizational

structure Roles and

responsibilities Products Internal deliverables Events

Business Object Model

Business Use-Case Model


Six Scenarios for Business ModelingSix Scenarios for Business Modeling

Organization chart Domain modeling One business, many systems Generic business model New business Revamp


Business Modeling and e-businessBusiness Modeling and e-business

e-Business Involves building Internet solutions to implement

business processes Business modeling

Applies model-based technology to the business and the business tools


Summary: Core WorkflowsSummary: Core Workflows

What are the parts of an Implementation Model?

What is the role of use cases in the test workflow?

How are use cases used in the deployment workflow?

What are the elements of configuration and change management in RUP?

What is a development case? How is business modeling important for e-

business development?

Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified...

Documents

Transcript of Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified...