A software development project has been identified as having six stages, these being (1) design the logical plan for the software operation, (ii) select a programming language, (ill) write source code, (iv) test the source code, (v) integrate software with existing applications, and (vi) train users. The time estimates for each of these activities are contained in table 14.3, as well as actual time taken (where available, since the project is only partly complete).

Required

(a) Using the data in the table, construct a Gantt chart.

(b) Comment on the ability of the project to meet its schedule: if all remaining activities are completed according to budgeted times, will the project be completed on time?

(c) What activities are over schedule?

(d) Recognising that you are under pressure to meet the budgeted deadline for this software implementation, since it forms a part of an organisation-wide strategic initiative that will propel the company into the future, your boss suggests that you may want to revise your plans for testing and training, to ensure that the original 60-day schedule is met. One suggestion is to cut back on testing at the unit and system level and just focus on testing at the stub level. What is your response to this suggestion? Is it a good idea? Why? In your response be sure to distinguish between the different levels of testing and the aims of each level of testing.

Transcribed Image Text:

TABLE 14.3 Project activities, budgeted time and actual time Activity Design the logical plan for the software Budgeted time (days) Actual time (days) 00 8 7 operation Select a programming language 2 2 Write source code 15 25 Test the source code 24 Not available Integrate software with existing applications. 4 Not available Train users 7 Not available