kul10SIA2unkris

8/12/2019 kul10SIA2unkris

1/47

2004 Prentice Hall Business Publishing,Accounting Information Systems, 9/e, by Bodnar/Hopwood 101

Systems Planning and Analysis

Chapter 10


2/47


Learning Objective 1

Describe the relationship of

systems analysis to systems

development as a whole.


3/47


Overview of SystemsPlanning and Analysis

Systems planning

involves identifying

subsystems within the information system.

Systems analysis

begins after systems planning

has identified subsystems for development.


4/47



Objectives of Systems Analysis

1. Gain an understanding of the existing system (if one exists).

2. Identify and understand problems.

3. Express identified problems in terms of information needs

and system requirements.

4. Clearly identify subsystems to be given highest priority.

Focus

Identify critical success factors.

Give special attention to these factors.


5/47



Cost Patterns at Varying Development Stages

Cost in

Dollars

SystemsAnalysis

SystemsDesign

SystemsImplementation


6/47


Systems Planning andFeasibility Analysis Phases

4. Developing a strategic

information systems plan

1. Discussing and planning on

the part of top management

2. Establishing a systems

planning steering committee

3. Establishing overall

objectives and constraints


7/472004 Prentice Hall Business Publishing,Accounting Information Systems, 9/e, by Bodnar/Hopwood 107

Systems Planning andFeasibility Analysis Phases

5. Identifying and prioritizing specific

areas within the organization for

the systems development focus

6. Setting forth a systems proposal.

7. Assembling a team of individualsfor purposes of the analysis and

preliminary systems design



Systems Planning andTop Management

Developing objectives and system constraints

Developing a strategic systems plan

Identifying individual projects for priority

Commissioning the systems project



Learning Objectives 2 and 4

Describe the various stages

of systems analysis.

Describe some of the human

problems involved in

systems analysis.



The Steps of Systems Analysis

Step 2:Identify

information

needs

Step 1:Surveycurrent

system

Step 3:

Identifysystems

requirements

Step 4:

Systemsanalysisreport



Phase I: Survey the Present System

Gain a fundamental understanding of

the operational aspects of the system.

Establish a working relationship with users.

Collect important data.

Identify specific problems.




Communication Gap Problem

Systems Analyst

Management

Resistanceto change

Jobsecurity

Uncertainty


13/47



Get to know as many people involved

in the system as soon as possible.

Communicate the benefits

of the proposed system.


14/47



Sources for gathering facts

Analysis of survey findings

Inside

Outside


15/47


Phase II: IdentifyInformation Needs

Identify the managers primary job responsibilities.

Identify the means by which the manager is evaluated.

Identify some of the major problems the manager faces.

Identify the means by which the manager

evaluates personal output.


16/47


Phase III: Identify theSystems Requirements


17/47


Phase IV: Develop aSystems Analysis Report

What are key elements of this report?

A summary of the scope and

purpose of the analysis project

A reiteration of the relationship of the project to

the overall strategic information systems plan

A description of any overall problems

in the specific subsystem being studied


18/47


Phase IV: Develop aSystems Analysis Report

A summary of the decisions being made

and their specific information requirements

Specification of system performance requirements

An overall cost budget and timetable

Recommendations for improving the existing

system and modifying objectives


19/47



Discuss the major techniques

for gathering and organizing

data for systems analysis.


20/47


Techniques for Fact Organization

WarnierOrr Illustration

Due date > = Discount =Determine todays date percent discount gross amount

Compute Due date < Discount = 0total amount todays datedue forinvoices Amount due =

(n) gross discount

Accumulate totalamount due

+

h f h


21/47


Techniques for GatheringFacts for Analysis

Closed-ended questionnaire

Open-ended questionnaire

Structured interviewDepth interview

Document reviews Observation


22/47


Techniques for Fact Organization

Flow charting

Functional analysis

Matrix analysis

Decision analysis

Work distributionWork measurement

Hierarchical function

Narratives File/report summaries


23/47

St i St t d


24/47


Steps in StructuredSystems Analysis

Develop logical data flow diagrams

Define data dictionaries

Define access methods

Define process logic

P h i S t


25/47


Purchasing SystemContext Diagram

Purchasingsystem

Stores

Requisition

Vendors

Purchaseorder

Purchasedetails

Purchasefile

E i f P h i


26/47


Expansion of PurchasingSystem Context Diagram

Stores

Validaterequisition

Vendors

Requisition

Requisitiondetails

Purchaseorder

Purchasefile

Preparepurchaseorder

Details


27/47


28/47


Learning Objectives 5 and 7

Describe the various steps

involved in specifying

systems design alternatives.

Describe the content of a

systems design proposal.


29/47


Steps in Systems Design

Systemsimplementation

Systemsreview and

control

Systemsplanning

and analysis

Systems DesignEvaluatevariousdesigns

1 Preparedesign

specifications

2 Systemsdesign

specifications

3


30/47


Evaluating Design Alternatives

Enumeration of design alternatives

Describing the alternatives

Evaluating the alternatives

Preparing design specifications


31/47


Design of System Elements

Reportsand otheroutputs

Databasedesign

Specify

processing

Specifyinputs

Controlconsiderations

Type of controlFunction of control

Applicable systems component

P epa ing and S bmitting


32/47


Preparing and SubmittingSpecifications

What should the design proposal include?

Specific timetables for completion Budget

Description of personnel requirements

Flowcharts Other diagrams


33/47



Discuss the various

considerations relevant

to preparing design

specifications.


34/47


Design Considerations

System Element Design Consideration

Outputs (report or document) Cost effectivenessRelevanceClarity

TimelinessDatabase Cost effectiveness

IntegrationStandardizationFlexibility

SecurityAccuracyEfficiencyOrganization


35/47


Design Considerations

System Element Design Consideration

Data processing Cost effectivenessUniformityIntegration

AccuracyData input Cost effectiveness

AccuracyUniformityIntegration

Controls and security measures Cost effectivenessComprehensivenessAppropriateness


36/47



Summarize several majordesign techniques.


37/47


Design Techniques

Forms design

Database design

Systems design packages


38/47



Discuss the usefulness ofsystems design packages.


39/47


Systems Design Packages

Data flow diagrams

Narrative documentation

Screen and report prototypes

Data dictionary descriptions


40/47


Choosing Software and Hardware

What are some advantages of

purchased software packages?

They are cheaper.

They are already debugged.

Trials of the product can be made prior

to investing a great deal of money.


41/47



What is the main disadvantage of

purchased software packages?

They rarely exactly meet a companys needs.


42/47



It is usually safe to be content with the

hardwareon which that software runs.

It is recommended to get machinery

that is upwardly compatible.


43/47


Real Systems Life Cycle

DisillusionmentTotal

confusionWild

enthusiasm


44/47


Real Systems Life Cycle

Search forthe guilty

Punishment ofthe innocent

Promotion ofnonparticipants

Communication Problems in


45/47


Communication Problems inSystems Development

As proposedby the user

manager

As approvedby the steering

committee

As structuredby the dataadministrator


46/47


47/47

End of Chapter 10

Documents

kul10SIA2unkris