CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

System Planning (Preliminary Investigation Overview)
Chapter 2 Analyzing the Business Case.
Systems Analysis and Design 9th Edition
Chapter 2.
12 C H A P T E R Systems Investigation and Analysis and Analysis.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Fundamentals of Information Systems, Second Edition
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 2.
Systems Development Life Cycle
Analyzing the Business Case
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Fact-Finding Fact-Finding Overview
Introduction to System Analysis and Design - Dr. Mahmoud Abu-Arra - Dr. Mahmoud Abu-Arra - Mr. Ahmad Al-Ghoul System Analysis and Design.
Chapter 4: Beginning the Analysis: Investigating System Requirements
System Planning Analyzing the Business Case
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Introduction to Systems Analysis and Design
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Requirements Modeling
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design: The Big Picture
Chapter 2: Analyzing Business Case Phase 1: Systems Planning
CIS 321—IS Analysis & Design Chapter 3: The Analyst as a Project Manager.
System Planning- Preliminary investigation
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Business Case Justification System Planning
Chapter 14 Information System Development
Lecture 4 1 Introduction to Systems Planning Lecture 4 2 Objectives n Describe the strategic planning process n Explain the purpose of a mission statement.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
Prof. Mohammad Moizuddin
Phase 1: Preliminary Investigation or Feasibility study
Chapter 2 Analyzing the Business case
System Planning (Preliminary Investigation Overview)
Systems Analysis and Design
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Development Life Cycle
Topic 2 Analyzing the Business Case.  Describe the strategic planning process and why it is important to the IT team  Explain the purpose of a mission.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Lecture 21 Introduction to System Development Life Cycle - Part 1.
1 Systems Analysis & Design 7 th Edition Chapter 2.
Systems Analysis & Design 7 th Edition Chapter 2.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Phase 1 Systems Planning
MANAGEMENT INFORMATION SYSTEM
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
The System Development Life Cycle
Systems Development Life Cycle
Systems Analysis and Design
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
SYSTEMS ANALYSIS Chapter-2.
THE FEASIBILTY STUDY LECTURE-5.
Business System Development
Systems Analysis and Design 10th Edition
The System Development Life Cycle
Analyzing the Business Case
Introduction to Projects
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Systems Development An Overview of Systems Development
Joint Application Development (JAD)
Presentation transcript:

CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design

SUMMARY This chapter explains why it is important to understand business operations and requirements, how IT projects support a company’s overall strategic plan, how systems projects get started, and how systems analysts conduct a preliminary investigation and feasibility study.

COURSE LEARNING OUTCOME CLO 1 – Explain the concept of System Analysis and Design and project management relating to various model, tools and techniques. (C4, PLO1) CLO 2 – Produce the key deliverable’s of System Development Life Cycle (SDLC) activities. (P4, C3, PLO2, PLO1)

TOPIC 2.1Preliminary Investigation

TOPIC 2.1 PRELIMINARY INVESTIGATION

Preliminary Investigation A systems analyst conducts a preliminary investigation to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with managers and users. The analyst gathers facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. The end product of the preliminary investigation is a report to management.

Interaction With Managers And Users Let people know about the investigation and explain your role Employee attitudes and reactions are important and must be considered Be careful in your use of the word problem Question users about additional capability they would like to have

Planning The Preliminary Investigation During a preliminary investigation, a systems analyst typically follows a series of steps The exact procedure depends on the nature of the request, the size of the project, and the degree of urgency

Steps In Preliminary Investigation

STEP 1 : Understand The Problem Or Opportunity – A popular technique for investigating causes and effects is called a fishbone diagram, or Ishikawa diagram – A fishbone diagram is an analysis tool that represents the possible causes of a problem as a graphical outline. – When using a fishbone diagram, an analyst first states the problem and draws a main bone with sub-bones that represent possible causes of the problem.

Steps In Preliminary Investigation STEP 1 : Understand The Problem Or Opportunity

Steps In Preliminary Investigation STEP 1 : Understand The Problem Or Opportunity

Steps In Preliminary Investigation STEP 1 : Understand The Problem Or Opportunity

Steps In Preliminary Investigation STEP 2 : Define The Project Scope & Constrain – Determining the project scope means defining the specific boundaries, or extent, of the project. – Projects with very general scope definitions are at risk of expanding gradually, without specific authorization, in a process called project creep. To avoid this problem, you should define project scope as clearly as possible.

Steps In Preliminary Investigation STEP 2 : Define The Project Scope & Constrain – A constraint is a requirement or condition that the system must satisfy or an outcome that the system must achieve. A constraint can involve hardware, software, time, policy, law, or cost – When examining constraints, you should identify their characteristics. Present versus future Internal versus external Mandatory versus desirable

Steps In Preliminary Investigation STEP 2 : Define The Project Scope & Constrain – PRESENT VERSUS FUTURE - Is the constraint something that must be met as soon as the system is developed or modified, or is the constraint necessary at some future time? – INTERNAL VERSUS EXTERNAL - Is the constraint due to a requirement within the organization or does some external force, such as government regulation, impose it? – MANDATORY VERSUS DESIRABLE - Is the constraint mandatory? Is it absolutely essential to meet the constraint, or is it merely desirable?

