pmsd presentation

8/2/2019 Pmsd Presentation

1/14

ELANGO.G

RAMACHANDRANSUNIL KUMARTHIYAGARAJAN

Software Development Life

Cycle (SDLC)


2/14

SDLC Model

A framework that describes the activities

performed at each stage of a software developmentproject.


3/14

Win Win Spiral Model

The Win-Win spiral approach is an extension of thespiral approach. The phase in this approach is same

as the phase in the spiral approach. The onlydifference is that at the time of the identifying therequirements, the development team and thecustomer hold discussion and negotiate on the

requirements that need to be included in the currentiteration of the software.


4/14

The approach is called Win-Win because it is awinning situation for the development team and alsofor the customer. The customer wins by getting theproduct that fulfils most of the requirements whilethe development team wins by delivering software

which is developed with all the requirementsestablished after negotiations with the customer. The

Win-Win approach is generally used when you havetime-bound releases.


5/14

WinWin Spiral Model


6/14

Cont

Identifying the system's stakeholders and their winconditions and

reconciling win conditions through negotiation toarrive at a mutually satisfactory set of objectives,

constraints, and alternatives for the next level. Evaluate Product and Process Alternatives. Resolve

Risks

Define next level of product and process - includingpartitions

Validate Product and Process Definitions

Review, commitment


7/14

Spiral Quadrant

Determine objectives, alternatives and constraints

Objectives: functionality, performance,hardware/software interface, critical success factors, etc.

Alternatives: build, reuse, buy, sub-contract, etc.

Constraints: cost, schedule, interface, etc.


8/14

Spiral QuadrantEvaluate alternatives, identify and resolve risks

Study alternatives relative to objectives and constraints

Identify risks (lack of experience, new technology, tightschedules, poor process, etc.

Resolve risks (evaluate if money could be lost by continuingsystem development


9/14

Spiral QuadrantDevelop next-level product

Typical activites:

Create a design

Review design

Develop code

Inspect code

Test product


10/14

Spiral QuadrantPlan next phase

Typical activities

Develop project plan

Develop configuration management plan

Develop a test plan

Develop an installation plan


11/14

Spiral Model Strengths

Provides early indication of insurmountable risks,without much cost

Users see the system early because of rapid

prototyping tools Critical high-risk functions are developed first

The design does not have to be perfect

Users can be closely tied to all lifecycle steps

Early and frequent feedback from users

Cumulative costs assessed frequently


12/14

Spiral Model Weaknesses

Time spent for evaluating risks too large for small or low-risk projects

Time spent planning, resetting objectives, doing riskanalysis and prototyping may be excessive

The model is complex

Risk assessment expertise is required

Spiral may continue indefinitely

Developers must be reassigned during non-developmentphase activities

May be hard to define objective, verifiable milestones thatindicate readiness to proceed through the next iteration


13/14

When to use Spiral Model

When creation of a prototype is appropriate When costs and risk evaluation is important For medium to high-risk projects Long-term project commitment unwise because of

potential changes to economic priorities Users are unsure of their needs Requirements are complex New product line Significant changes are expected (research and

exploration)


14/14

THANK YOU

ELANGO.G

RAMACHANDRANTHIYAGARAJAN

SUNIL KUMAR

pmsd presentation

Documents