Technical Design Document (TDD)

From GM-RKB
(Redirected from Technical Design Document)
Jump to navigation Jump to search

A Technical Design Document (TDD) is a comprehensive document for a software system.

  • Context:
    • It can detail the architecture, components, modules, interfaces, and data flow of the system.
    • It serves as a blueprint for the development team, providing guidance and clarity on the intended design and functionality.
    • It helps in ensuring that all stakeholders have a clear understanding of the system's technical requirements and constraints.
    • It facilitates communication among team members and can be used for project estimation, planning, and management.
    • It can be updated throughout the development process to reflect changes in the system design or requirements.
    • ...
  • Example(s):
  • See: Software Requirements Specification, Software Architecture Document, System Design Document, Project Management Plan.


References

2021

  • https://uit.stanford.edu/pmo/technical-design
    • QUOTE: A Technical Design Document (TDD) is written by the development team and describes the minute detail of either the entire design or specific parts of it, such as:
      • The signature of an interface, including all data types/structures required (input data types, output data types, exceptions)
      • Detailed class models that include all methods, attributes, dependencies, and associations
      • The specific algorithms that a component employs and how they work
      • Physical data models that include attributes and types of each entity/data type
    • In short, the functional design specifies how a program will behave to outside agents and the technical design describes how that functionality is to be implemented in code. The Technical Design Document must be approved by the IT project sponsor before proceeding to the development/integration phase.