[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-581677-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-581677-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","total-learning-architecture-addendum-functional-requirements-document","Total Learning Architecture Addendum - Functional Requirements Document","","Functional requirements define the objective end-state for Department of Defense learning organizations transitioning to Total Learning Architecture (TLA) compliant data and microservices. The addendum is issued as a 2021 update to an earlier 2019 version, establishing requirements across required modes and states, core system capabilities, and learning experience management. It also specifies internal and external interface requirements, including xAPI, REST, messaging topology, user interfaces, conformance testing, and schema control to support end-to-end interoperability.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/research-report/","Research & Report",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/total-learning-architecture-addendum-functional-requirements-document/581677/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/total-learning-architecture-addendum-functional-requirements-document/581677.png","ImageObject",300,407,{"name":42,"@type":43},"Aurelia","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-11-16","2026-10-15",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",8,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the document’s main purpose?","Question",{"text":63,"@type":64},"It defines the objective end-state and functional requirements for DoD learning organizations migrating to TLA-compliant data and microservices.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How is the addendum positioned relative to earlier versions?",{"text":68,"@type":64},"It is a 2021 update to a 2019 version.",{"name":70,"@type":61,"acceptedAnswer":71},"Which interface standards and technologies are explicitly referenced?",{"text":72,"@type":64},"The table of contents highlights internal interface requirements including xAPI and REST, as well as messaging topology and schema control for external integration.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},581677,1792208764,{"code":4,"msg":82,"data":83},"success",[84,88,92,96,101,106,111,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":85,"show_sort_weight":86,"slug":87},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":93,"show_sort_weight":94,"slug":95},"Exam",70,"exam",{"id":97,"doc_module":4,"doc_module_name":25,"category_name":98,"show_sort_weight":99,"slug":100},5,"Comic",60,"comic",{"id":102,"doc_module":4,"doc_module_name":25,"category_name":103,"show_sort_weight":104,"slug":105},6,"Technology",50,"technology",{"id":107,"doc_module":4,"doc_module_name":25,"category_name":108,"show_sort_weight":109,"slug":110},7,"Healthcare",40,"healthcare",{"id":55,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":112,"slug":113},30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":97,"slug":129},19,"General","general",{"code":4,"msg":82,"data":131},{"doc_id":79,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":55,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":139,"language":140,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":12,"update_tm":144,"read_time":145,"preview_page_count":4},1099514068365,"https://ap-avatar.wpscdn.com/avatar/10000253d8d9f28188e?x-image-process=image/resize,m_fixed,w_180,h_180&k=1794309523707217728","| REPORT DOCUMENTATION PAGE |  |  |  |  |  |  | Form Approved\u003Cbr>OMB No. 0704-0188 |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| The public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information . Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302 . Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.\u003Cbr>PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS. |  |  |  |  |  |  |  |\n| 1. REPORT DATE (DD-MM-YYYY) |  |  | 2. REPORT TYPE |  |  |  | 3. DATES COVERED (From-To) |\n| 4. TITLE AND SUBTITLE\u003Cbr>|  |  |  |  |  | 5a. CONTRACT NUMBER\u003Cbr>|  |\n|  |  |  |  |  |  | 5b. GRANT NUMBER\u003Cbr>|  |\n|  |  |  |  |  |  | 5c. PROGRAM ELEMENT NUMBER\u003Cbr>|  |\n| 6. AUTHOR(S)\u003Cbr>|  |  |  |  |  | 5d. PROJECT NUMBER\u003Cbr>|  |\n|  |  |  |  |  |  | 5e. TASK NUMBER\u003Cbr>|  |\n|  |  |  |  |  |  | 5f. WORK UNIT NUMBER\u003Cbr>|  |\n| 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)\u003Cbr>\u003Cbr>|  |  |  |  |  |  | 8. PERFORMING ORGANIZATION\u003Cbr>REPORT NUMBER |\n| 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)\u003Cbr>\u003Cbr>|  |  |  |  |  |  | 10. SPONSOR/MONITOR'S ACRONYM(S)\u003Cbr>|\n|  |  |  |  |  |  |  | 11. SPONSOR/MONITOR'S REPORT\u003Cbr>NUMBER(S) |\n| 12. DISTRIBUTION/AVAILABILITY STATEMENT\u003Cbr>|  |  |  |  |  |  |  |\n| 13. SUPPLEMENTARY NOTES |  |  |  |  |  |  |  |\n| 14. ABSTRACT |  |  |  |  |  |  |  |\n| |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n| 15. SUBJECT TERMS |  |  |  |  |  |  |  |\n| 16. SECURITY CLASSIFICATION OF: |  |  |  | 17. LIMITATION OF ABSTRACT\u003Cbr>| 18. NUMBER OF\u003Cbr>PAGES\u003Cbr>| 19a. NAME OF RESPONSIBLE PERSON\u003Cbr>|  |\n| a. REPORT | b. ABSTRACT | c. THIS PAGE |  |  |  |  |  |\n|  |  |  |  |  |  | 19b. TELEPHONE NUMBER (Include area code)\u003Cbr>|  |\n\nStandard Form 298 (Rev. 8/98) Prescribed by ANSI Std. Z39 . 18  \nTable of Contents  \n1.0 Scope .........................................................................................................................................3  \n1.1 Identification................................................................................................................................. 3  \n1.2 System Overview........................................................................................................................... 3  \n1.3 Document Overview ..................................................................................................................... 4  \n2.0 Referenced Documents and Normative Standards and Specifications ..........................................8  \n3.0 Requirements.............................................................................................................................8  \n3.1 Required Modes and States .......................................................................................................... 9  \n3.2 System Capabilities ..................................................................................................................... 13  \n3.2.1 Learning Experience Management (LEM) ........................................................................... 13  \n3.2.2 Activity and Resource Management ................................................................................... 23  \n3.2.3 Competency Management ................................................................................................. 27  \n3.2.4 Learner profile management ................","cbCaioTQXd2n0oHY","https://ap.wps.com/l/cbCaioTQXd2n0oHY","pdf",3965951,49,"English","# 1.0 Scope\n## 1.1 Identification\n## 1.2 System Overview\n## 1.3 Document Overview\n# 2.0 Referenced Documents and Normative Standards and Specifications\n# 3.0 Requirements\n## 3.1 Required Modes and States\n## 3.2 System Capabilities\n## 3.3 Internal Interface Requirements\n## 3.4 External Interface Requirements","[{\"question\":\"What is the document’s main purpose?\",\"answer\":\"It defines the objective end-state and functional requirements for DoD learning organizations migrating to TLA-compliant data and microservices.\"},{\"question\":\"How is the addendum positioned relative to earlier versions?\",\"answer\":\"It is a 2021 update to a 2019 version.\"},{\"question\":\"Which interface standards and technologies are explicitly referenced?\",\"answer\":\"The table of contents highlights internal interface requirements including xAPI and REST, as well as messaging topology and schema control for external integration.\"}]","Total Learning Architecture Addendum - Functional Requirements Document | PDF",1792040993,123]