Data dictionary

WEEK V
JOEY MILLER D. MINGUILLAN

 Data dictionary concepts
 Defining data flow
 Defining data structures
 Defining elements
 Defining data stores
 Using the data dictionary
 Data dictionary analysis
Kendall & KendallCopyright © 2002 by Prentice Hall, Inc.
10-
2

 Data dictionary is a main method for
analyzing the data flows and data stores of
data-oriented systems
 The data dictionary is a reference work of
data about data (metadata)
 It collects, coordinates, and confirms what a
specific data term means to different people
in the organization
10-
3

 The data dictionary may be used for the
following reasons:
◦ Provide documentation
◦ Eliminate redundancy
◦ Validate the data flow diagram
◦ Provide a starting point for developing screens and
reports
◦ To develop the logic for DFD processes
10-
4

 A data repository is a large collection of
project information
 It includes
◦ Information about system data
◦ Procedural logic
◦ Screen and report design
◦ Relationships between entries
◦ Project requirements and deliverables
◦ Project management information
10-
5

 Data dictionaries contain
◦ Data flow
◦ Data structures
◦ Elements
◦ Data stores
10-
6

 Each data flow should be defined with
descriptive information and it's composite
structure or elements
 Include the following information:
◦ ID - identification number
◦ Label, the text that should appear on the diagram
◦ A general description of the data flow
10-
7

 (Continued)
◦ The source of the data flow
 This could be an external entity, a process, or a data
flow coming from a data store
◦ The destination of the data flow
◦ Type of data flow, either
 A record entering or leaving a file
 Containing a report, form, or screen
 Internal - used between processes
10-
8

 (Continued)
◦ The name of the data structure or elements
◦ The volume per unit time
 This could be records per day or any other unit of time
◦ An area for further comments and notations about
the data flow
10-
9

10-
10
Name Customer Order
Description Contains customer order information and is used
to update the customer master and item files and
to produce an order record.
Source Customer External Entity
Destination Process 1, Add Customer Order
Type Screen
Data Structure Order Information
Volume/Time 10/hour
Comments An order record contains information for one
customer order. The order may be received by
mail, fax, or by telephone.

 Data structures are a group of smaller
structures and elements
 An algebraic notation is used to represent the
data structure
10-
11

 The symbols used are
◦ Equal sign, meaning “consists of”
◦ Plus sign, meaning "and”
◦ Braces {} meaning repetitive elements, a repeating
element or group of elements
◦ Brackets [] for an either/or situation
 The elements listed inside are mutually exclusive
◦ Parentheses () for an optional element
10-
12

 A repeating group may be
◦ A sub-form
◦ A screen or form table
◦ A program table, matrix, or array
 There may be one repeating element or
several within the group
10-
13

 The repeating group may have
◦ Conditions
◦ A fixed number of repetitions
◦ Upper and lower limits for the number of
repetitions
10-
14

 Data structures may be either logical or
physical
 Logical data structures indicate the
composition of the data familiar to the user
10-
15

 Include elements and information necessary
to implement the system
 Additional physical elements include
◦ Key fields used to locate records
◦ Codes to indicate record status
◦ Codes to identify records when multiple record
types exist on a single file
◦ A count of repeating group entries
10-
16

10-
17
Customer Order = Customer Number +
Customer Name +
Address +
Telephone +
Catalog Number +
Order Date +
{Order Items} +
Merchandise Total +
(Tax) +
Shipping and Handling +
Order Total +
Method of Payment +
(Credit Card Type) +
(Credit Card Number) +
(Expiration Date)

 A structure may consist of elements or
smaller structural records
 These are a group of fields, such as
◦ Customer Name
◦ Address
◦ Telephone
 Each of these must be further defined until
only elements remain
10-
18

10-
19
 Structural records and elements that are
used within many different systems should
be given a non-system-specific name,
such as street, city, and zip
 The names do not reflect a functional area
 This allows the analyst to define them
once and use in many different
applications

10-
20
Customer Name = First Name +
(Middle Initial) +
Last Name
Address = Street +
(Apartment) +
City +
State +
Zip +
(Zip Expansion) +
(Country)
Telephone = Area code +
Local number

 Data elements should be defined with
