0% found this document useful (0 votes)
99 views45 pages

AIS Chapter 3

System development involves three phases: system analysis, system design, and system implementation. During system analysis, facts and data are collected through methods like interviews, questionnaires, and observations. In the system design phase, a blueprint is created with input/output analysis and tools like flowcharts. Finally, during system implementation the design plan is carried out and documentation techniques are selected. Common documentation tools include data flow diagrams, which show logical data flows, and flowcharts, which depict physical data flows and processes using standard symbols.

Uploaded by

Ashenafi Zeleke
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
99 views45 pages

AIS Chapter 3

System development involves three phases: system analysis, system design, and system implementation. During system analysis, facts and data are collected through methods like interviews, questionnaires, and observations. In the system design phase, a blueprint is created with input/output analysis and tools like flowcharts. Finally, during system implementation the design plan is carried out and documentation techniques are selected. Common documentation tools include data flow diagrams, which show logical data flows, and flowcharts, which depict physical data flows and processes using standard symbols.

Uploaded by

Ashenafi Zeleke
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 45

Chapter three

System development and


Documentation techniques
Introduction to system development

 System development has three phases:


1. System Analysis
2. System design
3. System implementation
1. System analysis
 Much of system analysis job involves
collecting and organizing facts or data
 On data collection we may use:
 Interview
 Questioner
 Observation
 Matric of the above
2. System design
 A blueprint must be formulated for the
complete system.
 The design should include Input/output
(matrix) analysis
 The design may shows:
A. Systems flowcharting
B. Data flow diagrams
3. System implementation

 Systems implementation involves the actual


carrying out of the design plan.
 What systems techniques serve as a
documentation tool should be decided on
this stage.
Why Accountants learn about Documentation
techniques
 The major purposes are:
 At a minimum, they have to read documentation
to understand how a system works.
 They may need to evaluate the strengths and
weaknesses of an entity’s internal controls. E.g.
auditors
 They may Organize very complicated systems
into a form that can be more readily understood
Cont’d

 They may involve on helping new team


members understand a pre-existing
system
 They may prepare documentation for
different purpose.
 So that, Accountants should know about
documentation techniques.
Documentation techniques
Documentation includes the following types
of tools:
 Narratives (written descriptions)
 Flowcharts
 Diagrams
 Other written material
Documentation techniques
Documentation covers who, what,
when, where, why, and how of:
 Data entry
 Processing
 Storage
 Information output
 System controls
Documentation techniques
 There are two of the most common
documentation tools:
1. Data flow diagrams: Focus on logical or
conceptual flow of data.
• Graphical descriptions of the sources and
destinations of data. They show:
 Where data comes from
 How it flows
 The processes performed on it
 Where it goes
Documentation techniques
There are two of the most common documentation
tools:
 Data flow diagrams
 Flowcharts: Focus on physical or actual flow
of data
 Include three types:
 Document flowcharts describe the flow of documents and
information between departments or units.
 System flowcharts describe the relationship between inputs,
processing, and outputs for a system.
 Program flowcharts describe the sequence of logical operations
performed in a computer program.
DATA FLOW DIAGRAMS
The data flow diagram focuses on the
logical flow of data.
A data flow diagram (DFD) graphically
describes the flow of data within an
organization. It is used to:
 Document existing systems
 Plan and design new systems
DATA FLOW DIAGRAMS
• Example of a data flow
diagram of the Accounts
customer payment Receivable
process

Customer 1.0 Remittance 2.0 Receivables


Customer payment Process data Update Information Credit
Payment A/R Manager

Deposit

Bank
DATA FLOW DIAGRAMS
• A data flow diagram consists of four basic
elements:
 Data sources and destinations
 Data flows
 Transformation processes
 Data stores
DATA FLOW DIAGRAMS
• A data flow diagram consists of four basic
elements:
 Data sources and destinations
– Data flows
– Transformation processes
– Data stores
DATA FLOW DIAGRAMS
 Data sources and destinations
Appear as squares
Represent organizations or individuals that send or
receive data used or produced by the system
 An item can be both a source and a destination
DATA FLOW DIAGRAMS
• Data sources and destinations
are marked in red.
Accounts
• Can you tell which are sources Receivable
and which are destinations?

Customer 1.0 Remittance 2.0 Receivables


Customer payment Process data Update Information Credit
Payment A/R Manager

Deposit

Bank
DATA FLOW DIAGRAMS
• A data flow diagram consists of four basic
elements:
 Data sources and destinations
 Data flows
 Transformation processes
 Data stores
DATA FLOW DIAGRAMS
• Data flows
Appear as arrows
Represent the flow of data between sources
and destinations, processes, and data stores
DATA FLOW DIAGRAMS
• Data flows are shown in red.
• Does it appear that a data
Accounts
flow can be two-way?
Receivable
• If so, how is it handled?

Customer Remittance Receivables


1.0 2.0
Customer payment data Information Credit
Process Update
Payment A/R Manager

Deposit

Bank
DATA FLOW DIAGRAMS
 As you probably see from the previous slides, if a
data flow is two-way, use a bi-directional arrow.

Update
General
Receiv-
Ledger
ables
DATA FLOW DIAGRAMS
 If two data elements flow together, then the
use of one data flow line is appropriate.

Cash Rec’t & Remittance Slip


Process
Customer
Payment
DATA FLOW DIAGRAMS
If the data elements do not always flow
together, then multiple lines will be needed.

Customer Inquiry Process


Customer Payment
Customer Payment
DATA FLOW DIAGRAMS
 A data flow diagram consists of four basic
elements:
 Data sources and destinations
 Data flows
 Transformation processes
 Data stores
