The document outlines different models for the software development process, including the waterfall model and iterative model. It then describes various stages of the process in more detail, such as creating a project proposal, conducting a feasibility study, performing system investigation to create an operational requirements document, development, implementation and testing, and maintenance. The waterfall model allocates most resources to the operational and maintenance stage.

1. Advanced Higher
Computing
SOFTWARE DEVELOPMENT PROCESS

2. Waterfall Stages Model
1. Analysis
2. Design
3. Implementation
4. Testing
5. Documentation
6. Evaluation
7. Maintenance

3. Iterative Stages Model
Analysis of
Operational
requirements
System
specification
Software
Design
Implementation
and testing
Evaluation and
maintenance

4. Project Proposal
 Sometimes known as the Problem Definition
 Limitations of existing system
 Company Profile
 Project Requirements
 Migration Routes
 Budget Constraints
 Used as a basis for bids/offers for developers.

5. Feasibility Study
 Technical
 Economic
 Legal
 Schedule
 Advantages for both clients and developers.

6. System Investigation
 Undertaken by a System Analyst
 Observation
 Interview
 Document and data flow inspection
 Establish scope, boundaries, inputs and outputs
 Produces an Operational Requirements Document
(ORD).

7. Operational Requirements Document
(ORD)
 Legally binding contract
 Functional Requirements
 Data Requirements
 Physical Specification
 Scope and Boundaries
 Inputs and Outputs
 System Prospectus

8. ORD: Functional Requirements
 Used at the beginning of the design stage to identify the features to be
present in the proposal software.
 Used to validate other stages or analysed at the end of
design/implementation/etc to ensure functional requirements are being
met.
 Used for dispute resolution between client and developer.

9. ORD: Scope and Boundaries
 Scope: What the proposal software will be able to do.
 Boundaries: The limitations of the software (what it
will not be able to do).

10. ORD: Data Requirements
 The data structures which will be used.
 The amount of data which the software will generate
and store.

11. ORD: System Prospectus
 Schedule – preliminary timings and task
dependencies.
 Proposed Documentation.
 Training required to use the software.

12. Development Phase
 System Design:
 Flow chart
 Data Flow Diagram
 Jackson Structured Programming
 Pseudocode
 Checked to make sure it matches specification and customer
requirements.

13. Implementation and Testing
 Coding and Testing
 Design and Test HCI
 Set up Hardware
 Convert legacy files
 Complete documentation and Manuals
 Train Staff

14. Testing
 Dry runs
 Structured Walkthroughs
 White box (Structural Testing)
 Black box (Functional Testing)
 Module >Sub System > Complete System

15. Adopting a New System
 Pilot conversion
 Phased conversion
 Direct conversion (Sudden Death)
 Parallel conversion

16. Maintenance
 Corrective
 Adaptive
 Perfective
 Preventative

17. Evaluation (Questions)
 Does it meet the specification?
 It is what the client want?
 Is it fit for purpose?

18. Waterfall Model
Analysis
3%
Specification
3%
Coding
7%
Design 5%
Operational and
Maintenance 67%
Testing 15%