descriptive information, length and type of
data information, validation criteria, and
default values
 Each element should be defined once in the
data dictionary
10-
21

 Attributes of each element are
◦ Element ID. This is an optional entry that allows the
analyst to build automated data dictionary entries
◦ The name of the element, descriptive and unique
 It should be what the element is commonly called in
most programs or by the major user of the element
10-
22

◦ Aliases, which are synonyms or other names for the
element
◦ These are names used by different users within
different systems
◦ Example, a Customer Number may be called a
 Receivable Account Number
 Client Number
10-
23

◦ A short description of the element
◦ Whether the element is base or derived
◦ A base element is one that has been initially keyed
into the system
◦ A derived element is one that is created by a
process, usually as the result of a calculation or
some logic
10-
24

 The length of an element
◦ This should be the stored length of the item
◦ The length used on a screen or printed lengths may
differ
10-
25

 What should the element length be?
◦ Some elements have standard lengths, such as a
state abbreviation, zip code, or telephone number
◦ For other elements, the length may vary and the
analyst and user community must decide the final
length
10-
26

◦ Numeric amount lengths should be determined by
figuring the largest number the amount will contain
and then allowing room for expansion
◦ Totals should be large enough to accommodate the
numbers accumulated into them
◦ It is often useful to sample historical data to
determine a suitable length
10-
27

10-
28
Percent of data that will
Element Length fit within the length
Last Name 11 98%
First Name 18 95%
Company Name 20 95%
Street 18 90%
City 17 99%

10-
29
 If the element is too small, the data will be
truncated
 The analyst must decide how this will
affect the system outputs
 If a last name is truncated, mail would
usually still be delivered
 A truncated email address or Web address
is not usable

10-
30
 The type of data, either numeric, date,
alphabetic or alphanumeric or other
microcomputer formats
 Storage type for numeric data
◦ Mainframe: packed, binary, display
◦ Microcomputer (PC) formats
◦ PC formats depend on how the data will be used,
such as Currency, Number, or Scientific

10-
31
Bit - A value of 1 or 0, a true/false value
Char, varchar, text - Any alphanumeric character
Datetime, smalldatetime - Alphanumeric data, several formats
Decimal, numeric - Numeric data that is accurate to the least significant digit
Can contain a whole and decimal portion
Float, real - Floating point values that contain an approximate decimal value
Int, smallint, tinyint - Only integer (whole digit) data
Money, smallmoney - Monetary numbers accurate to four decimal places
Binary, varbinary, image - Binary strings (sound, picture, video)
Cursor, timestamp, uniqueidentifier - A value that is always unique
within a database

10-
32
 Input and output formats should be
included, using coding symbols:
◦ Z - Zero suppress
◦ 9 - Number
◦ X - Character
◦ X(8) - 8 characters
◦ . , - Comma, decimal point, hyphen
 These may translate into masks used to
define database fields

10-
33
 Validation criteria must be defined
 Elements are either
◦ Discrete, meaning they have fixed values
 Discrete elements are verified by checking the
values within a program
 They may search a table of codes
◦ Continuous, with a smooth range of values
 Continuous elements are checked that the data is
within limits or ranges

10-
34
 Include any default value the element may
have
 The default value is displayed on entry
screens
 Reduces the amount of keying
◦ Default values on GUI screens
 Initially display in drop-down lists
 Are selected when a group of radio buttons are
used

10-
35
 An additional comment or remarks area
 This might be used to indicate the format
of the date, special validation that is
required, the check-digit method used,
and so on

10-
36
Name Customer Number
Alias Client Number
Alias Receivable Account Number
Description Uniquely identifies a customer that has made any business
transaction within the last five years.
Length 6
Input Format 9(6)
Output Format 9(6)
Default Value
Continuous/Discrete Continuous
Type Numeric
Base or Derived Derived
Upper Limit <999999
Lower Limit >18
Discrete Value/Meaning
Comments The customer number must pass a modulus-11 check-digit test.

 Data stores contain a minimal of all base
elements as well as many derived elements
 Data stores are created for each different
data entity, that is, each different person,
place, or thing being stored
10-
37

 Data flow base elements are grouped
