Information Technology Reference
In-Depth Information
The scope of a software project is used to describe the function, performance,
constraints, interfaces, and reliability of, as well as the data to be processed by, the
software system. Functions are initially described in the statement of a system's
scope, are later evaluated and, if needed, refined in order to provide the proper level
of detail required for accurate and successful estimation phases. Because both cost
and schedule estimates are function oriented, a degree of decomposition is often
useful in providing a meaningful picture of the development process. A scope's
statement of performance encompasses both processing and response time
requirements for the software system. The statement of a system's constraints is used
to identify the limits within which the software system will exist, as imposed by
factors such as external hardware, available memory, or other preexisting systems.
4.1.2 Identifying the Deliverables of the Project
Following the identification of a project's purpose and scope, the software engi-
neering team must now create a set of goals to be met throughout the process. This
is accomplished through the establishment of a series of milestones, or recog-
nizable endpoints for specific development activities. This practice allows a pro-
ject to be broken down into distinct, logical sections. Closely related to this
concept is that of producing deliverables. Deliverables make up the tangible
results of the development process such as code, documentation, cost estimates, or
reports from engineers. As a milestone is reached, the deliverables produced by the
included development activities are completed. The relationship between a mile-
stone and the related deliverables allows both, for the sequential production of the
various portions of the software project, as well as the assessment of the devel-
opment team's progress.
4.1.3 Cost Estimation
Finally, the third activity involved in project planning is cost estimation. Cost
estimation is the practice of calculating the amount of resources required to suc-
cessfully complete the software project. These resources come in two basic cat-
egories: money and time. Certainly, there are other types of resources, such as
personnel or work space, however, resources of this type can usually be reduced
back to money; in this case salary and rent. Both estimate types are of critical
importance to the relationship between the client and developer. They are also at
the core of establishing the cost the client will pay.
Schach defines two types of money cost estimates, as characterized by the party
for which they are intended. The internal cost is the cost for the development
team, while the external cost is the price tag that will be given to the client
(Schach
2008
). The internal cost is the composition of the various costs the
