Writing the solution design and the developer handover

Turning approved requirements into a solution design document and clear functional/technical handovers.

In this lesson

What a solution design covers
A developer handover that needs no meeting
Reviewing and validating delivered work

Key points

SDD: hosting, apps, structure, master data, processes, security, reports, integrations, migration, developments
Handover: why, story, criteria, fields, views, rules, security, data, tests
Add technical hints: model, method, view to extend
Validate against the approved requirement; keep the SDD current

Real-world example

A developer built a 'commission' field as a computed, non-stored field; reports by commission were impossible. The consultant's next handover specified 'stored, computed on invoice validation, groupable in reports, readable by sales managers only'. The rework disappeared.

Questions and answers

Name four sections of an SDD.

Any four of: hosting/edition, apps, company structure, master data, processes, security, reports, integrations, migration, developments.

What should change with an approved change request?

SDD, traceability matrix and tests, together.

Read the full lesson, worked example and quiz