MIS 5241 Systems Analysis. MIS 5242 Agenda Why Systems Analysis? Precursors of Analysis The Process of Systems Analysis The Products of Systems Analysis.

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

Systems Development Environment
Principles of Information Systems, Tenth Edition
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
Chapter 1 Assuming the Role of the Systems Analyst
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Computers: Tools for an Information Age
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, Fifth Edition
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
Chapter 1 Assuming the Role of the Systems Analyst
Chapter 4: Beginning the Analysis: Investigating System Requirements
System Analysis System Analysis - Mr. Ahmad Al-Ghoul System Analysis and Design.
SDLC and Related Methodologies
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design: The Big Picture
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Accounting systems design & evaluation 9434SB 12 April 2002.
Chapter 4 Investigating System Requirements
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 14 Information System Development
OCR ICT for A2 © Hodder Education 2009 Chapter 1 The systems cycle.
R EQUIREMENTS G ATHERING Getting the Scoop. T HE TASK One of the most difficult tasks in database development is getting all the requirements. A successful.
Describe the Program Development Cycle. Program Development Cycle The program development cycle is a series of steps programmers use to build computer.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
System Planning (Preliminary Investigation Overview)
IS2210: Systems Analysis, Systems Design and Change Twitter:
I Power Higher Computing Software Development The Software Development Process.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.
Requirements Collection By Dr. Gabriel. Requirements A requirement is any function, constraint, or property that the system must provide, meet, or satisfy.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 10 – 1 Systems Planning and Analysis Chapter 10.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
1 Systems Analysis & Design 7 th Edition Chapter 2.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 1 Assuming the Role of the Systems Analyst.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Systems Analysis and Design
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Systems Planning and Analysis
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
INFS 6225 Object Oriented Systems Analysis & Design
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Members: Keshava Shiva Sanjeeve Kareena
Chapter 1 The Systems Development Environment
Presentation transcript:

MIS 5241 Systems Analysis

MIS 5242 Agenda Why Systems Analysis? Precursors of Analysis The Process of Systems Analysis The Products of Systems Analysis Summing It Up

MIS 5243 Why Systems Analysis Use of a System All systems have a life cycle. Start with “using” Change Generally a change in the environment uncovers needs Implications of Change These needs are manifested in suboptimal action Reaction to Implications A match must be found between what is and what should or can be

MIS 5244 Basic Problem Solving Use of a System Accumulate experience with a system Change Notice gap, document it Implications of Change Try to characterize gap systematically Reaction to Implications Describe what has to be changed to cope See Think Say

MIS 5245 Precursors of Analysis Experience with existing system –There might not be an existing system Environment or system changes –Neither is more likely Someone notices or anticipates effects of changes A systematic study is called for

MIS 5246 Process of Systems Analysis Document current system Detail “symptoms” Determine alternatives Evaluate alternatives (feasibility) Select or prioritize alternatives Create logical design (functions) Create physical design (processes) User Involvement T I M E

MIS 5247 Activities in the Process Detailed observation of users Interviews with users Economic, process evaluation Feasibility study (time, money, will, technical) Alternative evaluation Charting, functional specification Process design

MIS 5248 Roles in the Process Client and client management Users (current and/or planned) Other stakeholders Systems analysts Facilitators Prototypers* or builders * In prototyping, a mock system is constructed and continuously modified until it meets user needs. The result is an “implicit” model of what must actually be constructed. Prototypes are rarely efficient and generally have to be optimized by technical people.

MIS 5249 Products of Systems Analysis Document Current System System Description Determine User Needs User Requirements Generate & Evaluate Alternatives Feasibility Study Determine Functionality Logical Specs Usually text, sometimes charts Various graphical formats Text, system diagrams Technical charts, flowcharts, data flow diagrams, various data representation charts, process charts

MIS Summing It Up Driven by organizational needs Based on system theory User involvement falls during SA Client is in control Methods are technical Generally work is collaborative, but might not always be SA is part of a larger, more complex process