BCS Professional Certificate in Advanced Requirements Engineering Practice Test

• Define the principles of service thinking and value co-creation
• Explain the concept and attributes of a value proposition

• Define the services within the BASF
• Explain the context and use of the BASF in relation to requirements definition service delivery

• Define project, programme and portfolio management and explain their relationships
• Define the relationship between requirements engineering and PPM

• Explain requirements governance using SIPOC
• Explain IDEF0 controls and mechanisms in requirements governance
• Explain RE in agile/iterative approaches using product backlog
• Explain RE in traditional/waterfall approaches using requirements catalogue or BRD

Define the roles and responsibilities of Programme Manager, Project Manager and Business Architect

Describe the content of a terms of reference for requirements engineering

Evaluate a problem statement

Explain the Outcome Frame

• Illustrate the importance of RE planning
• Analyse stakeholders using the RACI technique
• Explain the relationship between requirements planning and governance
• Describe the content of a requirements engineering plan
• Distinguish between linear and agile software development approaches

Describe top-down, bottom-up and PERT approaches to estimation

Analyse a given scenario using the cultural web

Apply the levels of listening to a given scenario

Identify listening barriers and behaviours

Define assertiveness

• Explain the importance and application of the hierarchy of requirements
• Identify Business Requirements (General and Technical)
• Identify Solution Requirements (Functional and Non-Functional)
• Identify transition and user interface requirements
• Explain the influence of business strategy on requirements
• Explain the influence of business ethos and core values on requirements

• Describe the Business Use Case Diagram
• Describe how BUCD relates to requirements
• Explain the relationship between customer experience and requirements using the Business Use Case

Apply MoSCoW and the Kano model to prioritise requirements

• Discuss the importance of decomposing requirements and their priorities
• Identify the difference between goal and functional decomposition

• Explain the rationale for requirements traceability
• Describe the advantages of requirements reuse
• Explain the rationale for requirements patterns

• Identify user role attributes for a given scenario
• Illustrate the use of the persona technique
• Apply user role analysis

Explain the components of usability requirements including Learnability, Satisfaction, Efficiency, Memorability, and Errors or error protection

• Define the six steps of the AEGIS Open Accessibility Framework
• Identify and apply the key principles of WCAG 2.2

Define look and feel requirements

Identify visualisation techniques to elicit non-functional requirements

Explain the rationale for service quality requirements

Define the elements of performance: Speed of response, Scalability, Longevity, Availability, Capacity, Accuracy

Describe the relationship between business risk, business continuity, and backup and recovery strategy

Describe the impact of legislation and compliance on archiving and deletion requirements

• Analyse a given situation to identify maintainability and reliability requirements
• Describe the relationship between maintainability and reliability requirements

• Explain access permission requirements and documentation techniques
• Explain security requirements and elicitation techniques
• Explain and apply the misuse case approach

• Explain requirements quality assurance
• Distinguish between quality assurance and quality control

• Explain the importance of requirements analysis
• Explain the importance of requirements validation

Describe the relationship between requirements planning and requirements quality

• Describe the relationship between requirements and the V-model
• Apply the 'given', 'when', 'then' extension to a user story