© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development.

Slides:



Advertisements
Similar presentations
CSIS 3600 Systems Analysis and Design
Advertisements

Managing Project Scope
CHAPTER 5: Identifying and Selecting Systems Development Projects
Initiating and Planning Systems Development Projects
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 6 Initiating and Planning Systems Development Projects 6.1.
Systems Planning & Selection Project identification & selection Project initiation & planning.
Project Estimation Describe project scope, alternatives, feasibility.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Initiating and Planning Systems Development Projects.
Modern Systems Analysis and Design Third Edition
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2008 by Prentice Hall 1 Chapter 2. © 2008 by Prentice Hall 2 Project – a planned undertaking of related activities to reach an objective that has a.
Chapter 4 Determining Feasibility and Managing Analysis and Design Activities Systems Analysis and Design Kendall & Kendall Sixth Edition.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph.
Feasibility By Garrett Jones and Ryan Butler. All projects are feasible given unlimited resources and infinite time. Unfortunately, most projects must.
Feasibility Study: Economic feasibility Technical feasibility
Chapter 5 Initiating and Planning Systems Development Projects
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design.
Initiating and Planning Systems Development projects
Systems Analysis and Design with UML Version 2
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 5 Initiating and Planning Systems Development Projects
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Chapter 5 Initiating and Planning Systems Development Projects
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design.
Initiation and Planning Systems Development Projects
Chapter 5 : Initiating and Planning Systems Development Projects.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
© 2005 by Prentice Hall Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
4-1 © Prentice Hall, 2007 Chapter 4: Selecting and Planning Projects Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S.
Information Systems System Analysis 421 Class Three Initiating and Planning Systems Development Projects.
Chapter 5 Initiating and Planning Systems Development Projects MIS 215 System Analysis And Design.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
BIS 360 – Lecture Four Ch. 5: Identifying and Selecting Projects
Cis339 Modern Systems Analysis and Design Fifth Edition Chapter 5 Initiating and Planning Systems Development Projects 5.1.
4-1 © Prentice Hall, 2004 Chapter 4: Project Management and Planning Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph.
NURHALIMA 1. Describe steps involved in the project initiation and planning process Explain the need for and the contents of a Statement of Work and Baseline.
9.351 Systems Analysis & DesignPlanning1 Chapter 4: Business and Systems Planning.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Chapter 4: Project Management and Planning Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer.
Chapter 5 Initiating and Planning Systems Development Projects Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation.
Project Estimation Describe project scope, alternatives, feasibility.
Chapter 5 Initiating and Planning Systems Development Projects
Systems Analysis and Design in a Changing World, 4th Edition
Modern Systems Analysis and Design Third Edition
Chapter 6 Initiating and Planning Systems Development Projects
CIS 210 Systems Analysis and Development
Business System Development
Chapter 4 Systems Planning and Selection
Chapter 4 Systems Planning and Selection
Systems Planning: Project Feasibility
Chapter 4 Systems Planning and Selection
Chapter 5 Initiating and Planning Systems Development Projects
Lecture 6 Initiating and Planning Systems Development Projects
Modern Systems Analysis and Design Third Edition
Chapter 5 Initiating and Planning Systems Development Projects
Chapter 5 Initiating and Planning Systems Development Projects
Chapter 6 Initiating and Planning Systems Development Projects
Presentation transcript:

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development Projects

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 2 Learning Objectives 7.Explain the role of an analyst in feasibility and requirement analysis.  Describe the steps involved in the project initiation and planning process.  Explain the need for and the contents of the Statement of Work and Baseline Project Plan.  List and describe various methods for assessing project feasibility.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 3  Describe the differences between tangible and intangible benefits and costs and between one-time and recurring benefits and costs.  Perform const-benefit analysis and describe what is meant by the time value of money, present value, discount rate, net present value, return on investment (ROI), and break-even analysis.  Describe the general rules for evaluating the technical risks associated with a systems development project.  Describe the activities and participant roles within a structured walkthrough. Learning Objectives

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 4  Describe the activities and participant roles within a structured walkthrough. Learning Objectives

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 5 Project Initiation and Planning

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 6 Project Initiation Tasks Establish:  Initiation team  Relationship with customer  Project initiation plan  Management procedures  Project management environment  Project workbook

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 7 Project Planning Tasks Describe project scope, alternatives, feasibility. Divide project into tasks. Estimate resource requirements and create resource plan. Develop preliminary schedule. Develop communication plan. Determine standards and procedures. Identify and assess risk. Create preliminary budget. Develop a statement of work. Set baseline project plan.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 8 Deliverables and Outcomes Business Case  Justification for an information system, expressed as tangible and intangible costs and benefits, and technical/organizational feasibility Baseline Project Plan (BPP) Statement of Work (SOW)

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 9 Statement of Work (SOW) is a “contract” between the IS staff and the customer regarding deliverables and time estimates for a system development project.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 10 System Service Request (SSR) is a form requesting development or maintenance of an information system. It includes the contact person, a problem statement, a service request statement, and liaison contact information.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 11 Assessing Project Feasibility Economic feasibility Technical feasibility Operational feasibility Schedule feasibility Legal and contractual feasibility Political feasibility

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 12 Economic Feasibility Cost-benefit analysis: helps to identify all the financial benefits and costs associated with a project Tangible vs. intangible benefits Tangible vs. intangible costs One-time vs. recurring costs

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 13 Tangible Benefits Benefits that can be measured in dollars and with certainty

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 14 Benefits that cannot easily be measured in dollars or with certainty

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 15 Types of Costs Tangible cost: can be measured in dollars and with certainty Intangible cost: cannot easily be measured in dollars or with certainty One-time cost: a cost associated with project start-up and development or systems start-up Recurring cost: a cost associated with ongoing evolution and use of a system

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 16 Possible IS Project Costs Procurement  Consulting, equipment, site preparation, capital, management time Start-up  Operating systems, communications installation, personnel hiring, organizational disruption Project-related  Application software, software modification, personnel overhead, training, data analysis, documentation Operating  System maintenance, rental, asset depreciation, operation and planning

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 17 One-time Costs

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 18 Recurring Costs

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 19 Three Financial Measurements for Economic Feasibility Net Present Value (NPV)  Use discount rate to determine present value of cash outlays and receipts Return on Investment (ROI)  Ratio of cash receipts to cash outlays Break-Even Analysis (BEA)  Amount of time required for cumulative cash flow to equal initial and ongoing investment

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 20 Definitions of Terms Present value: current value of a future cash flow Discount rate: rate of return used to calculate the present value of future cash flows Time value of money (TVM): comparing present cash outlays to future expected returns

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 21 Net Present Value PV n = present value of Y dollars n years from now based on a discount rate of i. NPV = sum of PVs across years. Calculates time value of money.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 22 Break-Even Analysis

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 23 Technical Feasibility Assesses the organization’s ability to construct the proposed system Takes into account various project risk factors

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 24 Project Risk Factors Project size  Team size, organizational departments, project duration, programming effort Project structure  New vs. renovated system, resulting organizational changes, management commitment, user perceptions Development group  Familiarity with platform, software, development method, application area, development of similar systems User group  Familiarity with IS development process, application area, use of similar systems

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 25 High technical familiarity mitigates risk due to project size and structure. Low familiarity increases risk.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 26 Other Feasibility Concerns Operational  Does the proposed system solve problems or take advantage of opportunities? Schedule  Can the project time frame and completion dates meet organizational deadlines? Legal and Contractual  What are legal and contractual ramifications of the proposed system development project? Political  How do key stakeholders view the proposed system?

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 27 Baseline Project Plan (BPP) is a document intended primarily to guide the development team. Sections: 1)Introduction 2)System description 3)Feasibility assessment 4)Management issues

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 28 Project Scope statement is part of the BPP introduction. Sections: 1)Problem statement 2)Project objectives 3)Project description 4)Business benefits 5)Deliverables 6)Expected duration

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 29 Factors in Determining Scope Organizational units affected by new system Current systems that will interact with or change because of new system People who are affected by new system Range of potential system capabilities

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 30 Diagram Depiction of Project Scope Context level is a top level data flow diagram. Data flow diagrams are covered in Chapter 7.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 31 Structured Walkthroughs A peer-group review of any product created during the system development process Roles: coordinator, presenter, user, secretary, standard-bearer, maintenance oracle Can be applied to BPP, system specifications, logical and physical designs, program code, test procedures, manuals and documentation

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 32 Structured walkthrough form

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 33 Summary In this chapter you learned how to: 7.Explain the role of an analyst in feasibility and requirement analysis.  Describe the steps involved in the project initiation and planning process.  Explain the need for and the contents of the Statement of Work and Baseline Project Plan.  List and describe various methods for assessing project feasibility.

© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 34  Describe the differences between tangible and intangible benefits and costs and between one-time and recurring benefits and costs.  Perform const-benefit analysis and describe what is meant by the time value of money, present value, discount rate, net present value, return on investment (ROI), and break-even analysis. Summary