|
Provided by: Serebra Learning Corporation Data Modeling: Create Basic ModelsUnfiled |
 |
Training
Provided by Serebra Learning Corporation
This is the first course in a two-part series which covers Data Modeling. You will begin by learning a top-down systematic approach to database development using entity-relationship models and normalization. Then you will use this approach to identify and define business information requirements both in the course and within your work environment. This course can be used as part of Oracle's integrated curriculum. It is designed to act as an alternative prerequisite to a large number of ILT courses in related curricula areas such as Server Developer/2000 and Designer/2000.
|
|
||||||||||
Data Modeling: Create Basic Models
Serebra Learning Corporation 119 - 7565 132nd Street Surrey BC V3W 1K5 Canada
Audience
Business managers business analysts technical analysts database designers database administrators and anyone responsible for the analysis and specification of data during the application development lifecycle.
Objective
- Consider the approaches to information modeling.
- Understand the components of the Entity Relationship Model.
- Understand the need for detailed definitions of attributes Identifiers and domains.
- Understand how attributes Identifiers and domains will be used during later development.
Topics Include
Unit 1: Introduction to Relational Data Modeling
- Identify the tasks involved in Systems Development.
- Identify some of the techniques involved in system development.
- Identify where conceptual modeling fits in a development cycle.
- Identify where logical modeling fits in a development cycle.
- Identify where physical modeling fits in a development cycle.
- Identify conceptual terms and logical terms.
- Identify why different terms are used within conceptual and logical modeling.
- Identify the reasons for modeling information.
- Identify the consequences of not modeling information.
- Identify what is involved in ER modeling.
- Identify what is involved in the technique of Normalization.
- Identify why information is hardware and software independent.
- Identify the benefits of combining Normalization with ER modeling.
Unit 2: Creating a Basic Entity Relationship Model
- Identify what an entity is.
- Identify the naming conventions used for an entity.
- Identify the drawing conventions for an entity.
- Identify the difference between an entity and an instance of an entity.
- Identify the definition of a relationship.
- Identify the implications of an optional relationship.
- Identify the implications of a mandatory relationship.
- Combine relationships to create a bi-directional relationship.
- Distinguish between a 'one or more' and a 'one and only one' relationship.
- Identify how a specific value can be attached to a one or more relationship end.
- Identify why it is necessary to name a relationship.
- Identify the conventions used for a relationship name.
- Identify a one to many relationship between two entities to reflect a business scenario.
- Identify a many to many relationship between two entities to reflect a business scenario.
- Identify when a one to one relationship exists between two entities.
- Read a relationship between two entities and validate it against a business scenario.
Unit 3: Adding Detail to the Model
- Identify the purpose of an attribute.
- Identify the diagramming conventions for attributes.
- Identify what an attribute is used for.
- Identify the format that an attribute must have.
- Identify if an attribute has more than one value for each entity instance.
- Identify if an attribute has attributes of its own.
- Identify what derived data is.
- Identify the reasons for not storing derived data.
- Identify what a domain is.
- Identify why a domain may be used.
- Identify when a domain is unnecessary.
- Identify what a unique identifier (UID) is used for.
- Identify when to use attributes as UIDs.
- Identify when to use relationships as UIDs.
- Identify when a relationship and an attribute are used to form a UID.
- Identify the UID for an entity using UIDs inherited from other entities.
- Identify when an entity may have multiple UIDs and the difference between Primary and Secondary UIDs.
- Identify the reasons why Many to Many (M:M) relationships exist.
- Identify when a M:M relationship should be resolved.
- Sequence the steps involved in resolving an M:M.
- Identify the options for allocating a UID to an Intersection entity.
Duration
8
Minimum Requirements
The CDROM version of this course requires:
- At least a 486DX 33Mhz CPU.
- Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
- At least 8MB RAM.
- At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
- At least a double speed CDROM drive.
- An MPC compliant sound card with attached speakers or headphones is recommended (Currently only the CDROM version supports audio).
- At least a 486DX 33Mhz CPU.
- Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
- At least 8MB RAM and 22MB available hard disk space or file server space.
- At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
Media
Serebra Learning Corporation 119 - 7565 132nd Street Surrey BC V3W 1K5 Canada
About The Training Provider: Serebra Learning Corporation
Serebra Learning Corporation - Serebra Learning Corporation provides technology-based training solutions through a combination of Cortex, its proprietary learning management system (LMS), and a curriculum catalog with over 1,825 current courseware titles. Founded in 1987 (as FirstClass Systems, with a name change to Serebra in 2001), Serebra has over sixteen years" experience delivering e-learning solutions to both...
