1. Systems Planning and Analysis
Chapter 10

2. Describe the relationship of systems analysis to systems
Learning Objective 1
Describe the relationship of
systems analysis to systems
development as a whole.

3. Overview of Systems Planning and Analysis
Systems planning involves identifying
subsystems within the information system.
Systems analysis begins after systems planning
has identified subsystems for development.

4. Overview of Systems Planning and Analysis
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. Overview of Systems Planning and Analysis
Cost Patterns at Varying Development Stages
Cost in
Dollars
Systems
Analysis
Systems
Design
Systems
Implementation

6. Systems Planning and Feasibility Analysis Phases
1. Discussing and planning on
the part of top management
2. Establishing a systems
planning steering committee
3. Establishing overall
objectives and constraints
4. Developing a strategic
information systems plan

7. Systems Planning and Feasibility 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 individuals
for purposes of the analysis and
preliminary systems design

8. Systems Planning and Top Management
Steering Committee:
Developing objectives and system constraints
Developing a strategic systems plan
Identifying individual projects for priority
Commissioning the systems project

9. Learning Objectives 2 and 4
Describe the various stages
of systems analysis.
Describe some of the human
problems involved in
systems analysis.

10. The Steps of Systems Analysis
Survey
current
system
Step 2:
Identify
information
needs
Step 3:
Identify
systems
requirements
Step 4:
Systems
analysis
report

11. Phase I: Survey the Present System
What are the objectives of surveying?
Gain a fundamental understanding of
the operational aspects of the system.
Establish a working relationship with users.
Collect important data.
Identify specific problems.

12. Phase I: Survey the Present System
Communication Gap Problem
Systems Analyst
Job
security
Uncertainty
Resistance
to change
Management

13. Phase I: Survey the Present System
Approaches to Commmunication Gap:
Get to know as many people involved
in the system as soon as possible.
Communicate the benefits
of the proposed system.

14. Phase I: Survey the Present System
Inside
Outside
Sources for gathering facts
Analysis of survey findings

15. Phase II: Identify Information Needs
Information Needs Analysis:
Identify the manager’s 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. Phase III: Identify the Systems Requirements
Inputs
Outputs

17. Phase IV: Develop a Systems 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. Phase IV: Develop a Systems 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. Discuss the major techniques for gathering and organizing
Learning Objective 3
Discuss the major techniques
for gathering and organizing
data for systems analysis.

20. Techniques for Fact Organization
Warnier–Orr Illustration
Due date > = Discount =
Determine today’s date percent ×
discount gross amount
Compute Due date < Discount = 0
total amount today’s date
due for
invoices Amount due =
(n) gross –
discount
Accumulate total
amount due +

21. Techniques for Gathering Facts for Analysis
Depth interview
Structured interview
Open-ended questionnaire
Closed-ended questionnaire
Document reviews
Observation

22. Techniques for Fact Organization
Work measurement
Work distribution
Flow charting
Decision analysis
Functional analysis
Hierarchical function
Matrix analysis
Narratives
File/report summaries

23. Structured Systems Analysis
This is an approach to systems analysis
that begins with a general description
of a particular system.
Logical flow diagrams versus Flowcharts
Systems design versus Systems analysis

24. Steps in Structured Systems Analysis
Develop logical data flow diagrams
Define data dictionaries
Define access methods
Define process logic

25. Purchasing System Context Diagram
Stores
Requisition
Purchase
details
file
Purchasing
system
Vendors
Purchase
order

26. Expansion of Purchasing System Context Diagram
Stores
Requisition
details
Purchase
file
Requisition
Validate
requisition
Purchase
order
Prepare
purchase
order
Details
Vendors

27. Structured English Access purchase file for each purchase requisition.
IF account no. on requisition equals account-no-1
THEN flag account-no-1 field
ELSE IF account no. on requisition equals account-no-2
THEN flag account-no-2 field
ELSE (none of the above)
SO void the transaction and generate error code

28. Learning Objectives 5 and 7
Describe the various steps
involved in specifying
systems design alternatives.
Describe the content of a
systems design proposal.

29. Steps in Systems Design
planning
and analysis
Systems Design
Evaluate
various
designs 1
Prepare
design
specifications 2
Systems
design
specifications 3
Systems
implementation
Systems
review and
control

30. Evaluating Design Alternatives
What are some aspects of systems design?
Enumeration of design alternatives
Describing the alternatives
Evaluating the alternatives
Preparing design specifications

31. Design of System Elements
Reports
and other
outputs
Control
considerations
Database
design
Specify
processing
Type of control
Function of control
Applicable systems component
Specify
inputs

32. Preparing and Submitting Specifications
What should the design proposal include?
Specific timetables for completion
Budget
Description of personnel requirements
Flowcharts
Other diagrams
Business process blue printing

33. considerations relevant
Learning Objective 6
Discuss the various
considerations relevant
to preparing design
specifications.

34. Design Considerations
System Element Design Consideration
Outputs (report or document) Cost effectiveness
Relevance
Clarity
Timeliness
Database Cost effectiveness
Integration
Standardization
Flexibility
Security
Accuracy
Efficiency
Organization

35. Design Considerations
System Element Design Consideration
Data processing Cost effectiveness
Uniformity
Integration
Accuracy
Data input Cost effectiveness
Accuracy
Uniformity
Integration
Controls and security measures Cost effectiveness
Comprehensiveness
Appropriateness

36. Summarize several major
Learning Objective 8
Summarize several major
design techniques.

37. Systems design packages
Design Techniques
Forms design
Database design
Systems design packages

38. Discuss the usefulness of systems design packages.
Learning Objective 9
Discuss the usefulness of
systems design packages.

39. Systems Design Packages
CASE (computer-aided software engineering):
Data flow diagrams
Narrative documentation
Screen and report prototypes
Data dictionary descriptions

40. 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. Choosing Software and Hardware
What is the main disadvantage of
purchased software packages?
They rarely exactly meet a company’s needs.

42. Choosing Software and Hardware
It is usually safe to be content with the
hardware on which that software runs.
It is recommended to get machinery
that is upwardly compatible.

43. “Real” Systems Life Cycle
Wild
enthusiasm
Disillusionment
Total
confusion

44. “Real” Systems Life Cycle
Punishment of
the innocent
Promotion of
nonparticipants
Search for
the guilty

45. Communication Problems in Systems Development
As approved
by the steering
committee
As proposed
by the user
manager
As structured
by the data
administrator

46. Communication Problems in Systems Development
As implemented
by the application
programmers
What the user
actually
wanted
As designed
by the lead
analyst

47. End of Chapter 10