Training
Provided by 123-CBT Computer Based Training
Course Overview
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.
Learn To:
- 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.
Content Emphasis
Skills-Based
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.
Total Learning Time
7 - 8 Hour(s)
Course Contents
Unit 1: Introduction to Relational Data Modeling
Duration: 3 Hour(s)
- 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
Duration: 2 - 3 Hour(s)
- 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
Duration: 2 Hour(s)
- 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.
Training Avaliability and Delivery
| This is primarily online training |  | This is an online eLearning or CBT training program |  | This program may be available on CD |  | Contact 123-CBT Computer Based Training for more information |
|
| Training Presented in: | English |
|
Related Keywords:
data modeling and warehousing
databases enterprise
n a
information technology
cd web
Training Program Details
--
About 123-CBT Computer Based Training - Training Provider
123-CBT Computer Based Training - 123-CBT offers discount pricing on top quality eLearning
programs from leading computer based training providers. Many of the training courses are available both online or on CD so that you can study at home at your own pace:
E-Learning available for
- ABAP 6.10
- Access 2003
- Acrobat 6.0
- ASP
- ASP.NET
- C
- Captivate 1.0
- Crystal Reports 8.5
- Crystal Reports v10
- Dreamweaver MX
-...
More Data Modeling and Warehousing Training from 123-CBT Computer Based Training
Click here for more information or to take this course
| 
