11 CPIT 456 by Dr. M. Rizwan Jameel Qureshi Chapter 2.

Slides:



Advertisements
Similar presentations
Chapter 7 Managing Risk.
Advertisements

Project Management Concepts
Chapter 3 Managing the Information Systems Project
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
© 2005 by Prentice Hall Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
© 2008 by Prentice Hall 3-1 ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
System Planning (Overview of Feasibility)
Moving from Analysis to Design
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
What is a project? Project Management Institute definition
Chapter 3 Managing the Information Systems Project
Systems Development Life Cycle
Professor Michael J. Losacco CIS 1150 – Introduction to Computer Information Systems Systems Analysis and Design Chapter 12.
The Analyst as a Project Manager
Jump to first page 30/06/ Chapter 1 System Development Environment.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Computer System Analysis
Chapter 3 : Managing the Information Systems Project.
Project Planning Class 7. SDLC Project Identification & Selection Project Initiation & Planning *** Analysis Logical Design Physical Design Implementation.
© 2005 by Prentice Hall 3-1 Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Fourth Edition.
INFO425: Systems Design INFORMATION X Finalizing Scope (functions/level of automation)  Finalizing scope in terms of functions and level of.
CIS 321—IS Analysis & Design Chapter 3: The Analyst as a Project Manager.
Chapter 14 Information System Development
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
1 Determining Feasibility and Managing Analysis and Design Activities.
SYSTEMSDESIGNANALYSIS 1 Chapter 3 Feasibility Jerry Post Copyright © 1997.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Managing the Information System Project Dr. Dania Bilal IS 592 Spring 2005.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 8 Moving from Analysis to Design.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 Chapter 5 Software Project Planning. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling,
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Chapter 3 Managing the Information Systems Project
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Software Engineering (CSI 321) Project Planning & Estimation 1.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
11 CPIT 456 by Dr. M. Rizwan Jameel Qureshi Chapter 3 Risk Management.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Accounting systems design & evaluation 9434SB 18 March 2002.
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 11 Project Management.
Chapter 3 Managing the Information Systems Project
Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
TIM 58 Continuing Ch 2: Project Management
Systems Analysis and Design in a Changing World, 4th Edition
Chapter 6: Database Project Management
Business System Development
Software Engineering (CSI 321)
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
CIS 210 Systems Analysis and Development
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Modern Systems Analysis and Design Third Edition
Chapter 3 Managing the Information Systems Project
Modern Systems Analysis and Design Third Edition
Presentation transcript:

11 CPIT 456 by Dr. M. Rizwan Jameel Qureshi Chapter 2

2 What is Technical Feasibility?

3 TECHNICAL FEASIBILITY Technical feasibility is composed of estimating: Hardware cost (HW); SW cost. SW cost includes the purchasing of SW required to develop the project, such as OS, server, front end and back end. HW cost includes the purchasing of HW required to develop the project, such as number of system units, monitors, keyboards, mousses and printers.

4 What is Operational Feasibility?

5 Operational Feasibility The operational cost includes all cost that is required to run the SW system operationally at all sites of the organization. It includes the computer terminals needed at each office, the cabling to establish network, salary required hiring computer operators and backup cost.

6 What is Schedule Feasibility?

7 Schedule Feasibility Schedule feasibility is used to display total scheduled time vs. the activities performed needed to complete the project. There are two main types of charts are drawn to represent schedule feasibility. – Gantt chart – PERT chart Gantt chart displays the activities against the time as a horizontal bar only whereas PERT chart also displays the interaction among the activities. PERT chart abbreviation is Program Evaluation and Review Technique. Time overlapping activities can be seen using the Gantt chart where as which activities can be done in parallel

8 Management Issues Who is going to finance the project? Who is/are suspected customer/s? Who is the champion of the project in the top management? How to manage risks regarding the project?

9 What is Costs-Benefits Analysis Sheet? Project manager prepares costs-benefits analysis sheet at the end of proposal document showing the tangible benefits of the SW system against the cost. The overall objective of costs-benefits analysis sheet is to show to the stakeholders that benefits would recover the investment cost.

10 The Main Criteria To Approve The Proposal Or PSD Or Baseline Plan How much the new system will save costs? When and where cost will be saved? How much new system will improve the organizational processes and information processing? How much better services are provided to customers? Will the system implement within affordable time? Is the organization having required resources? The benefits are long term or short term. Long-term benefits are covering the development cost or not.

11 Main benefits of the Baseline Plan To uncover main functional requirements. Track the project in the correct direction. To remove all misunderstandings and uncertainties regarding the project. Users can makeup their mind before a detailed analysis is made. To maintain a feedback loop among the customer, analyst and the developer. It is easy for an analyst to trace and manage the effects on the base line plan whenever a change is made in the project scope or goals

12 Make-Buy Decisions Make-buy decisions method is a graphical representation of alternative solutions using a decision tree. The alternative solutions could be: – Purchased off-the-shelf components; – Reuse full experienced or partially experienced components and then integrate to meet the specific needs; – Customized internal SW development; – Contract the SW house. The project director calculates the expected cost of each path and evaluates the least cost path.

13 Make-Buy Decisions The formula to calculate the expected cost cost = ∑ (path probability) * estimated cost Project manager used the make-buy decisions based on the following conditions

14 Problem 1

15 Problem # 1 The decision tree for a SW-based system ‘X’: – Internal SW development from scratch; – Reuse existing partial experienced components; – Customized off-the-shelf SW; – Contract to the SW house. – Calculates the least cost by using the decision tree.

16 Solution Expected cost (build) = 0.3 *($ 380 K) + 0.7* ($450K) = $ 429 K

17 Solution Expected cost (reuse) = 0.4 *($ 275 K) * [0.2*($310K) *(490K)] = $ 382 K Expected cost (buy) = 0.7 * ($ 210 K) + 0.3*($400K) = $ 267 K Expected cost (contract to SW house) = 0.6* ($ 350 K) *($500K) = $ 410 K It is clear that expected cost of buying the off-the- shelf SW is the least among all paths.