The Enterprise Context (12.5%, K3)

• Enterprise Architecture
  • Rationale for enterprise and business architecture
  • Definition of Enterprise Architecture domains
  • Structure of the Zachman framework (columns and rows)
• Business Architecture
  • Application of the Business Model Canvas
  • Identification and analysis of capabilities
  • Development of a value stream diagram
  • Use of capabilities in enabling value streams
• Customer and User Experience
  • Definitions of customer experience and user experience
  • Differentiation between customer experience and user experience

The Business Analysis Service Portfolio (7.5%, K3)

• Service Thinking and Value Propositions
  • Principles of service thinking and value co-creation
  • Concept and attributes of a value proposition
• Business Analysis Service Framework (BASF)
  • Definition of services within the BASF
  • Context and use of the BASF for requirements definition
• Project, Programme and Portfolio Management
  • Definitions of project, programme, and portfolio management
  • Relationship between requirements engineering and management
• Requirements Governance
  • Process of requirements governance using SIPOC
  • Relationship between IDEF0 controls and mechanisms
  • Agile/iterative change delivery and traditional/waterfall approaches

The Requirements Engineering Plan (15%, K4)

• Programme Manager, Project Manager, Business Architect
  • Roles and responsibilities of each role
• Terms of Reference for Requirements Engineering
  • Content of a terms of reference for requirements engineering
• Problem Definition and Problem Statements
  • Evaluation of problem statements
• The Outcome Frame
  • Explanation of the Outcome Frame
• Planning for Requirements Engineering
  • Importance of planning for requirements engineering
  • Stakeholder analysis using RACI
  • Relationship between requirements planning and governance
  • Content of a requirements engineering plan
  • Distinction between linear and agile software development approaches
• Estimating for Requirements Engineering
  • Top down, bottom up, and PERT estimation approaches

Engaging with Stakeholders (15%, K3)

• Relevance of Elicitation Techniques
  • Analysis using the cultural web
• Levels of Listening
  • Application of levels of listening
• Listening Barriers and Behaviors
  • Identification and application of listening barriers and behaviors
  • Explanation of questioning approaches
• Assertiveness
  • Definition of assertiveness

The Requirements Taxonomy (15%, K3)

• The Hierarchy of Requirements
  • Importance and application of hierarchy of requirements
  • Identification of Business Requirements (General and Technical)
  • Identification of Solution Requirements (Functional and Non-Functional)
  • Identification of transition and user interface requirements
  • Influence of business strategy and ethos on requirements
• The Business Use Case Diagram
  • Description and relation to requirements
  • Relationship between customer experience and requirements
• Prioritization Techniques
  • Application of MoSCoW and the Kano model

Non-Functional Requirements: Customer Experience Requirements (15%, K4)

• User Role Attributes and Personas
  • Identification, use, and analysis of user role attributes and personas
• Usability Requirements
  • Components of usability requirements
• Accessibility Requirements
  • Steps of the AEGIS Open Accessibility Framework
  • Principles of the Web Content Accessibility Guidelines (WCAG 2.1)
• Look and Feel Requirements
  • Definition of look and feel requirements
• Visualization Techniques
  • Identification of visualization techniques for non-functional requirements

Non-Functional Requirements: Service Quality Requirements (15%, K4)

• Rationale for Service Quality Requirements
  • Explanation of the rationale
• Performance Requirements
  • Elements of performance and definitions
• Backup and Recovery Requirements
  • Relationship between risk, business continuity, and backup
• Archiving and Deletion Requirements
  • Impact of legislation and compliance
• Maintainability and Reliability Requirements
  • Identification and description of maintainability and reliability
• Security and Access Requirements
  • Explanation and application of access permission and security requirements

Acceptance and Approval of Requirements (5%, K2)

• Quality Assurance for Requirements Engineering
  • Explanation and differentiation of quality assurance and control
• Analysis and Validation of Requirements Engineering Outputs
  • Importance of requirements analysis and validation
• Validation and the Requirements Engineering Plan
  • Relationship between planning and requirements quality
• Acceptance Testing
  • Relationship between requirements and the v-model
  • Application of ‘given’, ‘when’, ‘then’ extension to a user story

Professional Certificate in Advanced Requirements Engineering Course Prerequisites

• Prior work experience in software development or project management
• Basic understanding of systems engineering
• Familiarity with software requirements process
• Exposure to requirement modeling techniques
• Knowledge of requirement analysis, validation and documentation.
• Basic IT skills and proficiency in English.