K201week 5

K201week 5 - K201week 5 Phase 1:Planning Planning phase:...

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

View Full Document Right Arrow Icon
K201week 5
Background image of page 1

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

View Full DocumentRight Arrow Icon
Phase 1:Planning Planning phase: establishing high-level plan of the intended project and determining project goals Identify and Select system for development Assess Project Feasibility Develop Project plan
Background image of page 2
Identify and Select System for Development Systems development focuses on solving a problem or taking advantage of an opportunity Critical success factor: factor critical to organization’s success. Prioritization. Value Chain Analysis Strategic Alignment Cost benefit analysis Resource availability Project size, duration and difficulty
Background image of page 3

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

View Full DocumentRight Arrow Icon
Assess Project Feasibility A feasibility study determines if the proposed solution is feasible and achievable from financial, technical and organizational standpoint. Economic Feasibility Study (CBA) Legal and contractual Feasibility study Operational Feasibility Schedule Feasibility Technical Feasibility
Background image of page 4
Develop project plan Hard, important, activity Guiding force behind on-time delivery of a complete and successful system Updating of the project plan must be done if any changes occur.
Background image of page 5

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

View Full DocumentRight Arrow Icon
Phase 2:Analysis Involves analyzing end-user business requirement, refining project goals into defined function and operations of intended system. Create a business requirement Create Process diagrams Perform a buy versus build analysis.
Background image of page 6
Business Requirements They are the detailed set of business requests the system must meet in order to be successful. At this point, there is little or no concern with any implementation or reference to technical details. Requirements definition document: contains final set of business requirements, prioritized in order of importance Sign off: is the system user’s actual signatures indicate that they approve all business requirements. Methods for gathering business requirements
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 04/07/2008 for the course BUS K201 taught by Professor Johnson during the Spring '08 term at Indiana.

Page1 / 23

K201week 5 - K201week 5 Phase 1:Planning Planning phase:...

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