Requirements Analysis
Requirements analysis from a business perspective means analyzing the business context and, based on that, identifying functional needs. Important points of attention are:
- Research skills to create a solid understanding of the situation, taking into account the wishes of different stakeholders
- Interview skills as part of the research process
- Documentation of requirements in language or visualizations that are understandable for users, including:
- MoSCoW prioritization scheme
- Process descriptions, for example in BPMN
- Writing user stories
- Description of the data architecture, for example using ERD
- Use cases
- Creating clickable demos
A requirements analysis is also essential for communicating with team members and stakeholders: clear requirements give everyone direction and make realistic planning possible. A digital business engineer contributes to the definition of non-functional requirements to a limited extent. These differ per technological solution and are elaborated further in other BOKSA documents.
Starting Points
Many elements of requirements analysis are described on separate pages in this BOKSA. The links below refer to topics that are only addressed here:
Key Points
- You demonstrate the ability to identify user and stakeholder needs, for example by conducting needs analysis (interviews, surveys, or a workshop) and translating the results into concrete requirements.
- You formulate clear requirements in a recognized form such as user stories with acceptance criteria, which are traceable to the business needs and technical constraints.
- You make a well-founded distinction in the priority of different requirements, considering factors like business value, technical dependencies, and security implications.
- You show iteration, for example by refining or prioritizing requirements after a feedback round or after testing initial implementations.