Page 21 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 1: Introduction to Software Project Management

Application Area Notes

SSADM was initially developed to standardize the many and varied IT projects being developed
across government departments. Nowadays, SSADM Version 4 can be used in all kinds of
analysis and design stages of system development. SSADM can be used for practically any size
of project: small (1–2 persons, less than one man year), medium (4–10 persons, 1–20 man years)
and large projects. In addition SSADM can be used to develop new projects, but it can also be
used to maintain existing systems.

Advantages

 As stated before SSADM is an open standard, which means that it is freely available for use
in industry and many companies offer support, training and CASE tools for it.
 SSADM separates an application development project into modules, stages, steps, and
tasks, and offers a framework for describing projects in a fashion suited to managing the
project.

 SSADM’s objectives are to:
 Advance project management and control
 Make more effectual use of experienced and inexperienced development staff

 Develop improved quality systems
 Make projects flexible to the loss of staff

 Allow projects to be supported by computer based tools such as computer aided
software engineering systems
 Create a framework for good communications between participants in a project.

 SSADM can decrease the chances of initial requirements being misunderstood and of the
systems functionality straying from the requirements through the use of inadequate analysis
and design techniques.

Disadvantages

 SSADM is a typical instance of a structured methodology, which means that the purpose of
it is to:
 Formalize the requirements elicitation process to reduce the chances of
misunderstanding the requirements.
 Introduce best practice procedure to the analysis and design process.
 As stated before SSADM can reduce the chances of initial requirements being
misunderstood and of the systems functionality straying from the requirements through
the use of inadequate analysis and design techniques. Though, SSADM assumes that the
requirements (in the form of an agreed requirements specification) will not change during
the development of a project. Following each step of SSADM thoroughly can be time
consuming and there may be a considerable delay between inception and delivery (which
is typically the first time the users see a working system). The longer the development
time the more chance of the system meeting the requirements specification but not satisfying
the business requirements at the time of delivery.

LOVELY PROFESSIONAL UNIVERSITY 15