Mandatory Requirements Artefacts
In PrinceLite, Requirement engineering artefacts are at the heart of the process binding the process of project delivery together in an end-to-end manner. Requirements are often referred to as being 'high level'. The notion of 'high level' requirements implies a hierarchy. A hierarchy of requirements elicitation can be thought of as a relationship of specialisation. Each iteration is undertaken successively in different states of the project lifecycle. High level requirements inform scope and primarily satisfy senior managers regarding decisions to fund the project. Mid-level requirements representation verify the high level requirements and support the decision to continue funding a project from inception to elaboration. Low level requirements elaborate mid-level requirements and provide the detail to solution designers allowing a logical solution to be transformed into a physical design suitable for programmers.
Figure: Requirements are represented at different levels of detail (abstraction) and contained in artefacts that have owners.
The high and mid level requirements are owned by the Senior Responsible Owner (SRO). The PID may be of interest to the CEO depending on the importance of the project. The solution team (architects and designers) own the low level requirements. The business analyst owns the process of transforming the requirements from one layer of abstraction to another.
As a lightweight framework, PrinceLite emphasises a minimal set of artefacts. Any artefact that has a stakeholder is potentially valid, but the requirements artefact set, illustrated above [PID, BRS, SRS] is mandatory. In the above figure the Business analyst owning the transformation from the BRS to the SRS. The SRS representation may in fact be undertaken by a system analyst.