CS3007A Software Project Management

Problem Sheet 11

Lecturer: Dr Robert Macredie

E-mail: Robert.Macredie@brunel.ac.uk,

Introduction

In the eleventh session we discussed two broad themes. The first looked at the 'fixed-point theorem of information systems', a characterisation of the way in which software development and management is approached with a project-based focus and the inherent problems which this approach brings. We went on to consider the ways in which 'palliatives' have been adopted to try to ease some of the 'pain' that the traditional project approach brings, and explored why such palliatives cannot address the core problems. The second theme considered why we might have ended up in this position Ð with formalised, project-based approaches to SPM Ð and how formalisation might contribute to the problems.

Learning Outcomes

The learning outcomes for the problem sheet are as follows:


(i)     you should be able to explain the fixed-point theorem of information 
        systems and discuss its relation to SPM;

(ii)    you should be able to critically discuss palliatives to the fixed-point theorem, 
        their assumptions and the ways in which they aim to Ôease the painÕ 
        of software development and management;

(iii)   you should be able to explain the pressures for formalisation in software 
        development and management;

(iv)    you should be able to critically discuss the problems that we face in software 
        development and management and relate them to the formalised 
        approaches currently used.

Questions

(i)     What are the broad limitations of taking a project approach to 
        developing software systems?  The fixed-point theorem of 
        information systems captures one of these central problems.  
        Explain which one?

(ii)    In session 10, we looked at three emerging approaches in SPM 
        which we might consider palliatives to the fixed-point theorem 
        of information systems: Rapid Application Development (RAD); 
        the Capability Maturity Model (CMM); and Component-Based 
        Development (CBD).  How does each one aim to address some 
        of the problems in taking a project approach to the development 
        of software systems.

(iii)   Maintenance might also be seen as a palliative.  How does it aim 
        to cope with some of the inherent problems in taking a 
        project approach?

(iv)    What pressures have led to us adopting formalised approaches 
        to the management and development of software? 

(v)    How do you think that the problems that we face in software 
        development and management are related to the formalised 
        approaches currently used?

I would encourage you to work in groups of around five for this and subsequent exercises.

Robert Macredie

5 December 1998