Soft Proj Management and Maintenance

8/14/2019 Soft Proj Management and Maintenance

1/49

Soft Proj Management and MaintenanceSoft Proj Management and Maintenance

Software Project ManagementSoftware Project Management

RUPRUP

DSDMDSDM

COCOMOCOCOMO

Software Project ManagementSoftware Project Management

RUPRUP

DSDMDSDM

COCOMOCOCOMO


2/49

Software Maintenance

ProcessProcess

ToolsTools

PeoplePeople


3/49

Course

Presentation OnPresentation OnRUP

DSDM

COCOMO Models

Software Maintenance Case Study

Mini Project and PresentationMini Project and PresentationUsing RUP

Using DSDM


4/49

Evaluation

Project Documentation 30%

Project Plan 10%

Project conduct 10%

Presentation 20%

Assignements

Summary and Critic 30%


5/49

Before the UML

1960s - 70s1960s - 70s

COBOL, FORTRAN, C

Structured analysis and design techniques

1980s - early 1990s1980s - early 1990s

Smalltalk, Ada, C++, Visual BasicEarly generation OO methods

Mid/late 1990sMid/late 1990s

Java

UML

Unified Process


6/49

Models and Diagrams

Use CaseDiagrams

Use CaseDiagrams

Use CaseDiagrams

ScenarioDiagrams

ScenarioDiagrams

CollaborationDiagrams

StateDiagrams

StateDiagrams

ComponentDiagrams

ComponentDiagrams

ComponentDiagrams

DeploymentDiagrams

StateDiagrams

StateDiagrams

ObjectDiagrams

ScenarioDiagrams

ScenarioDiagrams

StatechartDiagrams

Use CaseDiagrams

Use CaseDiagrams

SequenceDiagrams

StateDiagrams

StateDiagrams

ClassDiagrams

ActivityDiagrams

model is a completescription of a system

m a particularrspective

Models


7/49

Team-BasedDevelopment

But, the UML Is NotEnough

ModelingLanguage

UnifiedProcess


8/49

Creating the Unified Process

Functional testingPerformance testingRequirements mgmtConf. and change mgBusiness engineeringData engineeringUI design

Rational Unified Process 5.01998

Rational Objectory Process 4.1

1996-1997

Objectory Process 1.0-3.81987-1995

The Ericsson Approach

The Rational Approach UML


9/49

New or changed

requirements

New or changed

system

Software Engineering

Process

What Is a Process?

DefinesDefines Who is doing What, When todo it, and How to reach a certaingoal.


10/49

Overview of the Unified Process

The Unified Process isThe Unified Process is Iterative and incremental

Use case driven

Architecture-centric


11/49

Lifecycle Phases

time

Inception Elaboration Construction Transition

Inception Define the scope of theDefine the scope of theproject andproject and develop business casedevelop business case

Elaboration Plan project, specifyPlan project, specifyfeatures, andfeatures, and baseline thebaseline thearchitecturearchitecture Construction Build the productBuild the product

Transition Transition the product toTransition the product toits usersits users


12/49

Major Milestones

time

Vision BaselineArchitecture

InitialCapability

ProductRelease



13/49

Phases and Iterations

An iteration is a sequence of activities with anestablished plan and evaluation criteria, resultingin an executable release

ArchIteration

... DevIteration

DevIteration

... TransIteration

...

Release Release Release Release Release Release Release Release

PrelimIteration

...



14/49

Inception Phase

InceptionInception

Vision Document

Initial Use Case Model

Business cases -------Success criteria,

Initial Proj Plan Initial risk Assesment

Prototype

Milestone Q

Life Cycle Objectives


15/49

Elaboration phase

Use cases specified in detail (80%Use cases specified in detail (80%Complete)Complete)

Architecture DescriptionArchitecture Description Executable Arch prototypeExecutable Arch prototype

Revised risk ListRevised risk List

Update development ProcessUpdate development Process

Milestone QMilestone Q

Life Cycle Architecture?Life Cycle Architecture?


16/49

