AS A COMPLETION REQUIREMENT BECAUSE OF THE ECQ (Enhanced Community
Quarantine) I am asking you all to make a module using the 3 Books I have
forwarded at the beginning of the Semester in the GC . Below is outline for the
said module. Follow the module and make the exercises as necessary as if you
are making your own book.
Final paper should be formatted as:
Paper size: Short bond paper (8.5 X 110
Font: Calibri
Font size: 12
Margins : Normal
Submission: day after classes resume after ECQ lifted
Module 1 - Introduction to the BA Role
What is a Business Analyst?
The evolving role of the Business Analyst
The BA roadmap - different ‘levels’ of business analysis
The basic rules of Business Analysis
IT and non-IT change
Exercise 1.1 – Delegates work in teams to define and document a set of requirements for a ‘simple’
project
Module 2 – Project Definition and Scoping
Aspects of a project
The importance of understanding and defining objectives and scope and identifying stakeholders
Projects phases and deliverables
The role of the BA across the project lifecycle
Project approaches (and how they affect the BA) – Waterfall, Agile, Iterative, Incremental
Exercise 2.1 – Delegates define a list of measurable project objectives and initial scoping questions.
Module 3 - Interviewing and Fact Finding
The user perception of IT and projects.
How to interview different types of user and how to capture and assimilate information.
How to use workshops effectively for requirements gathering.
Exercise 3.1 – Delegates work in teams to perform role-play interviews of 3 different stakeholders:
- Project Sponsor (Director level)
- Subject Matter Expert (Operational Manager)
- IT Manager
Module 4 - Requirements Definition
What are requirements, why they need to be defined and different techniques for documenting
requirements
Types of requirement including Business, Functional and Non-Functional
The importance of defining requirements at a high and low level of detail
The difference between requirements and solutions
Where requirements come from and how to identify them
How to work with business stakeholders to drive out high quality requirements
Requirements problems
Exercise 4.1 – delegates review a set of requirements to categorise them into different types of
requirement
Exercise 4.2 – delegates work in teams to scope a piece of project work and also produce an initial set of
high-level functional and non-functional requirements.
Exercise 4.3 – delegates are asked to identify and document a set of high-level functional requirements
and non-functional requirements from the case study
Module 5 - Process Modelling
Examines business process modelling and why and when it should be used
Introduces the industry standard process modelling technique - BPMN
Diagram levelling (how much detail to show in a diagram)
Process modelling as a requirements definition tool
Exercise 5.1 – delegates practise BPMN techniques using a simple scenario
Exercise 5.2 – delegates work in teams to produce an ‘as-is’ swim-lane diagram from the case study
Module 6 - Data Modelling
Why and when the BA should do data modelling.
How to build entity relationship diagrams and define attributes.
Exercise 6.1 – delegates work with the instructor to develop an entity relationship diagram from the
case study
Exercise 6.2 – delegates identify and define attributes for the case study entities
Module 7 – Ensuring Requirements Quality
Development of Use Cases and scenarios
Requirements quality criteria
Exercise 7.1 - delegates work with the instructor to develop a use case diagram
Exercise 7.2 – delegates work with the instructor to develop a use case description
Exercise 7.3 – delegates work in teams to produce a use case description from the case study
Exercise 7.4 – delegates review a set of requirements against defined quality criteria
Module 8 - Managing Delivery
Getting to solutions - the role of the BA beyond the requirements definition phase
Defining detailed requirements – how much detail do you need?
Identifying business impact
Supporting business implementation
Exercise 8.1 – delegates develop a set of detailed requirements based on high-level requirements from
an earlier exercise and interviewing the business stakeholder
Module 9 – Requirements Engineering Techniques
Production of a Requirements Catalogue
Requirements Databases and CASE tools
Knowledge Types and Investigative Techniques
Prototyping
Structured Walkthroughs
Requirements Management
Exercise 9.1 – delegates work in teams to prototype screens from the case study
Exercise 9.2 – delegates decide on the elicitation techniques to use in a number of business situations
Exercise 9.3 – delegates perform a structured walkthrough of the use case descriptions produced during
Exercise 7.3