Chapter 2 – Software Process Models

1. Software Process are the activities to develop software. The activities are –
a. Software Specification
b. Software Development
c. Software Validation
d. Software Evolution

2. Software Process Model (SPM) are the guidelines to develop are particular software. Includes
the process, products and the role of peoples involved.

3. Waterfall/Linear Model
a. Activities involved –
i. Information and modeling
ii. Software requirement analysis
iii. Design
iv. Code Generation
v. Testing
vi. Support

4. Advantages and Disadvantages

Advantages Disadvantages
Simple method, easy to use Does not allow much revision
Phases are clear Not suitable for complex projects
Suitable for small project High risk
Easy to manage Does not have a feedback path

5. Only use waterfall when –

a. Requirements are clear
b. User Involvement are low
c. Time to develop is long
d. Cost/Budget is high
 e. Many HR
f. Expertise of HR is low
g. Change is not allowed
h. Not interactive among developers and customer

6. Prototype model
a. A working prototype of the system is built before the actual software
b. A working model with limited function
c. Used for the customers to evaluate the software before implementation
d. Build a quick design, a prototype, customer feedback and improve the system, cycle the
process until customers approved, actual system developed.

7. Benefits and Drawback

Benefits
Misunderstanding between developers and
users will be identified
Missing user services detected
Developers might find inconsistent or
incomplete requirements as prototype is
developed
Confusion of user services can be identified
Able to demonstrate quickly
Serves as basis for writing the software
specification
Drawback
Planning, costing and estimating the project
needs a lot of experience
Procedures for changes may be unsuitable
for controlling the rapid change in
prototyping
Inappropriate requirements might be
happened as the develop

8. Types of Prototyping Model

a. Rapid Throwaway – Quickly developed to show how the requirement will look like for
the customer. Customer feedbacks helps to change the requirement and the prototype
 is created again, cycle until the requirement is reached. A developed prototyped will be
discarded.
b. Evolutionary – Prototype developed will incrementally refined by the customer
feedback until it is accepted.
c. Incremental – The final product is separated into small prototypes and develop
individually.
d. Extreme – Used for web design. Basic prototype with existing page in HTML format.
Simulate data process using a prototype services layer. Combined into a final prototype

9. Rapid Application Development

a. A process based on prototyping without any planning. Less attention is paid to the
planning, priority on the development task. Target developing software in a short
amount of time. The flow is below -
i. Business modeling – Based of the information given, product is designed
ii. Data modeling – Information collected from business modeling is refined into a
set of data object.
iii. Process Modeling – Data object declared above transform to achieve
information flow
iv. Application Generation – Tools are used to construct the software
v. Testing and Turnover – Prototypes are individually tested.