Information Technology Reference
In-Depth Information
development process, both technical and managerial. A SPMP is accompanied by
a
software
requirement
analysis
document
(SRAD),
which,
as
its
name
suggests, helps to further describe the project being undertaken.
4.7 Chapter Summary and Conclusions
In this chapter we have discussed the critical concepts to planning and managing a
software engineering project. A project must begin with communication. The
initial communication with the client is used to identify the software solution
envisioned by the client, and the functionality that they require from it. The
information gathered from the client is then utilized to create a plan for the project.
Project planning seeks to identify the activities, milestones, and deliverables that
are to be achieved throughout the project. Planning begins with the determination
of a software systems purpose and scope. Next, the project manager identifies the
activities to be undertaken during the project, the milestones that will define them,
and the deliverables that they will produce. Finally, the project plan must include
estimations of resources to be consumed, including manpower, time, and money.
From this estimation, a schedule is created for the development process. The
project manager is responsible for managing this schedule for the entirety of the
project. One tool a project manager might use in this endeavor is called a Work
Breakdown Structure, WBS, which lays out a project according to the activities
that make it up. In addition, project managers can use Gantt Charts to map out the
project's schedule, and to monitor progress.
In addition to planning the project, a project manager is responsible for com-
municating with, and supervising all of the individuals involved in the project.
This includes everyone from the client to the individual engineers. When a project
begins, the project manager must select staff based on ability, and assign that staff
to activities at which they can perform effectively.
Finally, a project manager is responsible for monitoring a software engineering
project to ensure that it follows the intended course and achieves the specified
goal. If deviation from the plan or schedule is encountered, the project manager
must take appropriate action to see that it is corrected. This can include the
reassignment of engineers, the hiring of new engineers, or the scrubbing of certain
requirements.
4.8 Exercises
1. Last chapter, we asked you to explain the difference between a class and an
object using examples. Now, present the same difference, this time using
models.
