Chapter 12 Systems Investigati on and Analysis
Apr 01, 2015
Chapter 12
Systems Investigation and Analysis
Chapter 12 IS for management2
Participants in System Development
StakeholdersBenefit from the systems develop- ment effort
UsersInteract with the system regularly
Systems AnalystsSpecialize in analyzing & designing business systems.
ProgrammersModify/develop programs to satisfy user requirements.
Chapter 12 IS for management3
Typical Reasons for Initiating a Systems Development Project
Chapter 12 IS for management4
Information System Planning
Information Systems PlanTranslates strategic & organizational goals into systems development initiatives.
Creative AnalysisInvestigates new approaches to existing problems.
Critical AnalysisUnbiased & careful questioning of whether system elements are related in the most effective/ efficient ways.
Chapter 12 IS for management5
Establishing Objectives for Systems Development Performance
– Quality or usefulness of output
– Quality or usefulness of output format
– Speed at which output is generated
Cost– Development costs
– Costs related to the uniqueness of the application
– Fixed investments in hardware & related equipment
– On-going operating costs
Chapter 12 IS for management6
Systems Development & the Internet
Applications being moved to the Internet– Sales
– Order placement
– Access to product information
Building a static Web site (much easier than dynamic Web site)
Tools to help with Internet systems development
Chapter 12 IS for management7
Systems Development Life Cycle
Chapter 12 IS for management8
Systems Development Life Cycle
Systems InvestigationID problems & opportunities
Systems AnalysisStudy existing systems & work processes
Systems DesignLays out how the system will do what it will do
Systems ImplementationAssemble components & put new/ modified system into operation.
Systems Maintenance and ReviewEnsures the system operates & is modified to keep up with business changes.
Chapter 12 IS for management9
Prototyping: The Iterative Life Cycle
Operational PrototypeAccesses real data files, edits input data, makes necessary computations & comparisons, & produces real output
Non-operational PrototypeA mockup or model that includes output & input specifications & formats
Chapter 12 IS for management10
General Prototyping Model
Rapid Application Development (RAD)Employs tools, techniques, & methodologies designed to speed application development, automates source code generation, & facilitate user involvement in design & development activities
Joint Application Development (JAD)Involves group meetings in which users, stakeholders, & IS professionals work together to analyze existing systems, propose solutions, & define requirements for a new or modified system
Chapter 12 IS for management11
Factors Affecting Systems Development Success
Managing ChangeRequires the ability to recognize existing or potential problems & deal with them before they become a serious threat to the success of the new/ modified system
Chapter 12 IS for management12
Factors Affecting Systems Development Success
Use of project management tools– Schedule
– Milestone
– Deadline
– Critical path
– Program Evaluation Review Technique (PERT)
– Gantt chart
Chapter 12 IS for management13
Computer-Aided Software Engineering (CASE) Tools
Tools that automate many systems development tasks – Upper CASE tools focus on activities associated with
the early stages of systems development
– Lower CASE tools focus on the later implementation stages of systems development
– Integrated (I-CASE) tools combine upper/lower CASE
Chapter 12 IS for management14
Systems Investigation
Identifies potential problems & opportunities & considers them in light of the company’s goals
SI report summarizes results of systems investigation & the process of feasibility analysis & recommends a course of action
Chapter 12 IS for management15
Feasibility Analysis
Technical Feasibility: Can the hardware, software, & other system components be acquired or developed to solve the problem?
Operational Feasibility: Can the project be put into action or operation?
Schedule Feasibility: Can the project be completed in a reasonable time?
Economic Feasibility: Does the project make financial sense?
Chapter 12 IS for management16
Internal & External Sources of Data
Internal sources Users, stakeholders, &
managers Organization charts Forms and documents Procedure manuals & policies Financial reports IS manuals Other manuals & business
processes
External Sources Customers Suppliers Stockholders Government
agencies Competitors Outside groups Journals, media Consultants
Chapter 12 IS for management17
Data Collection
Structured Interview Unstructured
Interview Direct Observation Questionnaires Statistical Sampling
Chapter 12 IS for management18
Data Analysis
Manipulating collected data so it is usable for development team members participating in systems analysis
Data Modeling: A commonly accepted approach to modeling organizational objects & associations that employs both text & graphics
Activity Modeling: A method to describe related objects, associations, & activitiesData Flow Diagram: A diagram that models objects, associations, & activities by describing how data can flow between & around them
Chapter 12 IS for management19
DiagramsEntity-Relationship Diagram (ERD)
Data Flow Diagram (DFD)
Chapter 12 IS for management20
Application Flowcharts
Charts that show relationships among applications or systems
Chapter 12 IS for management21
Grid Charts
A table that shows relationships among the various aspects of a systems development effort
Chapter 12 IS for management22
Requirements Analysis
An assessment used to determine user, stakeholder, & organizational needs
Chapter 12 IS for management23
The Systems Analysis Report
Strength and weaknesses of existing system from a stakeholder’s perspective
User/stakeholder requirements for the new system Organizational requirements Description of what new information systems
should do to solve the problem
Chapter 12 IS for management24
Case study
Case 1: FAA system development project, page 565