1

Pertemuan 12Implementasi SIM & Process Modelling

Matakuliah : M0084/Sistem Informasi dalam Manajemen

Tahun : 2005

Versi : 1/1

2

Learning Outcomes

Pada akhir pertemuan ini, diharapkan mahasiswa

akan mampu :

• Mahasiswa dapat Menghasilkan model simulasi dalam SIM (C3)

3

Outline Materi

• SIM dan Pertimbangan Manusia

• SIM dan Pemecahan Masalah

• Process Modeling - Data Flow diagram

Which Graphs to UseWhich Graphs to Use Line or bar charts are best to summarize dataLine or bar charts are best to summarize data Grouped line or bar charts show trends over Grouped line or bar charts show trends over

timetime Grouped bar charts are better for representing Grouped bar charts are better for representing

parts of a wholeparts of a whole Compare variables using horizontal, not Compare variables using horizontal, not

vertical, barsvertical, bars Use single line or bar charts to compare data Use single line or bar charts to compare data

pointspoints

12-4

0

10

20

30

40

50

60

70

80

90

1980 1981 1982 1983 1984

Apples Oranges Peanuts

0

10

20

30

40

50

60

70

80

90

100

1980 1981 1982 1983 1984

Apples

Oranges

Peanuts

Years

(c)

Years

(a)

GROUPED/MULTIPLE GROUPED/MULTIPLE LINE CHARTLINE CHART

GROUPED BAR GROUPED BAR CHARTCHART Sales RevenueSales Revenue

12-5

Segmented Line ChartSegmented Line Chart

0

50

100

150

200

1980 1981 1982 1983 1984

Years (b) Legend:

ApplesOrangesPeanuts

Dol

lars

in M

illi

ons

12-6

Segmented/Divided Bar ChartSegmented/Divided Bar Chart

0

50

100

150

200

Sales Revenue

1980 1981 1982 1983 1984

Years (d)

Dol

lars

in M

illi

ons

Legend:ApplesOrangesPeanuts

12-7

Human Factors Human Factors ConsiderationConsideration

Behavioral influences can affect employees Behavioral influences can affect employees in their computer-related tasksin their computer-related tasks

FearFear– Replacement of people by computersReplacement of people by computers– Computer systems tailored to organizations, not Computer systems tailored to organizations, not

individualsindividuals– Managers and line workers are affectedManagers and line workers are affected

12-8

Minimizing FearMinimizing Fear

Use computer as a means of achieving job Use computer as a means of achieving job enhancementenhancement

Use formal communications to keep Use formal communications to keep employees aware of firm’s intentionsemployees aware of firm’s intentions

Build a relationship of trust with employeesBuild a relationship of trust with employees Align employees’ needs with firm’s Align employees’ needs with firm’s

objectivesobjectives

12-9

Putting the MIS in Putting the MIS in PerspectivePerspective

The first attempt to make information The first attempt to make information available to available to managementmanagement

Enjoyed its greatest prominence in the Enjoyed its greatest prominence in the 1960s when it first originated1960s when it first originated

Now integrated throughout the firmNow integrated throughout the firm

12-10

MIS and Problem SolvingMIS and Problem Solving

Organizationwide information resourcesOrganizationwide information resources– Provides problems solving informationProvides problems solving information– Sets stage for accomplishment in other areas such as DSS, the Sets stage for accomplishment in other areas such as DSS, the

virtual office, and knowledge-basedvirtual office, and knowledge-based

Problem identification and understandingProblem identification and understanding– Main idea is to keep information flowing to the managerMain idea is to keep information flowing to the manager– Manager uses MIS to signal impending problemsManager uses MIS to signal impending problems

Main weakness is that it is not aimed at individual Main weakness is that it is not aimed at individual problem solversproblem solvers

12-11

Process ModelingProcess Modeling

MANAGEMENT INFORMATION SYSTEMS 8/ERaymond McLeod, Jr. and George Schell

Copyright 2001 Prentice-Hall, Inc.B-12

Data Flow Diagrams Data Flow Diagrams (DFDs)(DFDs)

Graphic representation of a system that uses Graphic representation of a system that uses a small number of symbol shapes to a small number of symbol shapes to illustrate how data flows through illustrate how data flows through interconnected processes interconnected processes – Most natural way to document processesMost natural way to document processes– Emphasis on processes rather than dataEmphasis on processes rather than data

B-13

DFD SymbolsDFD Symbols

DFDs consist of four symbolsDFDs consist of four symbols1) Environmental elements called 1) Environmental elements called terminatorsterminators

» PersonPerson

» OrganizationOrganization

» Another systemAnother system

2) 2) ProcessesProcesses which transform inputs to outputs which transform inputs to outputs» Labeled with verb and objectLabeled with verb and object

» Also labeled with system or computer program Also labeled with system or computer program namename

B-14

