Chapter 1: Intro to Software Project Management 1.

1 Software Prj - satisfy real needs To do this - Id project stakeholders and objectives Must know present state of prj before we will know if future objectives will be

met 1.2 Why is Software Project management important? Money Prj shortcomings because of mismanagement of projects (lack of skills and proven approach to prj mngment & risk mngment 1.3 What is a Project? Planned activity (planning - thinking carefully about what you do) Boundary between Non-Routine Prj and Routine Job: (First time you do a Routine task it will be like a project) Characteristics of Projects: - non routine tasks - planning required - specific objectives to be met, or specific product to be created - predetermined time-span - work carried out for someone else - involves specialisms - people formed into temp-work groups to carry out tasks - work done in phases - resources available are constrained - project is large or complex 1.4 Software Prj vs Other types of Prj --according to Fred Brooks, the following makes Software Prjects difficult -- Invisibility: Prgress not immediately visible, thus The Process of making the invisible Visible - Complexity: - Conformity: To requirements of Human Clients (Organisational Stupidity) - Flexibilaty: Think it is easy to change software w/o thinking of the changes in eg worklow 1.5 Contract mngment and Technical Project mngment Leans towards the Technical Prj mngers 1.6 Activities covered by Software Prj Mngment

3 Successive Processes that bring new system into being: - FeasablilityStudy (Is it worth doing?) - Plan (How do we do it?) - Project Execution (Do it!) 1. 2. Feasibility Study: asses if valid Business Case exist Info gathered about requirements of proposed application Requirements elicitation (complex and difficult) Stakeholders know the aims, but not sure of means of achievement Estimation of development & operational costs (Feasibility study can be project onits own, if large...)

Planning - If feasibility study apears viable, then Project Planning starts - Create outline Plan, and Detailed one for First Stage - Planing of later stages left till nearer their startdate

Project Execution - Contains Design and Implementation Sub Phases - Design: Making decisions about form of Products to be created - (Relate to external appearance of Software, thus User Interface, or Internal Architecture) - Planning mostly influenced by Design decisions - (Software with 5 major components likely to have 5 sets of activities to create them) ISO 12207 Software Development Life Cycle System Requirements Analysis Requirements System Architecture Design Requirements Software Requirements Analysis Requirements Software Architecture Design Design Software Requirements Analysis Design Software Detailed Design Code and test Software Code and Test Code and test Software Integration Code and test Software Qualification Test Code and test Software Integration Code and test System Qualification Test Code and test Software Installation Installation/Acceptance Report Software Acceptance Support Installation/Acceptance Report

3.