[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-168200-en":3,"doc-seo-168200-105":30,"detail-sidebar-cat-1-en-105":92},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":11,"category_id":12,"category_name":13,"doc_title":14,"doc_description":15,"doc_content":16,"file_id":17,"file_url":18,"file_type":19,"file_size":20,"view_count":4,"is_deleted":4,"is_public":11,"is_downloadable":11,"audit_status":11,"page_count":21,"language":22,"language_code":23,"site_id":24,"html_lang":23,"table_of_contents":25,"faqs":26,"seo_title":27,"seo_description":15,"update_tm":28,"read_time":29},168200,137441390410,"Hazel","https://ap-avatar.wpscdn.com/avatar/2000252f4ab5702993?_k=1776741390130283984",1,11,"Presentations","Technical Design Document - Issue 1 - Project template guidance","Technical Design Document template for IDA Projects, providing structured guidance for management and technical staff working with client or supplier teams. The document describes purpose, scope, intended use, and a repeatable template approach to producing project-specific technical design documents, including instructions for adapting boilerplate and removing italic guidance text once written. It outlines an IDA reference architecture, system overview and context, design methods and standards, documentation and naming conventions, programming and tooling standards, decomposition description, and a software requirements traceability matrix with document control outputs.","\u0013 DOCPROPERTY \"Project\" \\* MERGEFORMAT \u0014Template for IDA Project\u0015 (\u0013 DOCPROPERTY \"Proj Id\" \\* MERGEFORMAT \u0014Project Id\u0015)\n\u0013 DOCPROPERTY \"Contract\" \\* MERGEFORMAT \u0014Template for specific development\u0015 (\u0013 DOCPROPERTY \"Contr Id\" \\* MERGEFORMAT \u0014Contract Id\u0015)\n\u0013title  \\* mergeformat \u0014Technical Design Document\u0015\n\u0013 DOCPROPERTY \"Version\" \\* MERGEFORMAT \u0014Issue 1\u0015\nTABLE OF CONTENTS\n\u0013 TOC \\o \"1-2\" \\t \"Doc control first,1,Doc control other,1,Preface 1,1,Preface 2,2\" \u00140\tPreface\t\u0013 PAGEREF _Toc504386205 \\h \u00141\u0015\n0.1\tPurpose of this document\t\u0013 PAGEREF _Toc504386206 \\h \u00141\u0015\n0.2\tUse of this document\t\u0013 PAGEREF _Toc504386207 \\h \u00141\u0015\n0.3\tOverview\t\u0013 PAGEREF _Toc504386208 \\h \u00142\u0015\n0.4\tBasis of this Document\t\u0013 PAGEREF _Toc504386209 \\h \u00142\u0015\n0.5\tA Reference Architecture for the IDA Programme\t\u0013 PAGEREF _Toc504386210 \\h \u00143\u0015\n0.6\tSpecific Design Considerations\t\u0013 PAGEREF _Toc504386211 \\h \u00143\u0015\n1\tIntroduction\t\u0013 PAGEREF _Toc504386212 \\h \u00145\u0015\n1.1\tPurpose\t\u0013 PAGEREF _Toc504386213 \\h \u00145\u0015\n1.2\tScope\t\u0013 PAGEREF _Toc504386214 \\h \u00145\u0015\n1.3\tDefinitions, Acronyms and Abbreviations\t\u0013 PAGEREF _Toc504386215 \\h \u00145\u0015\n1.4\tReferences\t\u0013 PAGEREF _Toc504386216 \\h \u00146\u0015\n1.5\tOverview\t\u0013 PAGEREF _Toc504386217 \\h \u00146\u0015\n2\tSystem Overview\t\u0013 PAGEREF _Toc504386218 \\h \u00147\u0015\n2.1\tSystem Characteristics\t\u0013 PAGEREF _Toc504386219 \\h \u00147\u0015\n2.2\tSystem Architecture\t\u0013 PAGEREF _Toc504386220 \\h \u00147\u0015\n2.3\tInfrastructure Services\t\u0013 PAGEREF _Toc504386221 \\h \u00149\u0015\n3\tSystem Context\t\u0013 PAGEREF _Toc504386222 \\h \u001410\u0015\n4\tSystem Design\t\u0013 PAGEREF _Toc504386223 \\h \u001411\u0015\n4.1\tDesign Method and Standards\t\u0013 PAGEREF _Toc504386224 \\h \u001411\u0015\n4.2\tDocumentation Standards\t\u0013 PAGEREF _Toc504386225 \\h \u001412\u0015\n4.3\tNaming conventions\t\u0013 PAGEREF _Toc504386226 \\h \u001413\u0015\n4.4\tProgramming Standards\t\u0013 PAGEREF _Toc504386227 \\h \u001413\u0015\n4.5\tSoftware development tools\t\u0013 PAGEREF _Toc504386228 \\h \u001413\u0015\n4.6\tOutstanding Issues\t\u0013 PAGEREF _Toc504386229 \\h \u001414\u0015\n4.7\tDecomposition Description\t\u0013 PAGEREF _Toc504386230 \\h \u001414\u0015\n5\tComponent Description\t\u0013 PAGEREF _Toc504386231 \\h \u001415\u0015\n5.1\tComponent Identifier\t\u0013 PAGEREF _Toc504386232 \\h \u001416\u0015\n6\tSoftware Requirements Traceability Matrix\t\u0013 PAGEREF _Toc504386233 \\h \u001419\u0015\nDocument Control\t\u0013 PAGEREF _Toc504386234 \\h \u001420\u0015\nDocument Signoff\t\u0013 PAGEREF _Toc504386235 \\h \u001420\u0015\nDocument Change Record\t\u0013 PAGEREF _Toc504386236 \\h \u001420\u0015\n\u0015\n0\tPreface\n0.1\tPurpose of this document\nThis document is a generic \u0013title  \\* mergeformat \u0014Technical Design Document\u0015 document for use by IDA Projects. It provides guidance and template material which is intended to assist the relevant management or technical staff, whether client or supplier, in producing a project\u001especific \u0013title  \\* mergeformat \u0014Technical Design Document\u0015 document. It is also useful background reading for anyone involved in developing or monitoring the IDA Management System (IDA\u001eMS).\n0.2\tUse of this document\nThis Preface is addressed to the users of this generic document and is not meant to be retained in any project\u001especific \u0013title  \\* mergeformat \u0014Technical Design Document\u0015 documents based on it.\nThe remaining sections (numbered 1, 2, 3,…) constitute a template that should be used to construct the project-specific \u0013title  \\* mergeformat \u0014Technical Design Document\u0015 document.\nText in normal case is in the most part “boilerplate” that can be retained, amended or deleted in the document.\nText in italics provides instructions on how to complete a section and should be removed once the section is written.\nThe template should be used pragmatically, that is - where a section is not relevant it should be omitted. Conversely, the material contained in this document is not necessarily exhaustive; if there is a subject that is relevant to the IDA Project, but is not included in this document, it should still be included.\nThis document has been prepared using MS Word 97.  The following variables are currently recorded as File “Properties” under MS Word.  They may be modified by that means or overwritten directly at each occurrence in the document, at the discretion of the user.\n0.3\tOverview\nThis preface is for information only","cbCaicsvVgsGYIDA","https://ap.wps.com/l/cbCaicsvVgsGYIDA","doc",116224,21,"English","en",105,"# Preface\n## Purpose of this document\n## Use of this document\n## Overview\n## Basis of this Document\n## A Reference Architecture for the IDA Programme\n## Specific Design Considerations\n# Introduction\n## Purpose\n## Scope\n## Definitions, Acronyms and Abbreviations\n## References\n## Overview\n# System Overview\n## System Characteristics\n## System Architecture\n## Infrastructure Services\n# System Context\n# System Design\n## Design Method and Standards\n## Documentation Standards\n## Naming conventions\n## Programming Standards\n## Software development tools\n## Outstanding Issues\n## Decomposition Description\n# Component Description\n## Component Identifier\n# Software Requirements Traceability Matrix\n# Document Control\n# Document Signoff\n# Document Change Record","[{\"question\":\"What is the purpose of this Technical Design Document template for IDA Projects?\",\"answer\":\"It provides guidance and template material to help relevant management and technical staff produce project-specific technical design documents, and supports background reading for those involved in developing or monitoring the IDA Management System.\"},{\"question\":\"How should users adapt the template to create a project-specific document?\",\"answer\":\"Use the remaining numbered sections as a template, retaining, amending, or deleting boilerplate text as needed and removing italic instructions once each section is written.\"},{\"question\":\"What key technical areas does the template cover?\",\"answer\":\"It includes reference architecture, system overview and context, system design methods and standards, documentation and naming conventions, programming standards and tools, decomposition description, and a software requirements traceability matrix.\"}]","Technical Design Document - Issue 1 - Project template guidance | DOC",1788227307,7,{"code":4,"msg":31,"data":32},"ok",{"site_id":24,"language":23,"slug":33,"title":14,"keywords":34,"description":15,"schema_data":35,"social_meta":87,"head_meta":89,"extra_data":91,"updated_unix":28},"technical-design-document-issue-1-project-template-guidance","",{"@graph":36,"@context":86},[37,54,69],{"@type":38,"itemListElement":39},"BreadcrumbList",[40,44,48,51],{"item":41,"name":42,"@type":43,"position":11},"https://docshare.wps.com","Home","ListItem",{"item":45,"name":46,"@type":43,"position":47},"https://docshare.wps.com/template/","Template",2,{"item":49,"name":13,"@type":43,"position":50},"https://docshare.wps.com/template/presentations/",3,{"item":52,"name":14,"@type":43,"position":53},"https://docshare.wps.com/template/technical-design-document-issue-1-project-template-guidance/168200/",4,{"url":52,"name":14,"@type":55,"author":56,"headline":14,"publisher":58,"fileFormat":61,"inLanguage":23,"description":15,"dateModified":62,"datePublished":63,"encodingFormat":61,"isAccessibleForFree":64,"interactionStatistic":65},"DigitalDocument",{"name":9,"@type":57},"Person",{"url":41,"name":59,"@type":60},"DocShare","Organization","application/octet-stream","2026-09-02","2026-09-01",true,{"@type":66,"interactionType":67,"userInteractionCount":47},"InteractionCounter",{"@type":68},"ViewAction",{"@type":70,"mainEntity":71},"FAQPage",[72,78,82],{"name":73,"@type":74,"acceptedAnswer":75},"What is the purpose of this Technical Design Document template for IDA Projects?","Question",{"text":76,"@type":77},"It provides guidance and template material to help relevant management and technical staff produce project-specific technical design documents, and supports background reading for those involved in developing or monitoring the IDA Management System.","Answer",{"name":79,"@type":74,"acceptedAnswer":80},"How should users adapt the template to create a project-specific document?",{"text":81,"@type":77},"Use the remaining numbered sections as a template, retaining, amending, or deleting boilerplate text as needed and removing italic instructions once each section is written.",{"name":83,"@type":74,"acceptedAnswer":84},"What key technical areas does the template cover?",{"text":85,"@type":77},"It includes reference architecture, system overview and context, system design methods and standards, documentation and naming conventions, programming standards and tools, decomposition description, and a software requirements traceability matrix.","https://schema.org",{"og:url":52,"og:type":88,"og:title":14,"og:site_name":59,"og:description":15},"article",{"robots":90,"canonical":52},"index,follow",{"doc_id":7,"site_id":24},{"code":4,"msg":5,"data":93},[94,97,102,107,112,117,122,127,131],{"id":12,"doc_module":11,"doc_module_name":46,"category_name":13,"show_sort_weight":95,"slug":96},90,"presentations",{"id":98,"doc_module":11,"doc_module_name":46,"category_name":99,"show_sort_weight":100,"slug":101},12,"Resumes",80,"resumes",{"id":103,"doc_module":11,"doc_module_name":46,"category_name":104,"show_sort_weight":105,"slug":106},14,"Invoices",70,"invoices",{"id":108,"doc_module":11,"doc_module_name":46,"category_name":109,"show_sort_weight":110,"slug":111},15,"Posters",60,"posters",{"id":113,"doc_module":11,"doc_module_name":46,"category_name":114,"show_sort_weight":115,"slug":116},16,"Social Media",50,"social-media",{"id":118,"doc_module":11,"doc_module_name":46,"category_name":119,"show_sort_weight":120,"slug":121},17,"Forms",40,"forms",{"id":123,"doc_module":11,"doc_module_name":46,"category_name":124,"show_sort_weight":125,"slug":126},18,"Letters",30,"letters",{"id":21,"doc_module":11,"doc_module_name":46,"category_name":128,"show_sort_weight":129,"slug":130},"Paper Templates",5,"papers-templates",{"id":132,"doc_module":11,"doc_module_name":46,"category_name":133,"show_sort_weight":4,"slug":134},158,"General","general-158"]