Exam 4: Documenting Information Systems

arrow
  • Select Tags
search iconSearch Question
flashcardsStudy Flashcards
  • Select Tags

Internal entities are included on both data flow diagrams (DFDs) and systems flowcharts.

(True/False)
4.7/5
(45)

External entities are persons, places, or things outside the context of the system.

(True/False)
5.0/5
(34)

A(n) ______________________________ process activities might include picking goods in the warehouse inspecting goods at the receiving dock, or counting cash.

(Short Answer)
4.9/5
(37)

How many circles (bubbles) are included in a correctly drawn context diagram?

(Multiple Choice)
4.8/5
(38)

When the context diagram and the level 0 diagram reflect the equivalent external data flows, the two diagrams are said to be ______________________________.

(Short Answer)
4.9/5
(38)

A(n) ______________________________ is a data flow that leaves a bubble but does not go to any other bubble or data store.

(Short Answer)
4.7/5
(36)

Bubbles are labelled with verbs in a ____________ data flow diagram.

(Short Answer)
5.0/5
(43)

Figure TB-4.3 shows a context diagram of a cash sales system. The diagram intentionally violates several of the guidelines and other techniques presented in the text for drawing data flow diagrams. Required: Identify as many of the errors in data flow diagram construction as you can. In the diagram, place consecutive numbers (each in a circle) next to the points at which the errors exist. On your solution sheet, list the numbers and write a one- to two-sentence description of each error and what the correct procedure should be. Error 1 is provided as an example of how to construct the solution (but you must place the circled number 1 on your solution diagram). Errar\underline{Errar} \quad\quad\quad\quad\quad ErrarDescription\underline{Errar Description} 1 \quad\quad\quad\quad\quad\quad\quad\quad\quad Data flows should not connect twa external entities. Depending on the extent of the \quad\quad\quad\quad\quad\quad\quad\quad\quad system being analyzed, either the mail roum or the bark entity should be elininated \quad\quad\quad\quad\quad\quad\quad\quad\quad or docurnented wrthin the system.  Figure TB-4.3 shows a context diagram of a cash sales system. The diagram intentionally violates several of the guidelines and other techniques presented in the text for drawing data flow diagrams. Required: Identify as many of the errors in data flow diagram construction as you can. In the diagram, place consecutive numbers (each in a circle) next to the points at which the errors exist. On your solution sheet, list the numbers and write a one- to two-sentence description of each error and what the correct procedure should be. Error 1 is provided as an example of how to construct the solution (but you must place the circled number 1 on your solution diagram).   \underline{Errar}    \quad\quad\quad\quad\quad   \underline{Errar Description}  1 \quad\quad\quad\quad\quad\quad\quad\quad\quad Data flows should not connect twa external entities. Depending on the extent of the   \quad\quad\quad\quad\quad\quad\quad\quad\quad system being analyzed, either the mail roum or the bark entity should be elininated   \quad\quad\quad\quad\quad\quad\quad\quad\quad or docurnented wrthin the system.

(Essay)
4.8/5
(37)

All of the following are "guidelines" for grouping activities in a level 0 DFD except:

(Multiple Choice)
4.8/5
(40)

A(n) ______________________________ is a graphical representation of a system that depicts a system's components; the data flows among the components; and the sources, destination, and storage of data.

(Short Answer)
4.9/5
(42)

A(n) ______________________________ is any action being performed by an internal or external entity.

(Short Answer)
4.8/5
(40)

When we document a(n) ______________________________ system, the central computer will have one data store/disk symbol.

(Short Answer)
4.9/5
(32)

A(n) ______________________________ data flow diagram (DFD) depicts what activities the system performs rather than how, where, or by whom they are performed.

(Short Answer)
4.7/5
(39)

System flowcharts use only four symbols.

(True/False)
4.8/5
(43)

In the top-down partitioning of process 3.0, the next level's process bubbles would be labeled (assuming there are four subprocesses):

(Multiple Choice)
4.8/5
(33)

In a physical data flow diagram (DFD), this is something within the system that transforms data.

(Multiple Choice)
4.9/5
(42)

Which data flow diagram (DFD) symbol portrays a source or destination of data outside the system?

(Multiple Choice)
4.9/5
(37)

In a data flow diagram (DFD), a(n) ______________________________ symbol represents a pathway for data.

(Short Answer)
4.8/5
(34)

Which data flow diagram (DFD) symbol is portrayed by two parallel lines?

(Multiple Choice)
4.8/5
(41)

Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution. (A)  Manual Update to Accounts Receivable\text { Manual Update to Accounts Receivable} Subsidiary Ledger\text {Subsidiary Ledger}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}      (B) Query Computer ized Accounts Receivable\text {Query Computer ized Accounts Receivable} Mastar Data\text {Mastar Data}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}      (C) Manual Preparation of a Customer Invoice\text {Manual Preparation of a Customer Invoice} from a Shippina Notice\text {from a Shippina Notice}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}      (D)  Print a Report in Data Processing and Send it \text { Print a Report in Data Processing and Send it } to the Accounts Receivable Department\text {to the Accounts Receivable Department}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}      (E)  Print a Report on a computer in the Accounts Receivable Department\text { Print a Report on a computer in the Accounts Receivable Department}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}      (F) Update an Accounts Receivable Master\text {Update an Accounts Receivable Master}  data (maintained on disk) from event\text { data (maintained on disk) from event} data on disk\text {data on disk}  Figure TB-4.7 shows several systems flowchart routines that intentionally violate good flowchart construction procedures. Required: Redraw each of the routines so that they conform to the guidelines and other techniques presented in the text for drawing systems flowcharts. HINT: Be alert to the description of each routine; the descriptions should govern your solution.  (A) \text { Manual Update to Accounts Receivable}   \text {Subsidiary Ledger}      (B)  \text {Query Computer ized Accounts Receivable}   \text {Mastar Data}      (C)  \text {Manual Preparation of a Customer Invoice}    \text {from a Shippina Notice}       (D) \text { Print a Report in Data Processing and Send it }   \text {to the Accounts Receivable Department}     (E) \text { Print a Report on a computer in the Accounts Receivable Department}       (F)  \text {Update an Accounts Receivable Master}   \text { data (maintained on disk) from event}    \text {data on disk}

(Essay)
4.8/5
(30)
Showing 81 - 100 of 129
close modal

Filters

  • Essay(0)
  • Multiple Choice(0)
  • Short Answer(0)
  • True False(0)
  • Matching(0)