SOFTWARE PROCESS MODELS
The Software Process
Development of Software follows a set of procedures
The series of activities to be followed is called software process or Software
development cycle
Software process to be followed is determined by nature of the project e.g the nature
of requirements, risk associated with the project, size of the project, the timeframe by
which the project is needed.
Phases of the Software Process Model
1. Requirements Analysis: both client and the service provider should agree on
specifications of the software system. These requirements what the software
product is expected to do and the constraints are documented in a document called
Software Requirements Specification (SRS).
2. Software Development : The software has to be designed and programmed
3. Software validation : Checking of the produced software against the
specification.
4. Software evolution: Software should be modifiable to meet those changing
customer and market requirements.
Software Process Models
A process model is a representation of a software process. The basic models are
the Waterfall Model, Rapid Application Development (RAD), Prototyping and the
Spiral Model
1. Waterfall Model.
Known as the classic life cycle or sequential model and was the first software process
model to be introduced.
When using this model, the requirements should be very clear at the start of the
project and the project should be small
A review is done at the end of phase so as to determine if the project is on the right
track and whether or not to continue or discard the project
The waterfall model takes the fundamental process activities of the SDLc and
represents them as separate process phases such as requirements specification,
software design, implementation and unit testing, integration and system testing as
well as operation and maintenance
Image below showing Waterfall Model
i. Requirements analysis : The client describes what they want the software
product to do.
ii. System analysis and software design: in system design the major system
components and their relationships are identified. In the design process, the
requirements are categorized into either hardware or software components.
iii. Implementation and unit testing: after system design the coding process
begins. Components are produced and tested to ensure that each system
component meets the desired specification.
iv. Integration and system testing: various system components are put together
and then tested as a complete to make sure that the software requirements
have ben met. Product delivered to client after system testing
v. Operation and Maintenance: the system is ready to be delivered to the
client and deployed
Advantages of the waterfall model
Easy to understand and use
Due to the fact that each
There are clear milestones
There is extensive documentation hence referenced documents are available
throughout the project life
Disadvantage
It is not suitable for complex, big and ongoing projects
No working software is produced until late during their life cycle.
This model is prone to high amounts of risk and uncertainty.
Time and resources are wasted
When to use waterfall model
1. The requirements are well- known
2. Project definition is stable
3. Technology to be used is well understood
4. There are enough resources for the project to be executed
5. The project is short