Scribd
Upload
6 views

Lecture 3 - Software Development Methodologies - Plan Driven Methods - Part 2

Uploaded by

nourmagde000
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views

Lecture 3 - Software Development Methodologies - Plan Driven Methods - Part 2

Uploaded by

nourmagde000
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Software Development Methodologies

Plan Driven Methodologies

Dr. Sayed AbdelGaber


Associate professor
Faculty of Computers and Information
Helwan University

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Spiral Model

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Spiral Model

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Spiral Model Sectors


 Objective setting
Specific objectives for the phase are identified.

 Risk assessment and reduction


Risks are assessed and activities put in place to reduce the key
risks.

 Development and validation


A development model for the system is chosen which can be any of
the generic models.

 Planning
The project is reviewed and the next phase of the spiral is planned.

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Spiral Model Disadvantages

 If the implementation of risk analysis will greatly


affect the profits of the project, the spiral model
should not be used.

 Software developers have to actively look for


possible risks, and analyze it accurately for the
spiral model to work.

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Software Prototyping
 A prototype is an initial version of a system used to
demonstrate concepts and try out design options.

 A prototype can be used in:


• The requirements engineering process to help with
requirements elicitation and validation;

• In design processes to explore options and develop a UI


design;

• In the testing process to run back-to-back tests.

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Benefits of prototyping
 Improved system usability.

 A closer match to users’ real needs.

 Improved design quality.

 Improved maintainability.

 Reduced development effort.

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

How Prototyping Works

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

The Process of Prototype Development

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Throw-away Prototypes

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Reuse-oriented Software Engineering

r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Criteria for Selecting the Appropriate Methodology


 Clear user requirements

 Familiar technology

 Complexity

 Time schedule

 Schedule visibility
r. Sayed AbdelGaber
Software Development Methodologies Lecture 3: Plan Driven Methodologies – part 2

Questions
r. Sayed AbdelGaber

You might also like