Biznesa procesu un datu plusmas diagrammas (turpinajums)

1
Biznesa procesu un datu plusmas diagrammas
(turpinajums)
2
Information Systems and Business Processes
Business process
Information system
Workflow system
B.Wangle/ 1/15/2016
3
The Drain Pipe Syndrom
Business Process
IS-5
IS-4
IS-3
IS-2
IS-1
Specific systems for each business
function. Little integration.
B.Wangle/ 1/15/2016
4
Leveled diagram
Janis Tenteris
Context
0 Top
1
2
5
Context level diagram
Kendall, Kendall, 1995, P 234
6
Kendall, Kendall, 1995, P 234
External Entity 1
Input A
System Name
External Entity 3
Output C
External Entity 2
Input B
Context level diagram
Top or 0 level diagram
7
Developing DFDUsing Top-Down Approach
Kendall, Kendall, 1995, P 233

• Make a list of business activities and use it to
  determine various
• External Entities
• Data Flows
• Processes
• Data Stores
• Create a context diagram which shows external
  entities and data flows to and from the system.
  Do not show any detailed processes or data stores
• Draw diagram 0, the next level. Show processes,
  but keep them general. Show data stores at this
  level
• Create a child diagram for each of the processes
  in Diagram 0
• Check for errors and make sure the labels you
  assign to each process and data flow are
  meaningful
• Develop a physical data flow diagram from the
  logical data flow diagram. Distinguish between
  manual and automated processes, describe actual
  files and reports by name, and add controls to
  indicate when processes are complete or errors
  occur
• Partition the physical data flow diagram by
  separating or grouping parts of the diagram in
  order to facilitate programming and implementation

8
Free choice of the starting point and working
forward/backward from the point
Kendall, Kendall, 1995, P 234

• Start with the data flow from an external entity
  on the input side, ask questions such as
• What happens to the data entering the system?
• Is it stored?
• Is it input to several processes
• Work backwards from an output data flow. Examine
  the output fields. For each field on the output
  ask
• Where does it come from?
• Is it calculated or stored on a file?
• Examine the data flow to or from a data store.
  Ask
• What processes put data into the store
• What processes use the data (Note, that data
  store may be produced by a different system -
  there may not be any data flow into the data
  store)
• Analyse a well defined process. Look at what
  input data the process needs and what output
  produces, Then connect the input and output to
  the appropriate data stores and external entities
• Take note of any fuzzy areas where you are unsure
  of what should be included, or what input or
  output is required. Awareness of problem areas
  will help to formulate a list of questions for
  follow-up interviews with key users

9
Logical checklist for DFD
1. Have you got a process behaving as a sink or
source (external entity) ?
WRONG!!
Customer name range
RIGHT
Customers
10
Logical checklist for DFD
2. For a given process, have you got enough (or
too many) inputs to produce the stated output?
WRONG !!
RIGHT
Delivery Schedule
11
WRONG !!
All data flows must either originate or terminate
at a process
12
Business level DFD and DFD for database
BM
ISM
MK, 96
13
BM
MK, 96
14
ISM
MK, 96
15
Types of data flow diagrams

• Physical
• includes details HOW the system works by physical
  items and physical processes
• state the person performing the processing
• Logical
• contains only details of WHAT is achieved with no
  reference to anything physical

16
Convertion to logical DFD
Addapted from I.T. Hawryckiewycz Introduction to
Systems Analysis and Design, Prentice Hall, 1991

• remove all the processes that refer to physical
  activities and do not transform information
• expand the remaining processes to the logical
  functions
• take each process
• find out what it does
• replace by a leveled DFD of logical functions
• combine expansions into a lower level logical DFD
• combine any similar or common functions and
  represent the combinations as processes in higher
  level logical DFD

17
Top-level physical DFD
Addapted from I.T. Hawryckiewycz Introduction to
Systems Analysis and Design, Prentice Hall, 1991
2 Sort into areas
Stored orders
Checked order
Unaccepted order
Customers
1 Reception (clerk)
3 Send to production section
Order
Unable to meet deadline
4 Production
Dispatched orders
18
Addapted from I.T. Hawryckiewycz Introduction to
Systems Analysis and Design, Prentice Hall, 1991
Expanded processes
Unaccepted order
Unable to meet deadline
Received order
Checked order
Customers
1.1 Record order
1.2 Check type of order
Order
4.1 Check available resources
Accepted order
ORDERS
4.2 Commit resources to production
RESOURCES - SCHEDULES
19
Addapted from I.T. Hawryckiewycz Introduction to
Systems Analysis and Design, Prentice Hall, 1991
Recombined logical processes
Replay to order
Received order
Accepted order
Customers
1 Record order
2 Check production feasibility
3 Commit resources to production
Order
ORDERS
20
Features of logical and physical DFD
Kendall, Kendall, 1995, P 241
21
Contents of Physical Data Flow Diagrams
Kendall, Kendall, 1995, P 244

• Manual processes
• Processes for adding, deleting, changing, and
  updating processes
• Data entry and verifying processes
• Validation processes for ensuring accurate data
  input
• Sequencing processes to rearrange the order of
  records
• Processes to produce every unique system output
• Immediate data stores
• Actual file names used to store data
• Controls to signify completition of tasks or
  error conditions

22
Current System
DFD may describe the current system as well as
the proposed one
Proposed System
23
Business process diagrams (BPD) and DFD
BPD
Ir lidziga
24
Business process diagrams (BPD) and DFD

• Datu plusmas diagramma tiek zimeta augstaka
  abstrakcijas limeni neka biznesa procesa
  diagramma
• Salidzinajuma ar BPD, datu plusmas diagramma
  neattelo
• Procesa izpilditaju
• Trigera nosacijumus
• Zarošanas nosacijumu saturu
• Biznesa procesa diagramma avoti un izlietnes var
  but procesi datu plusmu diagrammas tie parasti
  ir objekti
• Galvenais, kas japarada datu plusmas diagramma
  ka dati plust caur procesiem
• Galvenais, kas japarada biznesa procesa diagramma
  ar kadiem panemieniem (piemeram, darbibu
  secibu) dotaja konteksta tiek sasniegts biznesa
  procesa merkis

25
BPD fragments
DPD fragments
Answer
Applicant
Application Form
Deliver and Register Application
Registered Application Form
Discuss in Membership Committee
Approved Application
Decision
n
Send answer
26
BPD fragments
DPD fragments
Answer
Applicant
Application Form
Deliver and Register Application
Trigera nosacijums
Registered Application Form
Discuss in Membership Committee
Approved Application
Decision
n
Send answer
Ja šie procesi butu dažadi, tad DPD butu divi
nevis viens process