COMP3120_02_Project_Lifecyles-I_2010

COMP3120_02_Project_Lifecyles-I_2010 - MANAGING SOFTWARE...

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

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

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

View Full DocumentRight Arrow Icon
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 2 Software Development Lifecycle Divides the work into manageable stages Describes each stage as: Input, Process Output Supports hold-points and approvals Supports management criteria, like: Performance Quality Risk-management
Background image of page 2
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 3 Phases of Software Development 1. 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 3

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

View Full DocumentRight Arrow Icon
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 4 E f o r t
Background image of page 4
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 5 Time S ta k e h o ld r R is U n c t a in ty C s f g
Background image of page 5

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

View Full DocumentRight Arrow Icon
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 6 Inputs: Project Brief describing problem or opportunity Project Charter describing intention, mandate and motivation Process: Feasibility study describing options, costs/benefits, risks, approaches and recommendations Hold Point: Market Research Approvals Output: Project Proposal (a solution to the original problem) Decision: Proceed with the Project?
Background image of page 6
COMP3102 - Managing Software Development C. Johnson, E. Baniassad, M. Grundy 7 Phase 1: Key Activities Gather data Identify need Establish: Goals, objectives Economics, feasibility Stakeholders Risk level Strategy/approach Potential team Identify alternatives Present proposal Gain approval to proceed
Background image of page 7

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

View Full DocumentRight Arrow Icon
C. Johnson, E. Baniassad, M. Grundy 8 Phase 1: Who’s Involved A Sponsor or Champion of the problem Concerned stakeholders Investment Board Someone with authority to commit the
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 26

COMP3120_02_Project_Lifecyles-I_2010 - MANAGING SOFTWARE...

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

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