THE TECHNICAL DESIGN DOCUMENT | TDD
dlorenzolaguno17.github.io · 1,909 words · saved by 1 readers
This is a research about the Technical Design Document
I am Dani Lorenzo, student of the Bachelor’s Degree in Video Games by UPC at CITM. This content is generated for the second year’s subject Project 2, under the supervision of lecturer Ricard Pillosu. Index Introduction What is a Technical Design Document? The relation of the TDD with the GDD Sections of a Technical Design Document Core sections Features from the GDD Technical goals Technical risks Code style guidelines External libraries Code organization overview (UML) Branching policy Performance budgets Build delivery method Version list Delivery platform and requirements…
saved by
related reading
- Understanding Technical Design Document and Writing Guidekimi.ai
- Design Docs at Googleindustrialempathy.com
- Design Engineeringfloguo.com
- Writing a good design documentnews.ycombinator.com
- How to Write an Effective Software Design Documentrefactoringenglish.com
- Devouring Detailsdevouringdetails.com
- GitHub - google-labs-code/design.md: A format specification for describing a visual identity to coding agents. DESIGN.md gives agents a persistent, structured understanding of a design system.github.com
- Design Engineering at Vercel: What we do and how we do it - Vercelvercel.com
- DesEngs: Resources for Design Engineersdesengs.com
- About this guide | Google developer documentation style guide | Google for Developersdevelopers.google.com
- Design Engineeringmarcelochaman.com
- Khan Academy Early Product Development — Game designers vs. education researchers on unguided instructionklr.tumblr.com