together and a data store is created for each
unique group
 Since a data flow may only show part of the
collective data, called the user view, you may
have to examine many different data flow
structures to arrive at a complete data store
description
10-
38

 The Data Store ID
 The Data Store Name, descriptive and unique
 An Alias for the file
 A short description of the data store
 The file type, either manual or computerized
10-
39

 If the file is computerized, the file format
designates whether the file is a database
file or the format of a traditional flat file
 The maximum and average number of
records on the file
 The growth per year
◦ This helps the analyst to predict the amount of
disk space required
10-
40

 The data set name specifies the table or file
name, if known
◦ In the initial design stages, this may be left blank
 The data structure should use a name found
in the data dictionary
10-
41

 Primary and secondary keys must be
elements (or a combination of elements)
found within the data structure
 Example: Customer Master File
◦ Customer Number is the primary key, which should
be unique
◦ The Customer Name, Telephone, and Zip Code are
secondary keys
10-
42

10-
43
ID D1
Name Customer Master File
Alias Client Master File
Description Contains a record for each customer
File Type Computer
File Format Database
Record Size 200
Maximum Records 45,000
Average Records 42,000
Percent Growth/Year 6%

10-
44
Data Set/Table Name Customer
Copy Member Custmast
Data Structure Customer Record
Primary Key Customer Number
Secondary Keys Customer Name, Telephone, Zip Code
Comments The Customer Master file records are
copied to a history file and purged if the customer has not
purchased an item within the past five years. A customer
may be retained even if he or she has not made a purchase
by requesting a catalog.

 Data dictionary entries vary according to the
level of the corresponding data flow diagram
 Data dictionaries are created in a top-down
manner
 Data dictionary entries may be used to
validate parent and child data flow diagram
level balancing
10-
45

 Whole structures, such as the whole report or
screen, are used on the top level of the data
flow diagram
◦ Either the context level or diagram zero
 Data structures are used on intermediate-
level data flow diagram
 Elements are used on lower-level data flow
diagrams
10-
46

 1. Information from interviews and JAD
sessions is summarized on Input and Output
Analysis Forms
◦ This provides a means of summarizing system data
and how it is used
 2. Each structure or group of elements is
analyzed
10-
47

 3. Each element should be analyzed by asking
the following questions:
◦ A. Are there many of the field?
 If the answer is yes, indicate that the field is a
repeating field using the { } symbols
◦ B. Is the element mutually exclusive of another
element?
 If the answer is yes, surround the two fields with the [ |
] symbols
10-
48

◦ C. Is the field an optional entry or optionally
printed or displayed?
 If so, surround the field with parenthesis ( )
 4. All data entered into the system must be
stored
◦ Create one file or database file for each different
type of data that must be stored
◦ Add a key field that is unique to each file
10-
49

 Data stores may be determined by analyzing
data flows
 Each data store should consist of elements on
the data flows that are logically related,
meaning they describe the same entity
10-
50

 To have maximum power, the data dictionary
should be tied into other programs in the
system
 When an item is updated or deleted from the
data dictionary it is automatically updated or
deleted from the database
10-
51

 Data dictionaries may be used to
◦ Create reports, screens, and forms
◦ Generate computer program source code
◦ Analyze the system design for completion and to
detect design flaws
10-
52

 To create screens, reports, and forms
◦ Use the element definitions to create fields
◦ Arrange the fields in an aesthetically pleasing
screen, form, or report, using design guidelines
and common sense
◦ Repeating groups become columns
◦ Structural records are grouped together on the
screen, report, or form
10-
53

 The data dictionary may be used in
conjunction with the data flow diagram to
analyze the design, detecting flaws and areas
that need clarification
10-
54

 Some considerations for analysis are
◦ All base elements on an output data flow must be
present on an input data flow to the process
producing the output
◦ Base elements are keyed and should never be
created by a process
10-
55

◦ A derived element should be output from at least
one process that it is not input into
◦ The elements that are present on a data flow into or
coming from a data store must be contained within
the data store
10-
56

Data dictionary

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to Data dictionary (20)

Recently uploaded (20)

Data dictionary