|| BUSINESS INFORMATION MODELING
Business information requirements are best documented in a business object model. A business object model defines the concepts and terminology that will be used by the organization. Business Information Modeling is the precursor for data modeling and sets the foundation for designing stable, flexible data structures by placing the business users in the center of the data specification process. Business users are not experts on data; they are experts on the way their enterprise does business. Therefore, business object models are not based on data uses, data limitations, or data anything. They are based on the information business people need to know about the real-world objects that are important to them.
Because a business object model is a model of actual business objects and their relationships, it is a reflection of the business user’s image of the business. Only after this image is completed and agreed upon is the business object model converted into an efficient data model. This data model is later implemented as a populated data structure. Starting with a business object model yields a data structure that is:
- Stable - The structure is prepared for unanticipated queries.
- Flexible - New relationships and new objects can be added without altering the initial data structure.
- Intuitive - Users can efficiently find the data they need since the data structure matches their view of the world.
- Complete - Containing all the business objects and relationships (and therefore data) the users care about.
- Compact - Eliminating unnecessary redundant data and unmanaged data.
Data structures which are stable, flexible, intuitive, complete, and compact provide more value to an enterprise and require less resources for maintenance, support, training and enhancements.
Students of Advanced Strategies’ Business Information Modeling Course will return to work with the skills necessary to produce moderately complex object models in their actual work setting. Properly used, these models will form the basis for stable, flexible data structures.
|Fundamental Analysis Concepts
- What is Analysis?
- Business Aspects and Models
- Analysis vs. Design
- What Happens when Data Analysis is Inadequate?
|Fundamental Modeling Concepts
- Types of Facts
- Types of Models
- What Does the Model Represent?
- The Evolution of a Data Structure
|Fundamentals of Business Information Modeling
- Graphic Representation
|Object Modeling Approach
- How to Get Started
- Focus Statement
- Information Needs
- Fact Fragments
- Iterating the Model
- Entity Hierarchies
- Specific vs. Type Entities
- Associative Entities
- Entities with Multiple Relationships
- Recursive Relationships
- Multi-Member Links
- Relationship Roles
- Attributes vs. Relationships
- Derivable Attributes
- Repeating Attributes
- Attributes as Unique Identifiers
- Rules of Attribution
- Cardinality and Time
- Cardinality and Policy
- Cardinality Exceptions
- Consortium Cardinality
|Final Case Study
- Using the Focus Statement
- Entity/Relationship Diagramming
- Textual Descriptions
Who Should Attend:
Data Modelers, Systems and Business Analysts, Data Base Administrators and other individuals involved in analysis and design, including end-users.
Request It Now!