Project Toolkit

Design

Design

Creating the detailed design for the solution based on requirements.

Design

The design phase translates requirements into a detailed specification of how the solution will be built.

Purpose

Design activities ensure:

  • Requirements are translated into buildable specifications
  • Technical approach is defined and agreed
  • Risks are identified early
  • Build team has clear guidance
  • Solution is fit for purpose

Design Levels

flowchart LR A[High-Level
Design] --> B[Detailed
Design] B --> C[Technical
Specifications] C --> D[Build] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D blue
Level Description Output
High-Level Design Overall architecture and approach Architecture document
Detailed Design Component-level specifications Design documents
Technical Specs Implementation details Build specifications

Design Activities

Activity Purpose
Architecture design Define overall structure
Component design Specify individual components
Interface design Define how components interact
Data design Structure data models
Security design Address security requirements
UX/UI design Define user experience

Design Inputs

Input Source
Business requirements Requirements documentation
Functional requirements Solution specifications
Non-functional requirements Performance, security, etc.
Constraints Technical, budget, timeline
Standards Organisational guidelines
Existing systems Integration requirements

Design Outputs

Output Description
Architecture document High-level solution structure
Design specifications Detailed component designs
Data models Database and data structures
Interface specifications API and integration designs
Security design Security controls and measures
UI/UX designs Wireframes, mockups, prototypes

Design Principles

  1. Keep it simple - Avoid unnecessary complexity
  2. Design for change - Build in flexibility
  3. Reuse where possible - Leverage existing components
  4. Consider non-functionals - Performance, security, scalability
  5. Document decisions - Record rationale for choices
  6. Validate early - Review designs before building

Design Review

Before proceeding to build, validate design through:

Review Type Focus
Peer review Technical accuracy
Architecture review Standards compliance
Security review Security requirements
Business review Requirements coverage

Common Pitfalls

Pitfall Mitigation
Over-engineering Focus on actual requirements
Under-specifying Provide enough detail to build
Ignoring NFRs Address non-functional requirements
No traceability Link design to requirements
Skipping reviews Always validate before build

Design Checklist

  • Requirements understood and documented?
  • Architecture approach defined?
  • Components identified and specified?
  • Interfaces designed?
  • Data model complete?
  • Security addressed?
  • Non-functional requirements covered?
  • Design reviewed and approved?
  • Build team briefed?
Last updated: 13 January 2026
Themes

Delivery

Technical