Kravpresentasjon

Kravpresentasjon is the process of presenting and validating the set of requirements for a project or system to stakeholders and the development team. It is a core activity in requirements engineering, bridging elicitation and design by translating collected information into a form that can be reviewed and approved. The goal is to establish a common understanding of what the system should do, under which constraints, and with what level of quality.

A kravpresentasjon typically covers the project scope and objectives, functional requirements that describe specific behaviours, and non-functional requirements such as performance, reliability, security, and usability. It often includes use cases or user stories, acceptance criteria, data interfaces, system interfaces, constraints, and dependencies. The presentation may include a high-level architecture overview, process flows, and, where relevant, prototypes or diagrams. Deliverables commonly associated with kravpresentasjon are a requirements specification, a slide deck for stakeholder review, and a requirements traceability matrix.

The activity is usually conducted after requirements elicitation and analysis and before design and implementation. In traditional projects, it ends with formal sign-off; in agile environments, it supports ongoing refinement and backlog maintenance. Key participants are a business analyst or requirements engineer, product owner, project manager, developers, testers, and representative stakeholders.

Common risks include ambiguity, incomplete coverage, conflicting requirements, and scope creep. Mitigation strategies include structured reviews, validation against business goals, stakeholder walkthroughs, and the use of traceability and acceptance criteria.