Engineering Project Progress Software

1) Feasibility :

Examine the feasibility of the project and how the job may be done. Some approximations on time/resources can be calculated. The accuracy of the costs will depend on how clearly the project is defined. Discussions with customers and sales.

2) Cardboard Demo:

Mock up of job. E.g. control page layouts, graphic demonstrations showing some of the operation.
About 1% of the total time.

3) Concept:

Break the job into separate tasks. Ideally the interface between tasks should be minimize to enable each task to be written, debugged, run and tested independently.

4) Working Demo (Alpha) :

A preliminary design is done and an engineering model is built to demonstrate the viability of the design. Suitable for an Engineer to demonstrate. Time scales and cost can be modified and a firm time scale can be given. A set of operation notes should be produced.
About 5 to 10 % of the total time.

5) Main core :

The bulk core of the software is designed, coded, tested, and debugged.
If the time scale is long (say > 4 months), then intermediate releases could be made. Any method which gives early feedback and correction to reality is more likely to give control over the final result rather than the 'big-bang' method.
Testing carried out within engineering. About 65% of the total time.

6) Working Demo (Beta) :

This should show all the features working and enable customer/sales to provide constructive feedback on any outstanding points of the design. Preliminary handbook produced.
Testing carried out by an independent source.
About 5% of the total time.

7) Final:

Results from above should be integrated into the design and final software produced. The final handbook issued, together with test specifications.
About 10% of the total time.

8) Release:

Software and complete documentation should be logged and released. Any minor bugs could be cured by explanation of the problem and avoidance or simple patching of the software.
Serious problem will have to go back to stage 6 with new time estimates for completion.
Software Q.A. approval before final issue to customer.
About 5% of the total time.

Updated: Saturday, December 31, 2016 15:50