Physical, Mathematical, Computer and Life Sciences › Information Technology and Computer Sciences
This course equips learners with the skills to systematically analyse, document, and validate requirements for business systems and processes. Participants will learn to apply various techniques to elicit, prioritise, and manage requirements effectively, ensuring alignment with organisational goals and stakeholder needs.
Business analysts, systems analysts, project managers, and anyone involved in defining or managing requirements for projects or process improvements.
None — open enrollment.
Objectives:
• Define requirements analysis and its importance in systems development
• Understand the role of the business analyst
• Identify key stakeholders and their interests
• Differentiate between functional and non-functional requirements
Topics:
• Overview of systems development lifecycle
• Role and responsibilities of a business analyst
• Stakeholder identification and analysis
• Types of requirements: functional, non-functional, constraints
• Introduction to requirements engineering
Objectives:
• Describe various elicitation techniques
• Conduct effective interviews
• Facilitate workshops and focus groups
• Apply observation and document analysis
Topics:
• Interviewing techniques: structured, semi-structured, unstructured
• Workshop facilitation: brainstorming, JAD sessions
• Focus groups: planning and execution
• Observation methods: active, passive
• Document analysis: reviewing existing documentation
Objectives:
• Use surveys and questionnaires effectively
• Apply prototyping for requirements discovery
• Employ use cases and user stories
• Select appropriate elicitation techniques for different contexts
Topics:
• Survey and questionnaire design
• Prototyping: throwaway, evolutionary
• Use case diagrams and narratives
• User stories: format and acceptance criteria
• Technique selection criteria
Objectives:
• Write clear and concise requirements statements
• Structure a Business Requirements Document (BRD)
• Create a Software Requirements Specification (SRS)
• Apply standards like IEEE 830
Topics:
• Requirements writing guidelines: clarity, completeness, consistency
• BRD structure and content
• SRS components: introduction, overall description, specific requirements
• IEEE 830 standard overview
• Requirements traceability matrix
Objectives:
• Create Entity-Relationship Diagrams (ERDs)
• Define entities, attributes, and relationships
• Normalize data models
• Understand data dictionaries
Topics:
• ERD notation: Chen, crow's foot
• Entities, attributes, keys
• Relationships: one-to-one, one-to-many, many-to-many
• Normalization: 1NF, 2NF, 3NF
• Data dictionary components
Objectives:
• Develop Data Flow Diagrams (DFDs)
• Create flowcharts and activity diagrams
• Use Business Process Model and Notation (BPMN)
• Understand process decomposition
Topics:
• DFD levels: context, level 0, level 1
• Flowchart symbols and conventions
• Activity diagrams in UML
• BPMN basics: events, activities, gateways
• Process decomposition techniques
Objectives:
• Create class diagrams
• Develop sequence diagrams
• Use state machine diagrams
• Apply UML for requirements modeling
Topics:
• Class diagram notation: classes, attributes, methods, associations
• Sequence diagram: lifelines, messages, activation bars
• State machine diagrams: states, transitions, events
• UML overview and diagram types
• Case study: modeling a library system
Objectives:
• Perform requirements analysis: completeness, consistency, feasibility
• Validate requirements with stakeholders
• Use techniques like reviews and inspections
• Prioritize requirements using MoSCoW
Topics:
• Requirements analysis criteria
• Validation techniques: peer review, walkthrough, inspection
• Requirements prioritization: MoSCoW, Kano model
• Requirements sign-off process
• Managing requirements changes
Objectives:
• Establish a requirements management plan
• Use traceability matrices
• Manage requirements throughout the project lifecycle
• Handle requirements versioning and baselines
Topics:
• Requirements management plan components
• Traceability: forward, backward, bidirectional
• Requirements lifecycle: from elicitation to retirement
• Version control and baselines
• Tools for requirements management
Objectives:
• Identify stakeholder communication needs
• Develop a communication plan
• Manage stakeholder expectations
• Resolve conflicts and negotiate requirements
Topics:
• Stakeholder analysis: power/interest grid
• Communication planning: frequency, channels, formats
• Expectation management techniques
• Conflict resolution: win-win, compromise
• Negotiation skills for requirements
Objectives:
• Write effective user stories
• Prioritize and estimate user stories
• Manage product backlog
• Apply acceptance test-driven development (ATDD)
Topics:
• User story format: as a, I want, so that
• INVEST criteria for user stories
• Backlog grooming and prioritization
• Story points and planning poker
• ATDD: writing acceptance tests
Objectives:
• Decompose epics into user stories
• Organize themes and releases
• Create product roadmaps
• Use story mapping for backlog visualization
Topics:
• Epics vs. user stories
• Themes and release planning
• Product roadmap creation
• User story mapping: activities, tasks, stories
• Case study: e-commerce platform
Objectives:
• Elicit data requirements
• Define data quality rules
• Specify reporting and analytics needs
• Understand data governance basics
Topics:
• Data requirements elicitation: interviews, data profiling
• Data quality dimensions: accuracy, completeness, timeliness
• Reporting requirements: dashboards, KPIs
• Analytics requirements: descriptive, predictive, prescriptive
• Data governance principles
Objectives:
• Specify system interface requirements
• Understand API and service contracts
• Document data mapping and transformation rules
• Address non-functional requirements for integration
Topics:
• Interface requirements: input/output, protocol, format
• API specification: REST, SOAP
• Service contracts and SLAs
• Data mapping techniques
• Non-functional requirements: performance, security, reliability
Objectives:
• Identify security requirements
• Apply compliance requirements (POPIA, GDPR)
• Conduct threat modeling
• Specify authentication and authorization needs
Topics:
• Security requirements: confidentiality, integrity, availability
• Compliance frameworks: POPIA, GDPR, PCI-DSS
• Threat modeling: STRIDE, attack trees
• Authentication: password, MFA, SSO
• Authorization: RBAC, ABAC
Objectives:
• Elicit mobile-specific requirements
• Address usability and user experience
• Specify responsive design requirements
• Consider platform constraints
Topics:
• Mobile requirements: device, OS, screen size
• Usability heuristics and UX requirements
• Responsive design: breakpoints, layouts
• Platform constraints: iOS, Android, web
• Accessibility requirements (WCAG)
Objectives:
• Write testable requirements
• Create acceptance criteria
• Develop test cases from requirements
• Perform requirements-based testing
Topics:
• Testability criteria: unambiguous, measurable
• Acceptance criteria: given/when/then
• Test case design: equivalence partitioning, boundary value analysis
• Requirements traceability to tests
• User acceptance testing (UAT) planning
Objectives:
• Evaluate requirements management tools
• Use JIRA for requirements tracking
• Apply Confluence for documentation
• Explore other tools like IBM DOORS
Topics:
• Tool selection criteria: scalability, integration, cost
• JIRA: issues, epics, user stories
• Confluence: pages, templates, macros
• IBM DOORS: modules, links, baselines
• Comparison of tools: pros and cons
Objectives:
• Understand requirements in DevOps context
• Apply continuous requirements validation
• Use feature flags and A/B testing
• Integrate requirements with CI/CD pipelines
Topics:
• DevOps principles and requirements impact
• Continuous validation: automated acceptance tests
• Feature flags: toggling requirements
• A/B testing for requirements validation
• Requirements in CI/CD: versioning, traceability
Objectives:
• Apply all learned techniques to a real-world scenario
• Present requirements documentation
• Receive feedback and improve
• Review key concepts and prepare for assessment
Topics:
• Capstone project: from elicitation to specification
• Group presentation and peer review
• Feedback integration
• Course summary and key takeaways
• Assessment preparation and Q&A
The practicals allow learners to apply requirements analysis techniques in simulated and real-world scenarios. Through hands-on exercises, learners practice elicitation, modeling, documentation, and validation, reinforcing theoretical concepts and building competence in using industry-standard tools.
Each delegate is assessed continuously throughout the course via daily exercises, scored practical assignments, and a final summative test at the end.
Practical assignments are observed and scored against a rubric during the practical sessions. Each delegate's practical mark is averaged into a single 100% score and contributes 30% to the final total.
Every training day ends with a multiple-choice exercise scored out of 100%. The scores from each daily exercise are averaged across the duration of the course to produce a Daily Average mark, which contributes 20% to the final total.
On the last day a final summative test is written. It is a multiple-choice paper with multiple-answer questions: each question may have more than one correct option, and a single wrong selection on a question marks the entire question wrong — no partial credit. The final test is scored out of 100% and contributes 50% to the overall mark.
| Component | Out of | Weight |
|---|---|---|
| Practical Assignments (rubric-scored) | 100% | 30% |
| Daily Average (multiple choice) | 100% | 20% |
| Final Test (multi-answer multiple choice) | 100% | 50% |
| Final Total | — | 100% |
All marks are recorded on the AATICD LMS and visible to each learner under their account.
Sign in to the LMS, open your dashboard, and your certificates appear under My Certificates. Each entry has a View / Download button and a print option.
Group discounts apply automatically — the more delegates you enrol, the greater the saving. Discounts are calculated at 3% per 5 delegates, scaling up to 40% off for 100+ delegates.
| Delegates | Discount |
|---|---|
| 5 | 3% off |
| 10 | 6% off |
| 15 | 9% off |
| 20 | 12% off |
| 25 | 15% off |
| 30 | 18% off |
| 50 | 30% off |
| 75 | 35% off |
| 100 | 40% off |
3% discount per 5 delegates, up to 40% off for 100+ delegates. Contact us for a custom group quote.
Other Physical, Mathematical, Computer and Life Sciences courses at NQF level 6 learners on this page also viewed.
30-second guide
Type a keyword, NQF level or SAQA unit-standard ID in the search bar to see live matches across 3,000+ accredited courses. Filter by category, subfield and delivery mode.
Online · ask anything about AATICD
Answers come from the AATICD website.
For direct bookings call
+27 12 004 8389
or email
[email protected].