uml keerthi

7/31/2019 Uml Keerthi

1/25

Rational Unified ProcessRational Unified Process

1

PresentedBy

G.Keerthi SatyaM.Tech. (S.E.)

Roll. No: 11031D2507


2/25

What is the Rational UnifiedWhat is the Rational Unified

Process?Process?

A software engineering processA software engineering process

Process frameworkProcess framework

2


3/25

Dynamic Structure: IterativeDynamic Structure: Iterative

DevelopmentDevelopment

The sequential, or waterfall, process isThe sequential, or waterfall, process is

fine for small projects.fine for small projects.

An iterative process breaks a developmentAn iterative process breaks a development

cycle into a succession of iterations.cycle into a succession of iterations.

A development cycle is divided into aA development cycle is divided into a

sequence of four phases that partition thesequence of four phases that partition the

sequence of iterations. The phases aresequence of iterations. The phases are

inception, elaboration, construction, andinception, elaboration, construction, and

transition.transition.

3


4/25

iterative anditerative andincrementalincrementalprocess

process

partitions a system by functionalitypartitions a system by functionality Early release starts with small, functional subsystem, laterEarly release starts with small, functional subsystem, later

releases add functionalityreleases add functionality Top part of this figure shows how incremental developmentTop part of this figure shows how incremental development

builds up to full functionalitybuilds up to full functionality

improves overall system in each releaseimproves overall system in each release Delivers a full system in the first release, then changes theDelivers a full system in the first release, then changes the

functionality of each subsystem with each new releasefunctionality of each subsystem with each new release

Many organizations combine iterative and incremental approachesMany organizations combine iterative and incremental approaches
http://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpghttp://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpghttp://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpghttp://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpghttp://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpghttp://www.cse.lehigh.edu/~glennb/oose/figs/pfleeger/iterative.jpg


5/25

Why Iterative and IncrementalWhy Iterative and Incremental

5


6/25

From sequential to an iterativeFrom sequential to an iterative

cyclecycle

6


7/25


8/25

Each iteration has:Each iteration has:

8


9/25

Develop in small stepsDevelop in small steps

9


10/25

An Iteration is Not HackingAn Iteration is Not Hacking

10


11/25

Getting a RobustGetting a Robust

ArchitectureArchitecture

11


12/25

Handling ChangingHandling Changing

RequirementsRequirements

12


13/25


14/25

Achieving ContinuousAchieving Continuous

IntegrationIntegration

14


15/25

Slide #15

Risk is the possibility of suffering loss, injury,Risk is the possibility of suffering loss, injury,disadvantage, or destruction.disadvantage, or destruction. ]]


16/25

CS427 5-16

RisksRisks

Technical risksTechnical risks

Project risksProject risks

Business risksBusiness risks

Success does not require winning big, butSuccess does not require winning big, but

avoiding failureavoiding failure


17/25

CS427 5-17

Common risksCommon risks

Projects get killed for same old reasonsProjects get killed for same old reasons

Use database of problems to identify riskUse database of problems to identify risk

Assess risksAssess risks

Avoid risksAvoid risks

Monitor risks you cant avoidMonitor risks you cant avoid

Manage risksManage risks


18/25

CS427 5-18

Managing riskManaging risk

Iterations alleviate riskIterations alleviate risk FeedbackFeedback

Chance to try out new technologyChance to try out new technology

Architecture should address known risksArchitecture should address known risks

Rank use cases by customer priority andRank use cases by customer priority and

riskrisk

Management is responsible for non-Management is responsible for non-

technical risktechnical risk


19/25

Slide #19

Eliminate redundant risks; Combine related risks; Link dependent risksEliminate redundant risks; Combine related risks; Link dependent risks One possible grouping - Organizational, Process, ProductOne possible grouping - Organizational, Process, Product Schedule/budget, new technology/obsolescence, etc.Schedule/budget, new technology/obsolescence, etc.

Establish Measurement scaleEstablish Measurement scale Measure probability, consequence, time frameMeasure probability, consequence, time frame Risk Exposure = Likelihood x ConsequenceRisk Exposure = Likelihood x Consequence

Order of likelihood, consequence, exposure, time frameOrder of likelihood, consequence, exposure, time frame

Define scenarios or conditions that indicate occurrence of a risk is imminentDefine scenarios or conditions that indicate occurrence of a risk is imminent


20/25

Slide #20

Generic Software Project Risk FactorsRisk Factors Low Risk Cues Medium RiskCues High Risk Cues L M H

ProjectTeam

TeamMember

Availability

in place, littleturnoverexpected; fewinterrupts for firefighting

available, someturnoverexpected; somefire fighting

high turnover, notavailable; teamspends most oftime fighting fires

ApplicationExperience

extensiveexperience inteam with projectslike this

some experiencewith similarprojects

little or noexperience withsimilar projects

Experiencewith Process

extensiveexperience withthis process

some experiencewith this processor extensiveexperience withanother

little or noexperience with adefined process

Training of

Team

training plan in

place, trainingongoing

training for some

areas notavailable ortraining plannedfor future

no training plan or

training not readilyavailable


21/25

Slide #21

Prioritize risks by triggers, exposure andtimeframe. Deal with the most critical first.

All non-negligible risks must have mitigationstrategies.

Obtain more information as necessary toeliminate or reduce uncertainty

Document decisions and strategies


22/25

Slide #22

Take action to reduce risk -hold training, add resources,Take action to reduce risk -hold training, add resources,

reduce scope of project, etc.reduce scope of project, etc.

Have resources (money, staff, equipment, etc.) available toHave resources (money, staff, equipment, etc.) available tohandle occurrence of riskhandle occurrence of risk

Get someone else to accept the risk not recommended Get someone else to accept the risk not recommended if done, keep tracking the riskif done, keep tracking the risk

Live with it appropriate only for low consequence risksLive with it appropriate only for low consequence risks


23/25

Slide #23

Risk MitigationCreeping user requirements Requirements elicitation - consult

stakeholders early, plan forrequirements growth (10% per month)

Excessive schedule pressure Planning (7% of system cost), costestimation, communications

Low quality Planning (Quality Assurance Plan),independent QA organization, training,IV&V

Cost Overruns Cost estimation, planning

Inadequate ConfigurationControl Planning (Configuration ManagementPlan), Training, Automated CM tools


24/25

Chapter 2A 24

Iteration and IncrementationIteration and Incrementation

Iteration and incrementation are used in conjunction with one anotherIteration and incrementation are used in conjunction with one another There is no single requirements phase or design phaseThere is no single requirements phase or design phase Instead, there are multiple instances of each phaseInstead, there are multiple instances of each phase

Increment DIncrement CIncrement BIncrement A

HighMediumLowLowTest Workflow

LowHighMediumLowImplementation

Workflow

LowHighHighLowDesign

Workflow

LowLowHighMediumAnalysis

Workflow

NoneLowMediumHighRequirements

Workflow

Work Quantity In Each Increment


25/25

Thank youThank you

25

uml keerthi

Documents