Construction

Product is builtProduct is built

Design goes on to become a full fledgedDesign goes on to become a full fledgedsystemsystem

User ManualUser Manual

Description of releaseDescription of release

All Use cases are realisedAll Use cases are realised

Milestone?Milestone?

Initial operational CapabilityInitial operational Capability


17/49

Transition

Products move to beta releaseProducts move to beta release Defects and defeciencies are reportedDefects and defeciencies are reported

and rectifiedand rectified

training personneltraining personnel

Delta release identifiedDelta release identified

Milestone QMilestone Q

Product ReleaseProduct Release


18/49

Iterations and Workflow

Pre l iminary

I terat ion(s)

iter.

# 1

iter.

# 2

iter.

# n

iter.

#n+1

ite r.

# n + 2

iter.

# m

iter.

# m + 1


I t e r a t i o n s

Phases

Core Workflows

An iteration in the

elaboration phase

Requirements

Design

Implementation

Test

Analysis


19/49

Workflows and Models

Requirements

Design

Implementation

Test

Analysis

Use CaseModel

DesignModel

Depl.Model

Impl.

Model

AnalysisModel

TestModel

UML diagrams provide

views into each model

Each workflow is

associated with one ormore models.


20/49

Use Case ModelUse CaseDiagrams


ComponentDiagrams

DeploymentDiagrams

ObjectDiagrams

StatechartDiagrams

SequenceDiagrams

ClassDiagrams

ActivityDiagrams

Use CaseModel

DesignModel

Depl.Model

Impl.Model

AnalysisModel

TestModel


21/49

Analysis & Design ModelUse CaseDiagrams


ComponentDiagrams

DeploymentDiagrams

ObjectDiagrams

StatechartDiagrams

SequenceDiagrams

ClassDiagrams

ActivityDiagrams

Use CaseModel

DesignModel

Depl.Model

Impl.Model

AnalysisModel

TestModel

Incl. subsystems

and packages


22/49


23/49

Test ModelUse CaseDiagrams


ComponentDiagrams

DeploymentDiagrams

ObjectDiagrams

StatechartDiagrams

SequenceDiagrams

ClassDiagrams

ActivityDiagrams

Use CaseModel

DesignModel

Depl.Model

Impl.Model

AnalysisModel

TestModel

Test model refers to all

other models and uses

corresponding

diagrams


24/49

Use Case Driven

Req.ts Impl. Test

Use Cases bind these workflows together

Analysis Design


25/49

Architecture-Centric

Models are vehicles for visualizing,Models are vehicles for visualizing,specifying, constructing, andspecifying, constructing, anddocumenting architecturedocumenting architecture

The Unified Process prescribes theThe Unified Process prescribes the

successive refinement of ansuccessive refinement of anexecutable architectureexecutable architecture

time

Architecture


hi d d l


26/49

Architecture and Models

Architecture embodies a collection of views of the models

Views

Models

Use CaseModel

DesignModel

Depl.Model

Impl.Model

TestModel

AnalysisModel


27/49

Function versus Form

Use cases Architecture

Use case specify function; architecture specifies form

Use cases and architecture must be balanced


28/49

Engineered

Describe aUse Case

Use case

package

Use case

responsible for

Analyst

Artifact

A piece ofinformation that isproduced, modified,or used by a process

Worker

A role playedby anindividual or ateam Activity

A unit ofwork


29/49

The Unified Process is a ProcessFramework

There is NO Universal Process!

The Unified Process is designed for flexibility and extensibility

allows a variety of lifecycle strategies

selects what artifacts to produce defines activities and workers

models concepts


30/49

Two Parts of a Unified Whole

The Unified

Modeling

Language

The Unified

Process

Convergencein the future

Convergencethroughprocessframeworks

Convergencein the future

Convergencethroughprocessframeworks

OMG standard OMG standard

DSDM


31/49

DSDM

DSDM O i


32/49

DSDM Overview

DSDM Ph


33/49

DSDM Phases

Feasibility study

Business study

Functional model iteration

