1

Digital Consulting

1. Describe the rules for creating a context diagram. Place a single process symbol in center,name ir process 0. It will present your entire information system. Place external around page and connect them with data flow to proecess 0. Place and label all external entities around central process Between external entities and central system create input and output dataflows

2. Make a basic list of dos and donts when developing DFDs. Dont cross other lines when drawing DFD Diagram must be on single page Each process has unique reference number, and each set of number have unique name Use DFD shapes as described in rules

3. Explain the importance of leveling and balancing. Leveling and balancing techniques are vary important for developing lower-level diagrams. Leveling is the process of drawing a series of increasingly detailed diagrams, until the desired degree of detail is reached. Balancing maintains consistency among the entire series of diagrams, including input and output data flows, data definition, and process descriptions. Leveling displays the information system as a single process and then shows more detail until all processes are functional primitives. A balanced set of DFDs preserves the input and output data flows of the parent on the child DFD. 4. Ask Sara and Mike to review the order system context diagram on page 208, and compare it with the order system diagram 0 DFD on page 212. Then ask them to answer the following questions: (a) How many external entities are shown in each diagram? (b) In each diagram, how many data flows connect to the external entities? (c) How many subprocesses are identified in the diagram 0 DFD? (d) Could the data store have been shown in the context diagram? Why or why not? a) 5 entities in each diagram b) 9 data flows connect c) 3 subprocesses d) It couldnt been shown, beacause data store cant connect to external entitie.

Precision Tools

1. Draw a context diagram for the order system.

2. Draw a diagram 0 DFD for the order system.

3. Name four attributes that you can use to define a process in the order system.

Process name, DFD process name Description, description of process main purpose Input data flow, data flow names that enters the process Output data flow,data flow names that leaves the process

4. Name four attributes that you can use to define an entity in the order system.

External entity name, DFD external entity name Alternate name, aliases of external entity name Description, describes external entity Output data flow, data flows leaving external entity

Claremont School

1. Create a decision table that describes the Claremont School course catalog regarding eligibility for CIS 288. Show all possible rules. 1 Y Y Y X 2 Y Y N X 3 Y N Y X 4 Y N N X 5 N Y Y X 6 N Y N X 7 N N Y X 8 N N N X

CIS 100 CIS 286 Waiver Eligible Ineligible

2. Simplify the table you just created. Describe the results. 1 Y Y X 2 N Y Y X 3 N Y N X 4 Y N Y X 5 Y N N X 6 N N X

CIS 100 CIS 286 Waiver Eligible Ineligible

3. Draw a simplified decision tree to represent the Claremont School catalog. Describe the results.
CIS 286 Waiver No CIS 286 CIS 110 No CIS 286 CIS 286 No Waiver No CIS 110 Not Eligible No Waiver Waiver Not Eligible Eligible Not Eligible Eligible Eligible

4. Why might you use a decision tree rather than a decision table? Decision trees are a graphic ways to present system. More people find graphic presentations more attractive and more easy to undestand. Decision tree can be better to describe simple processes, but descision table could be better for more difficult processes.

City Bus Lines

1. Create a decision table that describes the bus transfer process.

Need more buses All other routes operating on schedule Supervisor override Give extra buses Dont give extra buses

1 Y

2 Y

3 Y

4 Y

5 N

6 N

7 N

8 N

Y X

N X

Y X

Need more buses

1 Y

2 Y

3 Y

4 N

All other routes operating on schedule Supervisor override Give extra buses Dont give extra buses

Y X

2. Draw a decision tree that describes the bus transfer process.

Other routes on schedule

Yes Yes

Give extra buses Give extra buses

Yes
Need more buses

No
Supervisor override

No

Dont Give extra buses

No Dont Give extra buses

3. Name four attributes that you can use to define a data flow in the bus information system.

Data flow name. DFD data flow name. Alternate names. Aliases for the DFD data flow name. Description. Describes the data flow and its purpose. Volume and frequency. Describes the expected number of occurrences for the data flow per unit of time.

4. Name four attributes that you can use to define a data store in the bus information system. Data store name or label. The DFD data store name. Alternate names. Aliases for the DFD data store name. Description. Description of data store and its purposes. Input data flows. The standard DFD names for the data flows entering the data store.