A requirements engineer is documenting the process for a new online food ordering system. The goal is to create a model that clearly shows the responsibilities of different actors (Customer, Kitchen, Delivery Driver) and the flow of activities from placing an order to final delivery. The model must be easily understood by non-technical stakeholders, such as restaurant managers. Which modeling approach and diagram type would be most effective for this purpose?
During a project to develop a control system for an automated warehouse, the development team is using an iterative process. Stakeholders are available for frequent feedback. However, there is a high degree of uncertainty about the optimal workflow for the robotic arms. The primary goal is to discover the most efficient operational logic through experimentation. Which RE process configuration is most suitable for this context?
A project team is developing a medical device for monitoring patient vitals. Regulatory standards require that every software feature must be traceable to a specific, approved stakeholder requirement, and every requirement must be linked to a set of test cases that verify its implementation. The project manager needs to produce a report for an audit. Which requirements management practice and work product are essential for fulfilling this regulatory demand?
A business analyst is writing requirements for a new CRM system. One of the requirements is stated as: 'The system should be fast.' Why does this requirement violate the quality criterion of being 'verifiable'?
During an elicitation workshop for a new banking application, the Head of Marketing requests a feature for 'gamified' user achievements. The Chief Security Officer states that this could introduce vulnerabilities and goes against the company's risk-averse policy. The requirements engineer identifies this as a conflict. According to the CPRE syllabus, which TWO of the following conflict types are most clearly represented in this scenario? (Select TWO)
True or False: In Requirements Engineering, the 'system boundary' defines the parts of the environment that are relevant for understanding the system, while the 'context boundary' separates the system itself from its environment.
A team is developing a smartphone app for tourists. The product owner wants to discover features that would surprise and delight users, which are not typically requested or expected. According to the Kano model, the team is trying to identify 'Delighters'. Which elicitation technique is most suitable for discovering this type of requirement?
**Case Study** A mid-sized regional airline, 'AirConnect', wants to develop a new mobile application for flight booking and management. Their current system is a web-only portal that is not mobile-friendly. The primary business goal is to increase direct bookings by 25% and improve customer satisfaction. The project team has identified several key stakeholder groups: travelers (end-users), marketing department, IT operations, and the company's executive board. The marketing team insists on a highly interactive, visually rich user interface with promotional pop-ups. The IT operations team is concerned about performance and the load on their legacy backend systems. The executive board has set a strict, non-negotiable deadline of 6 months for the first release. Given the tight deadline, the need to balance conflicting stakeholder interests (visuals vs. performance), and the fact that this is a customer-facing application for a broad, non-technical user base, the lead requirements engineer must choose an appropriate approach for validating the UI/UX requirements before development begins. Which validation technique would be most effective in this situation to quickly gather user feedback and align stakeholder expectations?
A project is creating a requirements specification document. The team has decided to create a central document that defines all context-specific terms, acronyms, and abbreviations to ensure a shared understanding among all stakeholders. What is this work product called?
A team is defining a life cycle model for their requirements. They need to represent the different stages a requirement can be in, such as 'Drafted', 'In Review', 'Approved', and 'Implemented'. Which diagram is most suitable for visualizing these states and the valid transitions between them?