DFD Symbols [cont.]DFD Symbols [cont.]

DFD symbols [cont.]DFD symbols [cont.]– Data flowsData flows which consist of logically related which consist of logically related

data elements that travel from one point or data elements that travel from one point or process to another. In other words, data in process to another. In other words, data in motion.motion.

» StructuresStructures

» DivergeDiverge

» ConvergeConverge

B-15

DFD Symbols [cont.]DFD Symbols [cont.]

DFD symbols [cont.]DFD symbols [cont.]– Data storesData stores which are data repositories. In which are data repositories. In

other words, data at rest.other words, data at rest.

B-16

CustomerMail

Salesorders

Enteredsales orders

Enteredsales orderdata

Sortedsales records

Sales commissionreport Sales

manager

Sales orderform file

1.Open mail

2.Enter salesorder data

3.Sort

sales order s

4.Compute

salescommissions

A Data Flow Diagram (Figure 0 Diagram) of a Sales Commission System

B-17

When Drawing a Context When Drawing a Context DiagramDiagram

1. Use only a single process symbol1. Use only a single process symbol

2. Label the process symbol to represent the 2. Label the process symbol to represent the entire systementire system

3. Do not number the single process symbol3. Do not number the single process symbol

4. Include all terminators for the system4. Include all terminators for the system

5. Show all the data flows between the 5. Show all the data flows between the terminators and the systemterminators and the system

B-18

Sales Commission

System

Customer

Sales Manager

Sales commission report

Mail A Context Diagram of a Sales Commission System

B-19

Figure Figure nn Diagrams Diagrams

Documents a single process of a DFD in a Documents a single process of a DFD in a greater amount of detailgreater amount of detail

nn represents the number of the process on represents the number of the process on the next higher level that is being the next higher level that is being documenteddocumented

The term “leveled DFDs” describe the The term “leveled DFDs” describe the hierarchy of diagrams ranging from context hierarchy of diagrams ranging from context to the lowest-level figure n diagram to the lowest-level figure n diagram

B-20

Figure 4 Diagram of a Sales Commission System

3

4.1Compute

commissionamounts

4.2Accumulatetotals

Salesmanager

Sortedsales

records

Commissionamounts

Salescommission

report

B-21

How Many Levels to Use?How Many Levels to Use?

Restrict a single DFD to no more than six to Restrict a single DFD to no more than six to eight processeseight processes

Use another tool to document the lowest Use another tool to document the lowest level of detail but use no more than a single level of detail but use no more than a single page. page.

B-22

Data Flow Diagramming Data Flow Diagramming GuidelinesGuidelines

1. Label each data flow with a unique name.1. Label each data flow with a unique name.

2. Keep data flow names constant between levels.2. Keep data flow names constant between levels.

3. Show proper disposition of records deleted from a data 3. Show proper disposition of records deleted from a data store.store.

4. When documenting a computer program, do not include 4. When documenting a computer program, do not include reads/writes.reads/writes.

5. Avoid read-only processes.5. Avoid read-only processes.

6. Write-only processes are permissible when time serves as 6. Write-only processes are permissible when time serves as the trigger.the trigger.

B-23

Structured EnglishStructured English

Narrative form of computer code Narrative form of computer code documentationdocumentation

Based on PseudocodeBased on Pseudocode Abbreviated, formalized pseudocode in a Abbreviated, formalized pseudocode in a

particular format that looks like computer particular format that looks like computer codecode

B-24

Structured English Structured English GuidelinesGuidelines

1) Use a verb when describing each 1) Use a verb when describing each processing strip.processing strip.

2) Supplement verb with one or more objects 2) Supplement verb with one or more objects when necessary.when necessary.

3) Use only three constructs of programming.3) Use only three constructs of programming.– SequenceSequence– SelectionSelection– RepetitionRepetition

B-25

Structured English Structured English Guidelines [cont.]Guidelines [cont.]

4) Use only data names defined in the data 4) Use only data names defined in the data dictionary.dictionary.

5) Use uppercase for all data names and 5) Use uppercase for all data names and computer syntax.computer syntax.

6) Indent to show a hierarchical structure.6) Indent to show a hierarchical structure.

B-26

Structured English Structured English Guidelines [cont.]Guidelines [cont.]

7) When documentation is subdivided into 7) When documentation is subdivided into modules, use the first line of each module modules, use the first line of each module for an identifying label and leave at least for an identifying label and leave at least one blank line in-between.one blank line in-between.

8) Restrict each module to a single entry 8) Restrict each module to a single entry and exit point.and exit point.

B-27

Structure English ExampleStructure English ExampleSTART

Initialize storage TOTAL.SALES, TOT.COM = 0

Process sales data DO WHILE (more records) PERFORM READ DATA PERFORM PROCESS DATA PERFORM PRINT DATA END DO

B-28

29

End of Session 12