Documente Academic
Documente Profesional
Documente Cultură
Plan
Introduction
Structured Methods
Data Flow Modelling
Data Modelling
Relational Data Analysis
Feasibility
Maintenance
Plan
Introduction
Structured Methods
Data Flow Modelling
Data Modelling
Relational Data Analysis
Feasibility
Maintenance
A communication tool
Should be clear and unambiguous
An analysis tool
Should help us to understand systems
A design tool
Should help us to develop and improve systems
Analysis
Analysis of Current System and Requirements
Design
Used as source for design of new system
Convert to
Logical View
New Logical
System DFD
Repository
Repository
Existing
System ERD
New System
ERD
Technical
Options +
Constraints
New Physical
System
Example 2 DeMarco/Yourdon
Example 3 - SSADM
Bottom up
More likely to be done in practice
Interviews provide localised detail not context
A precursor to DFDs
A good way of establishing the context
Identify the entities in the system (departments)
Identify documents flowing between them
Establish system boundary
DocFD Elements
Entity (also called Agencies)
Symbol
a
customer
Duplicate symbol
a
customer
DocFD Elements
Document Flow
Sales Order
booking+deposit
payment
confirmation
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+deposit
payment
confirmation
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+deposit
payment
confirmation
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+depos
it
confirmation
weekly
statement
final statement
payment
b
booking
dept
deposit
vouchers
d
bar/restaura
nt
weekly
statement
(copy)
c
accounts
dept
Document Definitions
It is important at this stage to identify the
information in the documents that flow
across the system boundary
These will inform us of the interface
between the system and external entities
Data Interface and possibly GUI
(Mason and
Wilcocks,
1994)
booking+deposit
payment
confirmation
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+deposit
payment
confirmation
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+deposit
confirmation
payment
weekly statement
b
booking
dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
booking+deposit
confirmation
weekly statement
CD Hotel
Bookings
b
booking dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
Elements of a DFD
Process Box
Symbol
Indicates Process at
lowest level of detail
2 Accounts
Sales Assistant
Dept
1
Maintain Sales
Create
Account
Reservation
*
Active Component
What goes in must come out or be transformed
Physical or Logical?
Elements of a DFD
Data Flow
Sales Order
Elements of a DFD
Data Store
Symbol
M1
Sales File
M1
Sales File
Duplicate
Passive Component
Does not process data
Manual or Digital (M/D)
Elements of a DFD
External Entity
also called Agencies, source and sink
Symbol
a
customer
Duplicate symbol
a
customer
Example - SSADM
booking+deposit
confirmation
weekly statement
CD Hotel
Bookings
b
booking dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
Identifying Processes
High Level Processes
can often be identified
as business functions
Accounts
Sales
Purchasing
Lower level
Processes will be
implied by verbs such
as
Create
Sort
Compile
Change
booking+deposit
confirmation
weekly statement
CD Hotel
Bookings
b
booking dept
final statement
deposit
vouchers
d
bar/restaura
nt
weekly statement
(copy)
c
accounts
dept
a
guest
b
accounts
dept
CD Hotel Bookings
Reception
Create Booking
File
Catalogue
Tray
Folder
Database
..or implied
Check against
Put into
Read
a
guest
b
accounts
dept
CD Hotel Bookings
Reception
Create Booking
CD Hotel Bookings
M1 Vacancy List
a
customer
Reception
Create Booking
M2 Reservation file
M3 Guest account
b
accounts
dept
But Never:
Between data Stores
From an entity to a data store
CD Hotel Bookings
M1 Vacancy List
a
customer
Reception
Create Booking
M2 Reservation file
M3 Guest account
b
accounts
dept
CD Hotel Bookings
booking+depo
sit
a
customer
confirmation
room details
Reception
Create Booking
deposit
deposit
guest details
b
accounts
dept
M1 Vacancy List
M2 Reservation file
M3 Guest account
Errors
Do not join data stores to data stores
Do not join data stores to entities
Any change in data implies a process so
add one
If data comes out of a process it must
have got in somehow
Do not give any impression of time
Do not show triggers (e.g. start)
Guidelines
Draw one to throw away youll never get
it right first time
Identifying the entity that starts the system
process can help
Develop one process at a time
A process is always on
Read Lejk and Deeks from cover to cover
Plan
Introduction
Structured Methods
Data Flow Modelling
Data Modelling
Relational Data Analysis
Feasibility
Maintenance
References
Whiteley, D. (2004) Introduction to
Information Systems, Palgrave, 2004.
Lejk, M. and D. Deeks (2002) Systems
Analysis Techniques, Addison Wesley
2002
Mason, D. and L. Willcocks (1994),
Systems Analysis, Systems Design, Alfred
Waller, 1994.
References
Yeates, D. and T. Wakefield (2004)
Systems Analysis and Design, FT/Prentice
Hall 2004
Gane, C. and T. Sarson (1979) Structured
Systems Analysis, Prentice Hall, 1979
Eva, M (1994) SSADM Version 4: A users
guide, McGraw hill, 1994
References
DeMarco, T. (1979) Structured Analysis
and System Specification, Yourdon, 1979
Royce, W. (1970) Managing the
development of large software systems,
In: Proceedings of IEEE WESCON, 1970
pp1-9.