DATA FLOW DIAGRAMS
• Processes
Appear as circles
Represent the transformation of data
DATA FLOW DIAGRAMS
• The transformation
processes are shown in red.
• Every process must have at Accounts
Receivable
least one data inflow and at
least one data outflow.
Customer 1.0 Remittance 2.0 Receivables
Customer payment Process data Update Information Credit
Payment A/R Manager

Deposit

Bank
DATA FLOW DIAGRAMS
Data stores
 Appear as two horizontal lines
 Represent a temporary or permanent
repository of data
DATA FLOW DIAGRAMS
• The data store is shown in
red.
• Notice that the inflows and Accounts
Receivable
outflows to the data store
are not labeled.

Customer 1.0 Remittance 2.0 Receivables


Customer payment Process data Update Information Credit
Payment A/R Manager

Deposit

Bank
DATA FLOW DIAGRAMS
The data flow diagram focuses on the
logical flow of data.
Next, we will discuss flowcharts, which
place greater emphasis on physical
details.
FLOW CHARTS
 A flowchart is an analytical technique that
describes some aspect of an information system
in a clear, concise, and logical manner.
 Flowcharts use a set of standard symbols to
depict processing procedures and the flow of
data.
 Flow charts can be:
A. Documentation flow chart
B. System flow chart
C. Program flow chart
A. DOCUMENT FLOWCHARTS
 A document flowchart shows the flow of documents and
information among areas of responsibility in an
organization.

 These flowcharts shows:


 Where a document comes from
 Where it’s distributed
 How it’s used
 It’s ultimate disposition
 Everything that happens as it flows through the
system
DOCUMENT FLOWCHARTS
E.G. Internal control flowcharts are document
flowcharts used to evaluate the adequacy of internal
controls, such as segregation of duties or internal
checks.
 They can reveal weaknesses or inefficiencies such as:
 Inadequate communication flows
 Unnecessarily complex document flows
 Procedures that cause wasteful delays
FLOWCHARTS VS. DFDs

 Now that we’ve examined both flowcharts and


DFDs, it may be useful to discuss the
differences again.
 DFDs place a heavy emphasis on the logical
aspects of a system.
 Flowcharts place more emphasis on the
physical characteristics of the system.
 An example may be useful.
FLOWCHARTS VS. DFDs

EXAMPLE: The registrar’s office of a small


college receives paper enrollment forms from
students. They sort these records alphabetically
and then update the student record file to show
the new classes. They also prepare class lists
from the same data. The sorted enrollment
forms are forwarded to the administrative
office for billing purposes. Class lists are
mailed to faculty members.
Here’s a
Students DFD that
Enrollment
goes with
Forms
the story.
1.0
Update Student
Student Records
Records
Enrollment
Forms

2.0
Prepare Administrators
Enrollment
Class Lists Forms

Class
Lists

Faculty
Registrar’s Office

Students Enrollment Sort


Students
Forms Forms
Enrollment
Forms

1.0 Update Sorted


A
Update Student Student Enrollment
Student Records Records Forms
Records
Enrollment
Forms
Sorted Prepare
Enrollment Class
Forms Lists
2.0
Prepare Enrollment
Administrators Here’s a
Class Lists Forms
flowchar Class Sorted
Class t that Lists Enrollment
Lists Forms
goes
Faculty with the Administrators
story Faculty
FLOWCHARTS VS. DFDs

Now let’s change the story so that


students enter enrollment data online.
The registrar’s office sends a tape
file(soft copy) of the enrollment data to
the administrative office and continues
to send paper class lists to faculty.
Original DFD Here’s the
revised DFD.
Students Students
How has it
Enrollment Enrollment changed?
Forms Data

1.0 1.0
Update Student Update Student
Student Records Student Records
Records Records
Enrollment Enrollment
Forms Data

2.0 2.0
Prepare Administrators Prepare Administrators
Enrollment Enrollment
Class Lists Forms Class Lists Data

Class Class
Lists Lists

Faculty Faculty
Registrar’s Office Registrar’s Office

Enrollment Sort Enrollment


Students Forms Student
Forms Data
s

Update Sorted Update


A Enrollment
Student Enrollment Student
Data
Records Forms Records

Sorted Prepare
Enrollment Class Administrator Prepare
Forms Lists Student Class
Records Lists
Sorted
Class
Lists
Enrollment
Forms
Here’s the revised Class
Lists
flowchart. How
Faculty Administers has it changed?
Faculty
Original
Flowchart
FLOWCHARTS VS. DFDs

 Changes in the physical characteristics of the


process do affect the flowchart but have
little or no impact on the DFD.
 The major reason is, the DFD focuses more on
the logic view and FC focuses on physical
view
 When deciding which tool to employ, consider
the information needs of those who will view
it.
B. SYSTEM FLOWCHARTS

 A system flowchart depicts the relationship


among the inputs, processes, and outputs of an
AIS.
 The system flowchart begins by identifying
the inputs to the system.
 These inputs can be:
 New data
 Data stored for future use
 Both
SYSTEM FLOWCHARTS

 Each input is followed by a process, i.e., the


steps performed on the data.

 If the process is performed by a


computer, the computer program
would be depicted in a program
flowchart.
SYSTEM FLOWCHARTS

 The process is followed by outputs: the


resulting new information.
 The output may be:
 Stored for later use
 Displayed on a screen
 Printed on paper
 An input to the next process
PROGRAM FLOWCHARTS

 Program flowcharts illustrate the sequence of


operations performed by a computer in
executing a program.
 They also follow an input – process – output
pattern.
 This is more specific than system flow chart.
End chapter 3

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy