Four-Day Business Information Analysis

Format:

Instructor led, with approximately 6 hours of exercise for the delegate to test each new tool or technique in the classroom environment.

Pre-requites:

NQF 3 / Matric and at least one years working experience from a business or systems development perspective. Computer Literacy.

Audience:

Analysts, Product Developers or any information systems or business professional actively involved in producing a business requirements definition or product development or process improvement / engineering .

Training Calendar & Registration Download Course Information

Course Description:

The emphasis of this four-day workshop is on the gathering and specifying of the Business Information. As data is typically global (i.e. shared by many within the organisation), information analysis is a critical task for any organisation. The inability to specify an organisation-wide set of data and their relationships can lead to mass redundancy of data and unsynchronized information as well as dead data (gathered, updated and never used). Communication between the Business Owner and the Business Analyst is obviously the most critical during the analysis stage. Business Information Analysis draws heavily on graphical as well as textual documentation (models) to assist in this critical gathering activity. Because we can’t see analysis (although we can easily see design and implementation aspects), we need models to help us convey the Business Requirements. Two widely accepted and applicable models for Information Analysis are Entity Relationship Diagrams and Data models which graphically represents an organisation’s stored data as Entities (cohesive groupings of facts), Relationships (associations between Entities) and Data Elements (business facts). The major focus of logical modeling is to derive a Business Event partitioned model that reflects the most customer-orientated, stable and maintainable view of the business data. This logical view of the Business Information will flow naturally into the Enterprise/organisation Information Model and into data design.

Format:

Instructor led, with approximately 6 hours of exercise for the delegate to test each new tool or technique in the classroom environment.

Pre-requites:

NQF 3 / Matric and at least one years working experience from a business or systems development perspective. Computer Literacy.

Audience:

Analysts, Product Developers or any information systems or business professional actively involved in producing a business requirements definition or product development or process improvement / engineering .

Training Calendar & Registration Download Course Information

Course Description:

The emphasis of this four-day workshop is on the gathering and specifying of the Business Information. As data is typically global (i.e. shared by many within the organisation), information analysis is a critical task for any organisation. The inability to specify an organisation-wide set of data and their relationships can lead to mass redundancy of data and unsynchronized information as well as dead data (gathered, updated and never used). Communication between the Business Owner and the Business Analyst is obviously the most critical during the analysis stage. Business Information Analysis draws heavily on graphical as well as textual documentation (models) to assist in this critical gathering activity. Because we can’t see analysis (although we can easily see design and implementation aspects), we need models to help us convey the Business Requirements. Two widely accepted and applicable models for Information Analysis are Entity Relationship Diagrams and Data models which graphically represents an organisation’s stored data as Entities (cohesive groupings of facts), Relationships (associations between Entities) and Data Elements (business facts). The major focus of logical modeling is to derive a Business Event partitioned model that reflects the most customer-orientated, stable and maintainable view of the business data. This logical view of the Business Information will flow naturally into the Enterprise/organisation Information Model and into data design.

Four-Day Business Information Analysis

Course Objectives:

After completing this course the delegate will be able to:

  • Start analysing in a structured approach and know what deliverables are required i.e. Process models, process specifications, Entity Relationship Diagrams, entity, relationship and data specifications and the data dictionary.
  • Which models are the most appropriate to use, flow charts, data flow diagrams (DFD), entity relationship diagrams (ERD), functional decomposition, object orientation, narrative text etc.
  • How to identify a process from stimulus to response (Organisational Events)
  • How to separate design issues from business issues
  • How to apply Quality Assurance to each deliverable
  • Use a systematic top down approach to information modelling
  • Normalise data to 3rd normal form
  • Develop a logical ERD
  • Understand what a repository is and why it’s important.
  • Identify the characteristics required from a case tool and understand the difference between a modelling tool and a case tool 
  • Develop a Business Requirements document that can be used as input to design (the Technical Specification / Functional Specification)

Course Outline:

  • A Common Platform of Understanding
  • Evolution of Systems Thinking
  • Identifying the Essential Business Data
  • The content of Information Analysis
  • The Goals of Information Analysis
  • The Essence of Every Organisation
  • Forming an Organisation’s Core Business
  • Forming the Business Policy Layer
  • Forming the Technology/Customer Interface Layer
  • How Organisations Should Grow by Replication
  • How Organisations Should Accomplish Strategic Growth
  • Dis-Covering the Real Business
  • Business Overgrowth
  • Business Archaeology
  • Business Processing and Data Overgrowth
  • Organisational/Systemic Overgrowth
  • Recognising Historical Wrong Turns
  • People and File Partitioning in Manual Systems
  • Computer, Program and Partitioning Data File Partitioning in Automated Systems
  • After-the-fact Quality Control
  • The Result of Historic Wrong Turns
  • The Nature of Systems
  • Fundamental Characteristics of Systems
  • Stimulus/Response Partitioning
  • The Need for Models
  • Specifying Business Requirements
  • Process-Oriented Models
  • Data-Oriented Models
  • The Complete Specification – The Organisation’s Repository
  • Overview of Information Analysis
  • Tools for the Information Analyst
  • Definition of an Information Model
  • Using ERDs to Model Design and Analysis Issues
  • Detailed View of Information Analysis Methodology
  • Separating Analysis/Design and Current/New Issues
  • Analysis of Entities
  • The Universal Entity Concept
  • How do we Form Entities?
  • Rules for Validating Entity Types
  • Entity-Type and Entity Occurrence
  • Discovering Entities  
  • The Flavours of Entities
  • Discovering Supertype and Subtypes
  • Specifying Optional/Mandatory Business Data Rules
  • Supertype/Subtype Rules
  • Analysis of Relationships
  • Defining Meaningful Relationships
  • Representing Relationship Cardinality
  • Relationship Type and Relationship Occurrence
  • Specifying Organisation-wide Relationship Connection Rules and Relationship Cardinality
  • Analysis of Data Elements
  • Definition of a Data Element (attribute)
  • Discovering Data Elements
  • Data Element Format, Content/Domain
  • Normalisation – Bottom Up Information Analysis
  • The Need for Attribution and Normalisation
  • The Benefits and Limitations of Normalisation
  • Organisational Event Modelling
  • Organisational Event Definitions
  • Classical Vs. Organisational Event Partitioning
  • Separating Organisation Events
  • Types Of Events
  • Business Event Partitioning Vs. Human or Computer Partitioning
  • Data Cohesion Vs. Data Conservation of Business Events
  • Understanding Event Primers
  • The Need for Process Analysis
  • The Task of the Information Analyst
  • Overview of Data Flow Diagrams
  • Encapsulating Business Event Memory
  • The Synergy of Process and Information Analysis
  • Business Event Driven Information Analysis
  • Modeling Analysis Data Store Redundancy
  • Forming the Organisation’s Information Model
  • Important Levels of the Information Model
  • Conservation of Data Elements, Data Entities, Relationships and Objects across the Organisation
  • Re-usability Via the Business Engineering Methodology
  • Access Path Diagramming
  • The Access Path Analysis Method
  • Forming a Logical Access Path Diagram (LAPD)
  • Mapping the Navigation Paths
  • Forward into Design
  • The Analysis Specification IS the Business
  • The Essential Corporate Library 
  • Engineering the Organisation

Who We Work With

  • AlexanderForbes
  • Rhodes
  • Bestmed
  • Anglo American
  • DataCentrix
  • Enviroserv
  • FirstRand
  • Sasol
  • FTP
  • MTN
  • Omnia
  • PEP
  • SABS
  • Sasol
  • StandardBank
  • SunCityResort