[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243106-105":53,"doc-detail-243106-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","insist-system-requirements-specification-d121","INSIST - System Requirements Specification - D1.2.1","","INSIST D1.2.1 presents system requirements jointly defined by project partners and structures them as both functional and non-functional requirements. Non-functional requirements are organized into a comprehensive set of quality and operational categories, including accessibility, availability, security, performance, scalability, reliability, compliance, interoperability, privacy, and maintainability. The requirements are derived from user needs and explicitly align with the work carried out in D1.1.2 use case scenarios, supporting the subsequent system design phase.",{"@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/insist-system-requirements-specification-d121/243106/",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/insist-system-requirements-specification-d121/243106.png","ImageObject",442,249,{"name":88,"@type":89},"Mason","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-22","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":73},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"How are INSIST system requirements classified in this deliverable?","Question",{"text":108,"@type":109},"The document classifies system requirements into functional and non-functional system requirements.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What types of non-functional requirements are covered?",{"text":113,"@type":109},"Non-functional requirements are organized into many categories such as accessibility, availability, security, performance/response time, privacy, scalability, reliability, compliance, and maintainability.",{"name":115,"@type":106,"acceptedAnswer":116},"How is this deliverable connected to user requirements and earlier work?",{"text":117,"@type":109},"System requirements are defined considering user requirements, and the document references “D1.1.2 - Use Case Scenarios and Requirements” for this task. It is intended to be used during the system design phase.","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},243106,1790060847,{"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":73,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},5909887256941,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","| INSIST\u003Cbr>Deliverable\u003Cbr>D1.2.1-System Requirements Specification\u003Cbr>Editors:\u003Cbr>Çiğdem Çavdaroğlu\u003Cbr>ITEA 3 Project 13021\u003Cbr>29/12/2017 |  |\n| --- | --- |\n| | |\n\nDocument properties  \n\n| Security | Confidential |\n| --- | --- |\n| Version | Version 1.1 |\n| Editor | Gülsüm Çiğdem Çavdaroğlu, KoçSistem |\n| Authors/ Contributors | Özgür Devrim Orman, Bor\u003Cbr>Gülsüm Çiğdem Çavdaroğlu, Koç Sistem\u003Cbr>Güven Fidan, Argedor\u003Cbr>Mustafa Eren, Verisun\u003Cbr>Juan Miguel Gómez, Ezeris Networks Global Services |\n\nAbstract  \nThis document includes the system requirements jointly defined by the project partners.  \nTable of contents  \nDocument properties ................................................................................................................. 2  \nAbstract ...................................................................................................................................... 3  \nTable of contents........................................................................................................................ 4  \n1. Introduction and Context ................................................................................................. 5  \n1.1. Introduction................................................................................................................ 5  \n1.2. Project ........................................................................................................................ 6  \n1.3. Work Package ............................................................................................................. 6  \n2. System Requirements ....................................................................................................... 7  \n2.1. Definition of terms ..................................................................................................... 7  \n2.1.1. System Requirement .......................................................................................... 7  \n2.2. Templates ................................................................................................................... 9  \n2.2.1. Template for the System Requirements ............................................................ 9  \n2.3. List of Requirements .................................................................................................. 9  \n3. User Characteristics of INSIST Platform.......................................................................... 16  \n3.1. System Users ............................................................................................................ 16  \n3.1.1. Maintenance User ............................................................................................ 16  \n3.2. End Users .................................................................................................................. 17  \n3.2.1. B2B Users .......................................................................................................... 17  \n3.2.2. B2C Users .......................................................................................................... 17  \n4. Abbreviations .................................................................................................................. 18  \n5. References ...................................................................................................................... 19  \n1. Introduction and Context  \n1.1. Introduction  \nIn this document, system requirements defined by the partners are presented. System requirements are classified into two categories: funtional and non-functional system requirements.  \nNon-functional system requirements are classified into various categories: accessibility; accuracy; audit, control, and reporting; availability; backup and restore; capacity, current and forecast; certification; compliance; compatibility of software, tools, standards, platform, database; concurrency; configuration management; dependency on third parties; deployment; documentatio","cbCaicpWW2MtL3Ze","https://ap.wps.com/l/cbCaicpWW2MtL3Ze","pdf",637034,19,"English","# 1. Introduction and Context\n## 1.1. Introduction\n## 1.2. Project\n## 1.3. Work Package\n# 2. System Requirements\n## 2.1. Definition of terms\n## 2.2. Templates\n## 2.3. List of Requirements\n# 3. User Characteristics of INSIST Platform\n## 3.1. System Users\n## 3.2. End Users\n# 4. Abbreviations\n# 5. References","[{\"question\":\"How are INSIST system requirements classified in this deliverable?\",\"answer\":\"The document classifies system requirements into functional and non-functional system requirements.\"},{\"question\":\"What types of non-functional requirements are covered?\",\"answer\":\"Non-functional requirements are organized into many categories such as accessibility, availability, security, performance/response time, privacy, scalability, reliability, compliance, and maintainability.\"},{\"question\":\"How is this deliverable connected to user requirements and earlier work?\",\"answer\":\"System requirements are defined considering user requirements, and the document references “D1.1.2 - Use Case Scenarios and Requirements” for this task. It is intended to be used during the system design phase.\"}]","INSIST - System Requirements Specification - D1.2.1 | PDF",1789200030,7]