Application of the Principles of

Systems Analysis and Design

Proud to be RTUian
Review of the Phases of SDLC

Proud to be RTUian
Systems Analysis

- the detailed investigation of business or

information systems.
- it is the scientific study of the systems
process, including investigation of inputs
and outputs, in order to find better,
economical, and more efficient means of
processing.

Proud to be RTUian
The Systems Development Life Cycle

Planning Phase
- the analyst recognize, diagnose and
define the problem.

Analysis Phase
- the analyst reviews the in-place systems.

Proud to be RTUian
The Systems Development Life Cycle

Design Phase
- the analyst puts down on paper the
elements of a new or improved system.

Development Phase
- the new system is actually built.

Proud to be RTUian
The Systems Development Life Cycle

Implementation Phase
- changeover to the new or improved
system.

For each phase of the SDLC, there is one or more

deliverable called work product or work output.
- It is a finite, measurable amount of work also
known as milestones that mark the completion of
a phase.
Proud to be RTUian
Design Guidelines
Modular structure following the top-down
approach
- develop systems in segments, dividing
the task into smaller more manageable
parts.
- for example, the AIS can be
developed in modules based on the
transaction processing cycles.

Proud to be RTUian
Design Guidelines

Modular Structure: Accounting Information Systems

Expenditure Revenue Conversion GL
Cycle Cycle Cycle Cycle

These self-contained modules should call

in others to eliminate redundant efforts.

Proud to be RTUian
Design Guidelines

Top-down approach: Accounting Information Systems

Expenditure Revenue Conversion GL
Cycle Cycle Cycle Cycle

Sales A/R
Cycle Cycle

Proud to be RTUian
Modular Approach
Transaction Processing Cycles

➢Expenditure Cycle
➢Revenue Cycle
➢Conversion Cycle
➢General Ledger and Financial Reporting Cycle

Proud to be RTUian
Project Deliverables

Proud to be RTUian
Preliminary Planning and Investigation

Deliverable:
- The Project Plan or The Project Charter
> problem definition
- statement of the problem or
objectives general and specific
- scope
- recommendation to:
> proceed, defer, discontinue

Proud to be RTUian
Preliminary Planning and Investigation

Scope
- Logical scope
> defines what is included in the
project; ‘where’ it starts and ‘where’ it ends
- Temporal scope
> time line; ‘when’ it starts and
‘when’ it ends
> use Gantt Chart
Proud to be RTUian
Preliminary Planning and Investigation

Scope
- Organizational scope
> the structure of the project team
> the structure of the end-users

Proud to be RTUian
Preliminary Planning and Investigation

Scope
- Financial scope
> cost-benefit analysis
- cost pertain to all the
expenses incurred during the SDLC , e.g.,
salaries of project team, installation of
equipment, etc.; this should be quantified

Proud to be RTUian
Summary of Deliverables: Planning Phase
I Planning Phase
A. Statement of the Objective
1. Specific objective
2. Specific objective
B. Scope
1. Logical scope
2. Temporal scope
3. Organizational scope
4. Financial scope Accounting Information Systems
The Analysis Phase

Proud to be RTUian
Analysis Phase

- Review and detailed investigation of the

system to understand what is needed and
what needs to be improved
> assess information and data
requirements
> conducting work samples, time studies,
and interviews
> analyzing documents
Proud to be RTUian
Analysis Phase

Deliverables
- Systems requirements
> Hardware / software

> End-user requirements

Proud to be RTUian
Data Cycle

OUTPUT

PROCESS
INFORMATION
RAW
DATA REPORT

Proud to be RTUian
Data Cycle
Master Files
Transaction Files OUTPUT
(Database)
PROCESS
INFORMATION
RAW
DATA REPORT

Proud to be RTUian
Data Cycle: Output as Input
Volume of planned production (from
strategic plan)
X Standard raw material usage (from
standard costing)
= Raw materials required for planned
production
- Raw materials inventory balance
(from inventory management)
- List of pending orders
= Raw materials to be purchased > >
Data Cycle: Output as Input
➢Purchase Order
➢ Receiving Report
➢ Supplier’s Invoice (from vendor)
➢ Payment Processing

Records updated (SL/GL):

Inventory, Accounts Payable, List of
Pending Orders
Cash Balance
Deliverables specific to the project:
End-user requirements

