Software Project Management Brochure Template Page 16
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
2916
Handbook on Software Engineering & Knowledge Engineering
•
the degree of structure in the project's outputs - it is negatively correlated
with the risk in the project;
In the context of the Unified Process of software development, it is adopted
that one can never fully eliminate risks; at best, one can manage them [12], [24].
For that reason, the Unified Process stresses the need to drive software
development as an architecture-centric activity. Architecture-centric approach
forces the risk factors to emerge early in the development process and make the
process simultaneously risk-driven - when the risk factors are identified early,
managers can take steps to mitigate them. Experienced software project
managers recommend to maintain a running list of project's top ten risk factors
and use that list to drive each release [12].
Software Metrics
Measurement is a key factor for managing and improving software development.
The purpose of the measurement process in software projects is to define and
operate a context-specific set of metrics, and to describe the required guidelines
and procedures for data collection and analysis [32]. Software measurement
generates quantitative descriptions of key processes and products, enabling us to
understand behavior and result [37]. Such descriptions can indicate the effort
needed to complete the project, the product’s quality, estimated schedules and
time-to-market, rework effort, estimated project costs, and distribution of
resources and costs by project phases. Software measurement makes possible to
compare the project a development team is currently working on, to similar
projects in terms of budget, costs, productivity, quality, staffing, development
processes, and technology used.
In order to operate a metrics program during a software development project,
the project manager must enforce continuous measurement of relevant factors.
These factors depend on the overall management goals of the measurement
process. In that sense, one can differentiate between the following kinds of
software metrics [2], [11], [15], [19], [28], [31], [32], [47]:
•
metrics for project size and team productivity – typical and most widely
used representatives of this kind of metrics are source lines of code
(SLOC) and function points; the SLOC metric can be converted relatively
accurately and easily into the number of programer-months needed to
complete the project; function points are dimensionless numbers that
indicate the application’s functionality from the user’s perspective, and
can also be easily converted into the effort needed to complete the project
or one of its parts;
•
metrics for schedules – these include the number of tasks completed on
time, the number of tasks not completed on time, the number of tasks with
changed schedules, and the number of postponed tasks;
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business