SAD5 Flashcards

1
Q

Data Flow Diagram

A

shows the data movements through information system but does not show program logic of process steps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

DFD Symbols

A
  • Gane and Sarson
  • Yourdon
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

DFD Symbol Names

A
  • process
  • data flow
  • data store
  • external entity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Process

A

receives an input and produces an output thas has a different content, form or both

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

business rules/business logic

A

transforms data into required results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

blackbox

A

inputs, outputs, functions are known but underlying details and logic arr hidden

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

data flow

A

path for data to move from one part of the information system to another

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

data flow types

A
  1. spontaneous generation
  2. black hole
  3. gray hole
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

spontaneous generation

A

produces output, but has no input data flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

black hole

A

which is a process that has input, but produces no output.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

data store

A
  • represent data that the system stores because one or more processes need to use the data at a later time
  • connected into a process with a data flow
  • does not show the detailed contents of data store
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Entity

A
  • rectangle with noun inside
  • DFD shows external entities that provide data to the system and receive output from system
  • DFD shows boundaries of the system and how system interfaces with outside world
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

DFD known as terminators

A

because they are the origin and data’s final destination

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Source

A

entity that supplies data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

sink

A

entity that receives data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Creating a set of dfd

A

Create a graphical model of the information system based on your fact-finding results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Step 1: Draw Context Diagram

A

top-level view of an information system that showsits boundaries and scope

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Step 2: Draw Diagram 0 DFD

A

To show the deta il inside the black box,
you create DFD diagram 0

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

diverging data flow

A

data flow in which the same data travels to two or more different locations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

parent diagram

A

When you explode a DFD, the higher-level diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

child diagram

A

lower-level diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

functional primitive

A

process that consists of a single function that is not exploded further

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Step 3: Draw the Lower Level Diagrams
Leveling and Balancing

A

lower-level DFDs

24
Q

Leveling

A

process of drawing a series of increasingly detailed diagrams, until all functional primitives are identified

25
Balancing
* maintains consistency among a set of DFDs by ensuring that input and output data flows align properly * ensures that the input and output data flows of the parent DFD are maintained on the child DFD
26
data dictionary or data structures
* central storehouse of information about the system's data * collect, document, and organize specific facts about the system, including the contents of data flows, data stores, entities, and processes
27
data element/item/field
smalles piece of data that has a meaning within the information system
28
record
meaningful combination of related data elements that is included in a data flow or retained in a data store
29
CASE Tools for Documentation
* The more complex the system, the more difficult it is to maintain full and accurate documentation * **modern CASE tools** simplify the task * **CASE repository** ensures data consistency
30
Documenting the Data Elements
* You must document every data element in the data dictionary * The objective is the same: to provide clear, comprehensive information about the data and processes that make up the system
31
Attributes usually are recorded and described in the data dictionary
1. data element name or label 2. alias 3. type and length 4. dafualt value 5. acceptable value 6. source 7. security 8. description and comments
32
data element name or label
standard name of the element
33
alias
other than the standard name of elements
34
type and length
* **Type** refers to whether the data element contains numeric, alphabetic, or character values * **length** maximum number of characters for an alphabetic or character data element or the maximum number of digits and number of decimal positions for a numeric data element
35
default value
value of data element if nothing was entered
36
Acceptable Value
**domain** is the permitted set of values for data element **validity rules** refers to the value for data element
37
Source
origination point of data element
38
security
individual/department that has access for each data element
39
Responsible user(s)
Identification of the user(s) responsible for entering and changing values for the data element.
40
Description and comments
allows you to enter additional notes
41
Documenting the Data Flows
1. Data flow name or label 2. Alternate name 3. Description 4. Origin 5. Destination 6. Record 7. Volume and Frequency
42
Documenting Data Process
1.Process name or label 2.Description 3.Process number 4.Process description
43
Documenting Data Store
1. Date store name or label 2. Alternate name 3. description 4. attributes 5. volume and frequency
44
Documenting entities
1. entity name or label 2. description 3. alternate name 4. input data flow 5. output data flow
45
Documenting data records
* record or data structure name * alternate name * description * attributes
46
data dictionary report
* alphabetized list of all data elements by name * report describing each data element and indicating the user or department that is responsible for data entry, updating, or deletion * A report of all data flows and data stores that use a particular data element * reports showing all characteristics of data elements, records, data flows, processes, or any other selected item stored in the data dictionary
47
data dictionary report
* alphabetized list of all data elements by name * report describing each data element and indicating the user or department that is responsible for data entry, updating, or deletion * A report of all data flows and data stores that use a particular data element * reports showing all characteristics of data elements, records, data flows, processes, or any other selected item stored in the data dictionary
48
Modular design
combination of three logical structures that serve as the building blocks for the process
49
sequence
refers to the completion of steps in a sequencial manner
50
selection
completion of one of two or more process steps based on the results of a test or condition
51
iteration aka looping
completion of a process step that is repeated until a specific condition changes
52
structured english
subset of standard English that describes logical processes clearly and accurately **rules:** * use only the three building blocks (sequence, selection, iteration) * use indention for readability * use limited vocubulary that includes standard terms
53
decision table
* shows logical structure, with all possible combinations of conditions and resulting actions * often are the best way to describe a complex set of conditions
54
decision tree
Graphical representation of the conditions, actions, and rules found in a decision table
55
logical model
tool used to deevlop physical model
56
physical model
shows system requirement implemented
57
Four-Model Approach
* physical model of the current system * logical model of the current system * logical model of the new system * Physical model of the new system