Steps In Preliminary Investigation STEP 2 : Define The Project Scope & Constrain

Steps In Preliminary Investigation STEP 2 : Define The Project Scope & Constrain – Regardless of the type, all constraints should be identified as early as possible to avoid future problems and surprises

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – The objective of fact-finding is to gather data about project usability, costs, benefits, and schedules. – Fact-finding involves various techniques – Depending on what information is needed to investigate the systems request, fact-finding might consume several hours, days, or weeks

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Analyze Organization Charts Conduct interviews Review documentation Observe operations Conduct a user survey

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Analyze Organization Charts – You should obtain organization charts to understand how the department functions and identify individuals you might want to interview. – Organization charts often can be obtained from the company’s human resources department. – If such charts are unavailable, you should obtain the necessary information directly from department personnel and then construct your own charts

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Conduct interviews – The interviewing process involves a series of steps: » 1. Determine the people to interview. » 2. Establish objectives for the interview. » 3. Develop interview questions. » 4. Prepare for the interview. » 5. Conduct the interview. » 6. Document the interview. » 7. Evaluate the interview.

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Review documentation – Although interviews are an extremely important method of obtaining information, you also might want to investigate the current system documentation. – The documentation might not be up to date, so you should check with users to confirm that you are receiving accurate and complete information.

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Observe operations – You might see how workers carry out typical tasks. – You might choose to trace or follow the actual paths taken by input source documents or output reports. – In addition to observing operations, you might want to sample the inputs or outputs of the system.

Steps In Preliminary Investigation STEP 3 : Perform Fact Finding – During fact finding, you might; Conduct a user survey – Interviews can be time consuming. – Sometimes you can obtain information from a larger group by conducting a user survey. – In this case, you design a form that users complete and return to you for tabulation. – A survey is not as flexible as a series of interviews, but it is less expensive, generally takes less time, and can involve a broad cross-section of people.

Steps In Preliminary Investigation STEP 4: Analyze Project Usability, Cost, Benefit, and Schedule Data – Before you can evaluate feasibility, you must analyze this data carefully – Also, you should develop time and cost estimates for the requirements modeling tasks for the next SDLC phase, systems analysis – Specifically, you should consider the following: What information must you obtain, and how will you gather and analyze the information?

Steps In Preliminary Investigation STEP 4: Analyze Project Usability, Cost, Benefit, and Schedule Data What sources of information will you use, and what difficulties will you encounter in obtaining information? Will you conduct interviews? How many people will you interview, and how much time will you need to meet with the people and summarize their responses?

Steps In Preliminary Investigation STEP 4: Analyze Project Usability, Cost, Benefit, and Schedule Data Will you conduct a survey? Who will be involved? How much time will it take people to complete it? How much time will it take to prepare it and tabulate the results? How much will it cost to analyze the information gathered and to prepare a report with findings and recommendations?

Steps In Preliminary Investigation STEP 5: Evaluate Feasibility – Start by reviewing the answers to the questions you asked – Also consider the following guidelines: Operational feasibility Technical feasibility Economic feasibility Schedule feasibility

Steps In Preliminary Investigation STEP 5: Evaluate Feasibility – Operational feasibility Your fact-finding should have included a review of user needs, requirements, and expectations. When you analyze this data, you should look for areas that might present problems for system users and how they might be resolved. Because operational feasibility means that a system will be used effectively, this is a vital area of concern.

Steps In Preliminary Investigation STEP 5: Evaluate Feasibility – Technical feasibility The fact-finding data should identify the hardware, software, and network resources needed to develop, install, and operate the system. With this data, you can develop a checklist that will highlight technical costs and concerns, if any.

Steps In Preliminary Investigation STEP 5: Evaluate Feasibility – Economic feasibility Using the fact-finding data, you can apply the financial analysis. The cost benefit data will be an important factor for management to consider. Also, a cost estimate for the project development team will be built into the project management plan.

Steps In Preliminary Investigation STEP 5: Evaluate Feasibility – Schedule feasibility The fact-finding data should include stakeholder expectations regarding acceptable timing and completion dates. As mentioned previously, often a trade-off exists between a project’s schedule and its costs. For example, compressing a project schedule might be possible, but only if the budget is increased accordingly. The schedule data will be incorporated into the project plan in the form of task durations and milestones.

Steps In Preliminary Investigation STEP 6: Present Results and Recommendations to Management – The final task in the preliminary investigation is to prepare a report to management – The format of the preliminary investigation report varies from one company to another – The report must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC

Steps In Preliminary Investigation STEP 6: Present Results and Recommendations to Management – A typical report might consist of the following sections: Introduction Systems request summary Findings Case for action Project Roles Time & cost estimates Expected benefits Appendix

End Of Chapter 2 Thank You