The mathematical model of formulas and logic used in a system
The abstract creating of an ideal system transformation
The model that is produced by extreme programming
The expanded, thoroughly balanced and normalized use case for a system
A formal way of representing the data that are used and created by a business system
Illustrate return-on-investment, break-even point, and economic feasibility
Represent actions or processes that occur in the to-be system
Be used as a logical data model in analysis and as a physical data model in design
Only be used with Document analysis
Only be used with JAD sessions
People
Places
Things
Actions
Enterprise Relationship Diagramming
Entity Relationship Diagramming
Electronic Repository Diagramming
Enhanced Relationship Diagramming
Entity Repository Design
Discover the individual pieces of information in a system and how they are organized and related to each other
Find what processes use what data
Determine the cardinality of processes in a system and if the modality of process is 1:M; 1:1; or M:N
Evaluate data structure hierarchies as to processing anomalies in a business system
Discover how the people, places and things in a business system are generated, moved, transformed and stored
Special symbols are added to show high-level business rules
The diagrams are drawn in a sequential order – from top to bottom
Similar kinds of information are listed together in entities
ERD's are data modeling techniques
Lines are drawn to show relationships among the data
Cardinality
Modality
Attribute
Relationship
Data stores
Age
Student identification number
Class room number
Home phone
Gender
Customer
Policy
Agent
Zip code
Car
Relationships of one-to-one; one-to-many; or many-to-many
Whether a child entity can exist with or without a related instance in the parent entity
The hierarchical structure that was developed in process models applied to data models
The number of attributes generated by an entity
Whether the entity has a unique identifier or a concatenated identifier
Information space
Data store
Meta file
Data flow
Data dictionary
Metadata
Cached information
Compiled data
Data repository
File silo
An oval
A crow's foot
The letter M
An infinity symbol
A diamond
Process, data flow, data store
Attribute, modularity, cardinality
Relationship, data flow, entity
Relationship, attribute, entity
Process, entity and relationship
There will be at most seven entities
There will be at most seven relationships
If you identify more than seven entities, analyze and combine until you have seven or less
It is an iterative process
Entities will have at most seven attributes
From the CASE tool
Data flows from DFD's
Requirements documents
The system proposal document
Through interviews (what users need for reports and processing)
Identify relationships
Define attributes and assign identifiers
Recognize entities
Test them with users
Compile them with Java
Identify data flows from the level 0 DFD diagram
Draw the relationships between the entities
Identify the attributes for each entity
Identify the entities
Identify the processes, data flows and data stores
0 normal form to 1st normal form (1NF)
1st normal form (1NF) to 2nd normal form (2NF)
3rd normal form (2NF) to 3rd normal form (3NF)
Generalized normal form (GNF) to fully normalized form (FNF)
Dependent normal form (DNF) to Independent normal form (INF)
When a child requires attributes from the parent
When there is only one entity for a data process model
When an entity can exist without the help of another entity
Where the entity identifier is also the primary key
When a entity comes from an external source (external entity)
Independent
Incomplete
Dependent
Variable
Non-complying
Base normal form
First normal form
Second normal form
Third normal form
Cannot tell from the above information
True
False
True
False
True
False