Business Information Analysis – 4 Days
The emphasis of this four-day Business Information Analysis 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 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 modeling 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.
Analyst, Product Developers or any information systems or business professionals actively involved in producing a business requirements definition or product development or process improvement / engineering. No Information Technology (IT) experience required.
NQF 3 / Matric and at least one years working experience from a business or systems development perspective. Computer Literacy.
Instructor led, with approximately 6 hours of exercise for the delegate to test each new tool or technique in the classroom environment. The case study takes the delegate through the 4 stages of information analysis i.e. as is design, as is analysis, to be analysis, to be design
After completing this workshop 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 Value Streams)
- 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
- Understand what is ‘analysis paralysis’ and how to ensure it doesn’t set in.
- Develop a Business Requirements document that can be used as input to design (the Technical Specification / Functional Specification)