Understanding Software Process Models & Approaches in Object-Oriented Project Management, Slides of Banking and Finance

Download Understanding Software Process Models & Approaches in Object-Oriented Project Management and more Slides Banking and Finance in PDF only on Docsity!

Object-Oriented Software Engineering

Practical Software Development using UML and Java

Chapter 11: Managing the Software Process

11.1 What is Project Management?

Project management encompasses all the activities needed to plan and execute a project:

• Deciding what needs to be done
• Estimating costs
• Ensuring there are suitable people to undertake the project
• Defining responsibilities
• Scheduling
• Making arrangements for the work
• continued ...

11.2 Software Process Models

Software process models are general approaches for organizing a project into activities.

• Help the project manager and his or her team to decide: —What work should be done; —In what sequence to perform the work.
• The models should be seen as aids to thinking , not rigid prescriptions of the way to do things.
• Each project ends up with its own unique plan.

The opportunistic approach

Think of Idea for Improvement

Modify Until Satisfied

First Prototype

The waterfall model

The waterfall model

The classic way of looking at S.E. that accounts for the importance of requirements, design and quality assurance.

• The model suggests that software engineers should work in a series of stages.
• Before completing each stage, they should perform quality assurance (verification and validation).
• The waterfall model also recognizes, to a limited extent, that you sometimes have to step back to earlier stages.

The phased-release model

The phased-release model

It introduces the notion of incremental development.

• After requirements gathering and planning, the project should be broken into separate subprojects, or phases.
• Each phase can be released to customers when ready.
• Parts of the system will be available earlier than when using a strict waterfall approach.
• However, it continues to suggest that all requirements be finalized at the start of development.

The spiral model

It explicitly embraces prototyping and an iterative approach to software development.

• Start by developing a small prototype.
• Followed by a mini-waterfall process, primarily to gather requirements.
• Then, the first prototype is reviewed.
• In subsequent loops, the project team performs further requirements, design, implementation and review.
• The first thing to do before embarking on each new loop is risk analysis.
• Maintenance is simply a type of on-going development.

The evolutionary model

The concurrent engineering model

The concurrent engineering model

It explicitly accounts for the divide and conquer principle.

• Each team works on its own component, typically following a spiral or evolutionary approach.
• There has to be some initial planning, and periodic integration.