Requirements Levels & Work Products (by SDLC phase)

Alignment [Business Requirements] : Problem / Opportunity Statement Business Objectives Business Context Diagram and System Context Diagram Conceptual Data Model and Subject Areas (for data centric solutions) Business Processes Stakeholder Needs Critical Success Factors Identification and Prioritization of Features

Solution Scoping [Solution Requirements] : Information Requirements Information Requirements visualizations, including Logical Data Model and Facsimiles Elaboration of Business Processes, including To Be Process Maps Business Rules Non-Functional Requirements, including Capacity Requirements Identification and Prioritization of Epics (Functions)

Elaboration [Functional Requirements for Epics (Functions or Use Cases) ]: Epic (Function) Information Requirements, including Input, Output, and Data Update requirements Identification and elaboration of the Business Rules the Epic (Function) must enforce Activity Diagram depicting high level logical flow for the Epic (Function) Identification and Prioritization of User Stories for the Epic (Function) UI / UX Design – Front End Application

Elaboration of User Stories, including Acceptance Criteria (for Agile Development)

Requirements have different level of

granularity. As you progress through the

Solution Development Lifecycle, the level of granularity increases.

Primary Requirements Work Products (by SDLC phase)

Iterative

Can be iterative

Requirements Work Products by Solution Development Lifecycle Phase

Requirements Work Products - Traceability

This diagram illustrates the vertical traceability for requirements work products. Vertical Traceability traces the requirements work product artifacts across the Solution Development Lifecycle. It helps to ensure all requirements are accounted for in the solution (i.e., completeness of the solution) and that all development traces back to a requirement (i.e., no scope creep).

The information contained in this presentation is from the guide “Requirements for an MDM Solution”. While the focus of the guide is Master Data Management (MDM) solutions, requirements levels and work products are similar, regardless of the type of solution. What differs is the approach, the emphasis of specific activities, and the content of work products.

The focus of the guide is to highlight a proven approach for requirements gathering and documentation for Master Data Management solutions. If you would like more information about the guide, refer to this article.

Both Paperback and Kindle versions of the guide are available from Amazon.