Page 11 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 1: Introduction to Software Project Management

 The technology changes very rapidly: Most large software projects utilize new technology; Notes
for many projects.

 The product is intangible: It’s very difficult to declare a bridge is 90% complete if there is
not 90% of the bridge there. It is easy to declare that a software project is 90% complete,
even if there are no visible outcomes.

 Large software projects are generally modified: Most large software systems are one-off,
with experience gained in one project being of little help in another.
 We don’t have much knowledge: Software engineering is a new discipline, and so we
basically don’t have much understanding of how to engineer large scale software projects.

Examples:
 Freshmeat
 Apache Software Foundation
 CPAN
 CTAN
 CRAN

Construction Projects

The project produces an artifact. The worth generated by the project is implanted in the artifact.
The artifact may be a compound system with human and mechanical components.

Examples:
 Warship
 Jubilee line extension
 Millennium dome
 Customer call centre
 Method guidebook
 IT system

Research Projects

The project generates information. The information may be formally symbolized as models,
patterns or patents. Or the information may be embedded in a working process or artifact.

Examples:
 Business modeling
 Developing a model of the UK economy
 Developing a new species of wheat
 Developing novel approaches to project management.
 Military intelligence/code breaking.
 The analysis, testing, QA or evaluation portions of a larger project.

LOVELY PROFESSIONAL UNIVERSITY 5