Advanced Business Information Analysis
The emphasis of this Advanced Business Information Analysis module 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 sell as dead data (gathered, updated and never used). This is regardless of any latest database implementation or stringent manual procedures.
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 of Entity Relationship Diagrams and Data models which graphical represents an organisation’s stored data as Entities (cohesive groupings of facts), Relationships (associations between Entities) and Data Elements (business facts).
A real world case study is used to show the importance of deriving a logical view of data and their relationships in an organisation. This logical view removes any design characteristics for folders, file cabinets, 3-part forms and sequential files, network/hierarchical/relational databases, mass storage devices, etc. That may be place today so that they do not corrupt the new design of stored data.
The major focus of logical modelling is to derive a Business Value Stream 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.
Advanced Business Information Analysis. Learning Outcomes
After completing this module the student 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 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 is a repository?” and why they are 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)
Estimated Study Timings
9 hours of study
1 hours of self-assessment
4 hours of Case Study
5 hours for the Assignment
- 12 months working experience either IT or business operations.
- Computer literacy.
- Introduction of Business Analysis
- Introduction to Business Information Analysis.It’s important that when we communicate with one another and with our users that we have a common understand of terms.
- Information Analysis Models. The most commonly used information models and their uses
- Overview of Information Analysis. The deliverables, methods, models and definitions for information analysis.
- Case Study.
- Recognising Historical Wrong Turns. By understanding where we have gone wrong in the past, we can prevent the same mistakes from taking place in the future
- Analysis of Entities. Entities are logical groupings of data that support the business process and represent the stored information needs of the organisation.
- Case Study.
- The Flavour of Entities. To gain a deeper understanding of information analysis, the business analyst can categorise entities.
- Case Study
- Analysis of Relationship. By uncovering the relationship between entities, the business analyst will discover, underlying business rules, that may not be evident by analysing processes on their own.
- Analysis Data Element. By analysing the data elements, the business analyst provides the organisation their own dictionary, which defines the essential business terms.
- Case Study
- Data Normalisation.This is a technical method, which ensures that all the essential data is grouped corrected in their entities and that the correct natural key of that data is identified and documented.
- Case Study
- Total Quality Management. By ensuring that each data element is created, retrieved, updated and delete, we can guarantee that total quality management within our systems.
IIBA BABOK alignment
BABOK KNOWLEDGE AREA
- Task: Prepare for Elicitation
- Task: Conduct Elicitation
- Task: Document Elicitation
- Task: Confirm Elicitation Results
- Requirements Analysis
- Task: Prioritize Requirements
- Task: Organize Requirements
- Task: Specify and Model Requirements
- Task: Verify Requirements
- Task: Validate Requirements
- Data Dictionary and Glossary
- Data Modelling
- Document Analysis
- Interface Analysis
- Requirements Workshop
advanced business information analysis