Lecture 3 - Software Process Model
Lecture 3 - Software Process Model
Poor Quality
Process as a "black box"
Informal
Requirements
Process
Product
Quality?
Uncertain /
Incomplete requirement
In the beginning
Problems
The assumption is that requirements can
be fully understood prior to development
Interaction with the customer occurs only at
the beginning (requirements) and end (after
delivery)
Unfortunately the assumption almost never
holds true
Process as a "white box"
Informal
Requirements
Process
Product
feedback
Advantages
Reduce risks by improving visibility
Allow project changes as the project progresses
based on feedback from the customer
Prescriptive Model
Prescriptive process models advocate an
orderly approach to software engineering
Organize framework activities in a certain
order
Process framework activities with set of
software engineering actions.
Each Task identifies the work to be
accomplished to meet the goals.
Prescriptive Model
Software engineer choose process
framework that includes activities like;
Communication
Planning
Modeling
Construction
Deployment
Prescriptive Model
Calling this model as “Prescribe”
because it recommend a set of
process elements, activities, action
task, work product & quality.
Each element is inter-related to one
another (called workflow).
Waterfall Model or Classic Life Cycle
Limitations of the waterfall model
14
Limitations of the Waterfall Model
Some teams sit ideal for other teams
to finish
Therefore, this model is only
appropriate when the requirements
are well understood, and changes will
be fairly limited during the design
process.
Waterfall Model - Problems
Problems:
1. Real projects rarely follow the
sequential model.
2. Difficult for the customer to state all the
requirement explicitly.
3. Assumes patience from customer -
working version of program will not
available until product is complete.
V-Model
V-Model
V-model depicts the relationship of quality
assurance actions to the Frame Work Activities.
In reality, there is no fundamental difference
between the classic life cycle and the V-model.
The V-model provides a way of visualizing how
verification and validation actions are applied to
earlier engineering work.
Incremental Process Model