1.5 System Analysis

4) Changeover

3) Design

5) Testing

6) Maintenance

8) Documentation

7) Backup and Recovery

1) Feasibility Study

2) Investigation and Analysis

Will the project be finished on time?

Will there be a profit?

What improvements need to be made?

How does the old system/similar systems work?

Data flow diagrams

Data dictionaries

Pseudocode

Prototype

Variable lists

Direct - Old system turned off, new one on.

Phased - System switched over one department at a time.

Pilot - Tested in one department, then given to the rest

Parallel - Both systems run at the same time

Alpha - Testing done by the developers, internal

Closed beta - Software is given to a small, select group of users

Open beta - Software is available for download for anyone who wants it

Acceptance - Software is given to the client, asking "Is this what you wanted?"

Adaptive - Changing the software, based on new specifications/user demand

Corrective - Bug fixing

Perfective - Adding new features to the software

Is the old system backed up in case the new system breaks?

Archiving old data to off-system devices

Is the new system regularly backed up?

Is there a manual, so that people know how to use the software?

Documentation, so that other people can repair the system if needed, in the future

Instructions for troubleshooting