amitdusane.com Adobe Analytics Learning

Deliver and maintain › Solution Design Reference (SDR)

Module 19 of 21 Deliver and maintain

Solution Design Reference (SDR)

The document that decides the build

6 sections about 1 hr 13 min

  1. 01 What Is an SDR An SDR is not a list of variables. It is the design that shows how a business request becomes a report, held together by an ID that survives to sign-off.
  2. 02 Business Requirements Document The document that records what the business wants and refuses to say how it will be done. Requirement IDs, phases, out of scope, and real sign-off.
  3. 03 SDR Structure One solution, one ID, and a block of rows beneath it. The seven columns of an SDR, and why requirements rarely map one to one.
  4. 04 Variable Mapping The variable list, given the job it can actually do. Every slot including the empty ones, and why your copy will drift from the live one.
  5. 05 Developer Instructions The technical document is the SDR with eight more columns, not a second document. Rule types, data elements, and the one ordering rule that matters.
  6. 06 Validation and Sign-off Testing against solution IDs rather than against the site. Four statuses, dated cycles kept in the row, named owners, and how a project reaches an honest yes.

About this module

The design artifact that determines whether an implementation succeeds: requirements, structure, variable mapping, developer instructions, and sign-off.

Most implementations fail on paper long before anyone writes code. Somebody asks for a report, somebody else builds a variable, and the connection between the two lives in a conversation nobody wrote down.

The solution design reference is the document that prevents that. This module covers the whole chain: recording what the business asked for, turning each request into a numbered solution, mapping those solutions onto variables, writing instructions a developer can actually follow, and testing against them afterwards. Five workbooks come with it, filled in for a fictional retailer, so the shape is visible rather than described.

Next module 20. Testing and Debugging