Output* Input**
- Name of output - Name of input
- Purpose - Source
- User > who prepares?
- Output media (soft or > where prepared?
hardcopy)
- Frequency of output - What is the input
medium?
* Should contribute to the ** What is needed to produce
achievement of the the output
objectives.
Deliverables specific to the project:
End-user requirements

Needed to produce the

Master Files
output

- Name of File
- Used for ?
Deliverables specific to the project:
End-user requirements
Output* Input**
- Name of output - Name of input
- Purpose - Source
- User > who prepares?
- Output media (soft or > where prepared?
hardcopy)
- Frequency of output - What is the input medium?

Master Files
- Name of File
- Used for ?
The Design Phase

Proud to be RTUian
Design Phase

System design
- the reduction of a plan or concept to a
set of specifications that describes a new or
modified system
Design Phase
Deliverables
- Final Design*
> in conformity with the result of the
analysis phase and the applicable policies
- procedures, methods,
input/output forms, hardware/software
evaluation
*For purposes of the project, the requirements are
only prototypes of the input and output forms, and
the content of the master and transaction files
Proud to be RTUian
PROTOYPES
Deliverables specific to the project:

- Name of File
- Content presented in columnar form
- Example:

RAW MATERIALS MASTER FILE

Item No. Description Unit of Measure
The Development Phase

Proud to be RTUian
Systems Development
- the stage during which the system is
actually built based upon the designs
conceived in the earlier phases.
- heavy support is required from IT or IS
Department (Computer /Systems
Engineer, Programmers) for the technical
requirements or specifications.

Proud to be RTUian
Systems Development
Deliverables
- the system, ready for implementation, i.e.,
> completed policies and
procedures,
> finalized software whether user-
written or application package,
> hardware is available,
> all tests are completed with the test
results approved and accepted by the users
> personnel who are well-trained to
use the system.
Proud to be RTUian
Deliverables
For purposes of the project, only
the following are required:
➢Relevant policies that govern the
systems
➢Procedures using context diagrams
with at least one level of
decomposition.
Proud to be RTUian
Context Diagram
- shows the entire system as
one general element.
- overall view where all sources
and sinks are linked to one entity
using flowlines or pipes.
- limited or no details
Proud to be RTUian
Decomposed or exploded diagram

- drawn to refine or show more

details, or expand individual
elements
- the first level of explosion is an
entity taken from the context
diagram.

Proud to be RTUian
Context Diagram

Order
Customer 0
__________
Order Bill request
Billing
Processing
Dept.
Ship request System
Shipping
Dept.
Ship confirm
 0
__________
Order
Processing
System

1.1 1.2 1.3 1.4 1.5

Verify Check Process Pick Ship

Pick List
Stock Customer Billing Order Order
Credit

Invoice
Customer
Order Delivery Receipt
The Implementation Phase

Proud to be RTUian
- The planned and orderly
conversion from an existing
system to a new one.
- Involves fine-tuning
elements in order to
maximize efficiency.

Proud to be RTUian
Project Deliverable
1. Soft-copy 0f the completed project
containing all the required work-
outputs or deliverables for each phase
in a formal report format.
➢ Size and background color: A4,
White
➢ Font: Calibri (Body)
➢ Text size: 12
➢ Submit using Word Document
2. 15 minutes PPT presentation
Project Presentation
What to present:
1. Planning Phase:
➢ Statement of the objectives:
• General objective
- Specific objectives
➢ Logical scope
Project Presentation
What to present:
2. Analysis Phase
➢The description of the outputs (reports /
information) and the required inputs.
Limit to two outputs but include all the
needed inputs to produce the output.
➢The description of the master files (limit
to two)
▪ Name of File
▪ Used for ?
Project Presentation
What to present:
3. Design Phase
➢prototypes of the input and
output forms presented in the
Analysis Phase
➢ and the design of the master
files presented in the Analysis
Phase
PROTOYPES
Deliverables specific to the project:

- Name of File
- Content presented in columnar form
- Example:

RAW MATERIALS MASTER FILE

Item No. Description Unit of Measure
Project Presentation
What to present:
4. Development Phase
➢Relevant policies that govern
the systems. Limit to 3 policies.
➢Procedures: Present only one
context diagram with at least
one level of decomposition.