PHASE II and iii of sdlc

C A R R E R A S X F E R R E R X PAT U N G A N

PHASE II : System
analysis

TRIVIA
&
RECAP

SYSTEM ANALYSIS
Primary purpose: identify user needs and specify
requirements for a new system
Importance: A business problem must be fully
understood by the systems analyst before he or she
can formulate a solution. An incomplete or defective
analysis will lead to an incomplete or defective
solution
Output: Systems Analysis Report

SYSTEM ANALYSIS
Involves two steps:
1. A survey of the current system
2. Analysis of the users needs

PHASE II : System analysis

Survey of the current
system

SYSTEM ANALYSIS The survey step

Disadvantages
Current physical tar pit
Thinking inside the box
Advantages
Identifying what aspects of the old system
should be kept
Forcing systems analysts to fully understand the
system
Isolating the root of problem symptoms

SYSTEM ANALYSIS Gathering facts

The facts fall into the following broad classes:
1. Data sources include external entities, such
as
customers or vendors, as well as
internal sources from other
departments
2. Users include both managers and operations
users
3. Data stores files, databases, accounts, and
source
documents used in the system

SYSTEM ANALYSIS Gathering facts

4. Processes processing tasks are manual or computer
operations
that represent a decision or an action
triggered
by information
5. Data flows represented by the movement of documents and
reports between data sources, data stores, processing
tasks, and users. It can also be represented in UML
diagrams
6. Controls include both accounting and operational controls
and
may be manual procedures or computer controls
7. Transaction volumes the analyst must obtain a measure of
the
transaction volumes for a specified period of
time

SYSTEM ANALYSIS Gathering facts

8. Error rates transaction errors are closely related to
transaction
volume. As a system reaches capacity,
error
rates increase to n intolerable level
9. Resource costs
time, materials
overhead

includes cost of labor, computer

(such as invoices), and direct

10. Bottlenecks and redundant operations can result

in delays
and promote processing errors during
peakload periods. By identifying these problems
during the survey phase, the analyst can avoid
making the same mistakes in the design of the
new system

SYSTEM ANALYSIS Fact-gathering

Techniques
Fact-finding involves answers to
five familiar questions:
Who?
What?
How?

When?
Where?

SYSTEM ANALYSIS Fact-gathering

Techniques
CURRENT SYSTEM

PROPOSED SYSTEM

Who does it?

Why does this person do

it?

Who should do it?

What is done?

Why is it done?

What should be done?

Where is it done?

Why is it done there?

Where should it be done?

When is it done?

Why is it done then?

When should it be done?

How is it done?

Why is it done this way?

How should it be done?

SYSTEM ANALYSIS Fact-gathering

Techniques
Techniques:
1. Observation
2. Task Participation
3. Reviewing Key Documents
4. Personal Interviews

SYSTEM ANALYSIS Fact-gathering

Techniques
Examples of an organizations documents are the
following:

Organizational Charts
Job description
Accounting records
Charts of accounts
Policy statements
Descriptions of procedures
Financial statements

SYSTEM ANALYSIS Fact-gathering

Techniques
Techniques:
1. Observation
2. Task Participation
3. Reviewing Key Documents
4. Personal Interviews

SYSTEM ANALYSIS Fact-gathering

Techniques
Personal Interviews
Step 1 : Determine the People to Interview
Step 2 : Establish Objectives for the Interview
Step 3 : Develop Interview Questions
Step 4 : Prepare for the Interview
Step 5 : Conduct the Interview
Step 6 : Document the Interview
Step 7 : Evaluate the Interview

SYSTEM ANALYSIS Fact-gathering

Techniques
Kinds of Interview Questions:
1. Open-ended Questions
2. Closed-ended Questions
3. Range-of-response Questions
4. Questionnaires

SYSTEM ANALYSIS Fact-gathering

Techniques
Personal Interviews
Step 1 : Determine the People to Interview
Step 2 : Establish Objectives for the Interview
Step 3 : Develop Interview Questions
Step 4 : Prepare for the Interview
Step 5 : Conduct the Interview
Step 6 : Document the Interview
Step 7 : Evaluate the Interview

SYSTEM ANALYSIS Documentation

The basic rule is to write it down.
Record information as soon as you obtain it.
Use the simplest recording method possible.
Record your findings in such a way that the can
be understood by some else.
Organize you documentation so related material
is located easily.

PHASE II : System analysis

Analysis of the users needs

SYSTEM ANALYSIS Users need

Systems Analysis Report
- Its preparation marks the conclusion of the
systems analysis phase
- Presents to management or the steering
committee the survey findings, the problems
identified with the current system, the users needs,
and the requirements for the new system.
- Specifies the objectives and goals of the system

Outline of Main
topics in system
analysis Report

PHASE IIi : Conceptual

Systems Design

Conceptual System Design

Purpose
to produce several alternative conceptual
systems that satisfy the system requirements
identified during systems analysis.
Two Approach
1. Structured Approach
2. Object-oriented Approach

Conceptual System Design Structured Approach

Structured Approach
- a disciplined way of designing systems from the
top
down
- starts with big picture
- business process is documented through data flow
and structured diagrams

Conceptual System Design object-oriented

Object Oriented Approach
- to build information systems from reusable
standard components or objects
- Concept of reusability

Conceptual System Design Auditors Role

Audit features designed to the systems

must be specified at the conceptual stage.

References
Hall, J. (2011). Information Technology Auditing and
Assurance. Cengage Learning.
Lo, P. (2004). Retrieved from http://www.peterlo.com/Teaching/CS211/L03.pdf
Maisen, J. (n.d.). Retrieved from
http://www.jk.rmutl.ac.th/sa/slide_03.pd

Thank You>