[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-196890-105":53,"doc-detail-196890-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","kaos-catalogue","KAOS Catalogue","","This document outlines the metadata extraction process, focusing on cataloging KAOS extensions and constructs. It details the structure for identifying and storing information about these elements, including their names, descriptions, types, and associated registered users. The process involves a systematic approach from initial systematic literature reviews (SLRs) of KAOS extensions to extraction, catalog development, population, testing, and evaluation. The images provided illustrate specific examples of constructs and the user interface of the KAOS Catalogue system, which allows users to report extensions and constructs with details such as title, author, and link. The system aims to facilitate the organization and retrieval of information related to KAOS extensions and constructs, supporting a structured approach to software engineering and requirements analysis.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/kaos-catalogue/196890/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/kaos-catalogue/196890.png","ImageObject",442,249,{"name":88,"@type":89},"Nguyễn Văn Học","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-27","2026-09-03",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of the KAOS Catalogue?","Question",{"text":108,"@type":109},"The KAOS Catalogue serves as a system for cataloging and organizing information about KAOS extensions and constructs, facilitating their management and retrieval.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What information is captured for each KAOS construct?",{"text":113,"@type":109},"For each construct, the KAOS Catalogue captures its Name, Description (meaning), Type (Node or Link), and an Example of its usage.",{"name":115,"@type":106,"acceptedAnswer":116},"What are the steps involved in developing and populating the KAOS Catalogue?",{"text":117,"@type":109},"The process involves a Systematic Literature Review (SLR) of KAOS extensions, followed by Extraction, Catalogue Development, Population, Testing, and Evaluation.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},196890,1788463455,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":20,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":47},1374402739827,"https://ap-avatar.wpscdn.com/avatar/14000c97e7351f1a627?x-image-process=image/resize,m_fixed,w_180,h_180&k=1787885694763230660","| ID-Code to identify the extension |\n| --- |\n| Title-Title of the paper related to the KAOS extension |\n| Link-Link to access the paper of the KAOS extension |\n| Authors-Authors of the paper of the KAOS extension |\n| Field-Journal/Conference/Book |\n| Extension base-If the extension is based on other extension |\n| Application Area - It can be one or more of the following values: Aspects, Adaptive Systems, Autonomic Systems, Business process, Enterprise, Web services, Risks, Safety, Organizational , Security-privacy-vulnerability and Other |\n| Level of extension-The level of the representation involved in the proposal of the extension (Abstract syntax, Concrete Syntax or Both) |\n| Compatibility between metamodel and concrete syntax-To identify if there is compatibility between the representation in the metamodel and concrete syntax |\n\n\n| ID-Code to identify the construct |\n| --- |\n| Name-Name of the concepts which the construct represents |\n| Description-meaning of the concept the construct represents |\n| Type-Node or Link |\n| Example-A model with the usage of the construct |","cbCaivmBGx7TbY75","https://ap.wps.com/l/cbCaivmBGx7TbY75","pdf",1097046,"English","# KAOS Catalogue\n## Extensions\n## Constructs\n## Form Report","[{\"question\":\"What is the purpose of the KAOS Catalogue?\",\"answer\":\"The KAOS Catalogue serves as a system for cataloging and organizing information about KAOS extensions and constructs, facilitating their management and retrieval.\"},{\"question\":\"What information is captured for each KAOS construct?\",\"answer\":\"For each construct, the KAOS Catalogue captures its Name, Description (meaning), Type (Node or Link), and an Example of its usage.\"},{\"question\":\"What are the steps involved in developing and populating the KAOS Catalogue?\",\"answer\":\"The process involves a Systematic Literature Review (SLR) of KAOS extensions, followed by Extraction, Catalogue Development, Population, Testing, and Evaluation.\"}]","KAOS Catalogue | PDF"]