Académique Documents
Professionnel Documents
Culture Documents
Data
Data may be defined broadly to include two interrelated components:
Data Models that provide structure to data
Data values
File Orientation Data-base Orientation
Record & Repository Creation Repository Maintenance through additions and updates Data Retrieval Data Archival and Removal
Entities
An Entity is an object, person, or event about which a firm wants to collect and maintain data Characteristics of Entities are Attributes Each attribute stored in the system is a Data Element
There is usually a one-to-one correspondence between attributes and data elements A broadly defined attribute may have several specific attributes and therefore data elements. e.g., Shipping Address
Street Address City State Zip Code Country
Data Models
Files
File Record Data Element
Data-base
Data bases
-
Figure 4-1
Data Elements
Every recorded attribute of an entity is a data element Field Length: This is the number of contiguous positions required to store a data element Data Type:
Character Numeric Date Raw
Data Value
Some Specifics
File
Record-Key
Record keys: These are data elements within records that serve as sort keys. e.g., customeraccount number Two types of keys often used in master and transaction file records are a primary key and one or more secondary keys
A Primary key (also called a record key) is the attribute that uniquely identifies a specific record. They are usually of numeric or alphanumeric modes, e.g., customer number A Secondary key is an attribute other than the primary key and represents an alternative way to sort or access records in a file, e.g., customer last name
Flags
Flags that are symbols or characters used for control purposes, e.g., end-of-batch flag. Flags are not visible to the end-user. It is a system-managed field that is transparent to the user.
Generally the primary keys are placed to occupy the first fields of the records Generally balance amounts or amounts of transactions are placed in the last fields
Data Dictionary
A data dictionary is a computer file that maintains descriptive information about the items in a database Each computer record of the data dictionary contains information about a single data item used in an AIS Examples of information that might be stored in a data dictionary are source document(s) used to create the data item, programs that update the data item and classification information about the items length and data type
Entity-Relationship Diagram - II
In order to arrive at a specific E-R model, one must select the entities first, and then define the relationship between them (cardinalities: one-to-one, one-to-many, many-to-many) Rectangle=Entity Diamond=Relationship Line=Links:
attribute to entity entity to relationship attribute to relationship
Sometimes we use ellipses to represent specific attributes of entities, e.g., customer_#, student_last_name, etc. To go from the ER model to a specific conceptual data model (hierarchical, network, relational, object-oriented), we typically assign attributes to the entities and relationships so as to obtain fully specified pointers (hierarchical & network), and normalized tables (relational)
Data-Flow Diagrams
A data-flow diagram shows the physical and logical flows of data through a transaction processing system without regard to the time period when each occurs Physical devices that transform data are not used in the logical diagrams Because of the simplified focus, only four symbols are needed
Physical DFDs
A Physical DFD documents the physical structure of an existing system. It answers questions such as Where an entity works, How an entity works, the work is done by Whom, etc. Given the very physical focus of a physical DFD, it changes whenever the entities, technology used to implement the system, etc. changes Physical DFDs have no lower levels This limitation makes physical DFDs cumbersome to work with, and usually of limited value
Logical DFDs - I
Logical Data flow diagrams are usually drawn in levels that include increasing amounts of detail A top level (or high-level) DFD that provides an overall picture of an application or system is called a context diagram A context diagram is then decomposed, or broken down, into successively lower levels of detail
Logical DFDs - II
Logical Data flow diagrams document the processes in an existing or proposed system (What tasks) Because the logic of a system changes infrequently, relative to its physical nature, a logical DFD will remain relatively constant over time Logical Data flow diagrams typically have levels below the level-0 diagram
Context Diagram
Level 1 diagram(s)
A Context Diagram
Process bubble
Customer Payment Relevant Environment comprised of External Entities Cash Receipts }Boundary (border between a system and its environment) Process
Dataflows (Interfaces)
This is a flow connecting a system with its environment
Deposit
Bank
A Physical DFD
Customer
Cash
1. Bubbles are labeled with nouns 2. Data flows & files have physical descriptions Order &
register tape
Cashier 2.0
Deposit slip & cash
Sales information
BookKeeper 3.0
A Logical DFD
1) Bubbles are labeled with verbs that describe the activity taking place 2) Data flows & files have logical Receipts & descriptions receipts summary
Verified receipts
Sales data
Sales Journal
Bank
Copyright 2000 John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for distribution or resale. The publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.