COMP3120_03_Project_Lifecyles-II_2010

COMP3120_03_Project_Lifecyles-II_2010 - MANAGING SOFTWARE...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
MANAGING SOFTWARE DEVELOPMENT COMP 3120 Project Lifecycles (ii) Chris Johnson, Mark Grundy, Elisa Baniassad
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad Phases of Software Development (Review) 1. Conception & Initiation: establishes the need, investigates feasibility, mounts a proposal to proceed 2. Design and Development: using guidelines from 1, design the product, outline the development method, detail plans for creating and/or implementing the product 3. Implementation and Construction: Executes the plan and designs of 2 4. Commission and Handover: confirm implementation, bring the product into effect and terminate the project
Background image of page 2
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad Phases vs Effort & Duration (Review) E f o r t
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad But what if… We don t know whether the project is feasible? Benefits are uncertain? Requirements are unclear or evolving? Suppliers are unreliable or untested? Team skills are patchy? Technologies are unfamiliar or evolving? Customer acceptance/adoption is uncertain?
Background image of page 4
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad Example A law enforcement agency of 15,000 personnel wants a new operations and intelligence system to: Track cases, investigations, clearance rates and staff workloads Match names of suspects and interviewees across cases Link names of suspects to known associates and past convictions Link evidence to other cases Link to other law enforcement systems nationally Nominal budget is $50M Current operations system has been used for 15 years Need is urgent (old systems failing), but no business-case to proceed An environmental scan shows that no identical system exists in the world In-house IT has no history of delivering a project of this scale and complexity Officers dislike using IT and most have little experience in intelligence analysis
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad Key questions Is it feasible within the budget? Should we invest $50M? More? Or less? Construction: adapt another system, integrate best of breed components, or build from scratch? Build it ourselves or hire people in to do it? How to establish requirements with so little experience in IT/intelligence analysis? How to ensure that customer sees the benefits and not just the system? How to manage delivery?
Background image of page 6
COMP3120 – Managing Software Development Chris Johnson, Mark Grundy, Elisa Baniassad Feasibility Has it been done before? What did it cost? How long did it take? What were the problems?
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/12/2010 for the course CSIT COMP3120 taught by Professor Markgrundy during the Three '10 term at Australian National University.

Page1 / 32

COMP3120_03_Project_Lifecyles-II_2010 - MANAGING SOFTWARE...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online