Design and build iteration Implementation

F iblit St d


34/49

Feasiblity Study

Is RAD a suitable Option ?Is RAD a suitable Option ? Are Technical and ManagerialAre Technical and Managerial

condititons met ?condititons met ?


35/49

F ti l d l it ti


36/49

Functional model iteration

Freezing the requirements till workingFreezing the requirements till workingmodel is readymodel is ready

Functional robust prototypes areFunctional robust prototypes areDevelopedDeveloped

Iteration done if requirements haveIteration done if requirements havebeen changedbeen changed

D i M d l It ti


37/49

Design Model Iteration

Ensure prototypes work underEnsure prototypes work underoperational Environmentoperational Environment

Trialling in operational environmentTrialling in operational environment

I l t ti


38/49

Implementation

User Approval and User guidelinesUser Approval and User guidelines

People are trainedPeople are trained

Review ImpactReview Impact

?


39/49

?

How do we compare RUP and DSDMHow do we compare RUP and DSDM

Mappings both ways

Opinion

Which is suitable for which project

COCOMO


40/49

COCOMO

Effort = C1 EAF (Size)Effort = C1 EAF (Size) P1P1

TimeTime == C2 (Effort)C2 (Effort)P2P2

C1, C2=constant scaling co-efficientC1, C2=constant scaling co-efficient EAF= product of domain,personnel,EAF= product of domain,personnel,

environment and tools usedenvironment and tools used

Size = in KLOCSize = in KLOC

z


41/49

zMetrics

EAFEAF Parameter rangeParameter range

Required reliablity 0.75-1.40Required reliablity 0.75-1.40

Product ComplexietyProduct Complexiety 0.70-1.650.70-1.65

Execution Time ConstExecution Time Const 1.00-1.661.00-1.66 Analyst capabilityAnalyst capability 1.46-0.711.46-0.71

Use of software toolsUse of software tools 1.24-0.831.24-0.83

----15 such Parameters related to the----15 such Parameters related to theprojectproject

COCOMO I


42/49

COCOMO-I

Organic ModeOrganic Mode

In House, Less complex,Flexible features,In House, Less complex,Flexible features,Qulities .............Qulities .............

Embedded ModeEmbedded Mode

Complexity, Realiability, Strict constraintsComplexity, Realiability, Strict constraints Change requires many approval .....Change requires many approval .....

Semi detached ModeSemi detached Mode

Organic Mode


43/49

Organic Mode

Effort = 3.2 EAF (size)Effort = 3.2 EAF (size) 1.051.05

Time In Months= 2.5(Effort)Time In Months= 2.5(Effort)0.380.38

Semidetached Mode


44/49

Semidetached Mode

Effort = 3.0 EAF (size) 1.12

Time In Months= 2.5 (Effort) 0.35

Embedded Mode


45/49

Embedded Mode

Effort = 2.8 EAF (Size)Effort = 2.8 EAF (Size) 1.121.12

Time (in Months)=2.5Time (in Months)=2.5(Effort)(Effort)0.320.32

COCOMO II


46/49

COCOMO-II

Effort=2.45 EEffort=2.45 EArchArch

(Size)(Size)PP

Effort = 2.45 Eapp (Size)Effort = 2.45 Eapp (Size)PP

E


47/49

EArch

IdentifiersIdentifiers

Product CmplxtyProduct Cmplxty

Required ReuseRequired Reuse

Personnel ExprncePersonnel Exprnce Facilities scheduleFacilities schedule

E


48/49

E App

IdentifiersIdentifiers

Required reliabilityRequired reliability

Database sizeDatabase size

Time ConstraintTime Constraint Use of Software toolsUse of Software tools

Reqd Development scheduleReqd Development schedule

Project


49/49

Project

Two groupsTwo groups

Documentation of the phasesDocumentation of the phases

User ManualUser Manual

ProposedProposed

JCE- Symm Key Filesecure (RUP)JCE- Symm Key Filesecure (RUP)

KK

Documents

Soft Proj Management and Maintenance