[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-245881-105":53,"doc-detail-245881-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","software-plan-plan-001-development-and-risk-management-activities","Software Plan - Plan-001 - Development and risk management activities","","Software Plan PLAN-001 (Rev. 1) outlines a structured set of activities for software risk management, development, and maintenance for PROJECT. It targets software developers and emphasizes ensuring the software is safe and useful while maintaining developer productivity. The plan defines key terms used throughout the document, explains the project’s Class C safety context under IEC 62304, and supports audit and regulatory expectations through references and recordkeeping requirements.",{"@graph":63,"@context":119},[64,80,102],{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/software-plan-plan-001-development-and-risk-management-activities/245881/",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/software-plan-plan-001-development-and-risk-management-activities/245881.png","ImageObject",442,249,{"name":88,"@type":89},"\tWilliam","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-21","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",13,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the primary purpose of the Software Plan for PROJECT?","Question",{"text":109,"@type":110},"The plan helps developers ensure PROJECT is safe and useful while allowing developers to remain productive.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Who is the document primarily written for?",{"text":114,"@type":110},"It is written primarily for software developers.",{"name":116,"@type":107,"acceptedAnswer":117},"What does the document state about the project’s safety classification?",{"text":118,"@type":110},"PROJECT is assigned a Class C software safety class, meaning death or serious injury could occur if the software fails, and related software items are presumed to have the same class.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},245881,1791742815,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":40,"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},5909887254083,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","Software Plan  \nPLAN-001, Rev. 1  \nInnolitics, LLC.  \nFebruary 19, 2021  \nContents  \n1 Purpose 2  \n2 Overview 2  \n2. 1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2  \n2.2 Development Life Cycle Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3  \n2.3 Roles and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3  \n2.4 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3  \n2.5 Development Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n2.6 Development Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n2.7 Development Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n2.8 Testing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n2.9 Quality Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n2.10 Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4  \n3 Activities 5  \n3.1 Activity Diagram ....................................... 6  \n3.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7  \n3.3 Requirements Analysis .................................... 8  \n3.4 Architectural Design ..................................... 8  \n3.5 Risk Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9  \n3.6 Risk Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9  \n3.7 Division of Labor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10  \n3.8 Release Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10  \n3.9 Detailed Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11  \n3.10 Unit Implementation and Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11  \n3.11 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13  \n3.12 Integration and System Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13  \n3. 13 Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13  \n3.14 Problem Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14  \n3.15 Prepare Problem Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14  \n3.16 Problem Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15  \n4 Appendices 16  \n4.1 Requirements Analysis .................................... 16  \n4.2 Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17  \n4.3 SOUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17  \n1 Purpose  \nThis document describes a set of activities which will be used during software risk management, development, and maintenance of PROJECT. It is written primarily for software developers.  \nPROJECT is assigned a Class C software safety class, which means death or serious injury could occur if the software fails [62304:4.3.a] . See risk.yml for details. All of the software items that compose the software system are also presumed to have the same Class C safety class [62304:4.3.c 62304:4.3.d 62304:4.3.d 62304:4.3.e 62304:4.3.f 62304:4.3.g] . The primary purpose of this document is to help developers ensure PROJECT is safe and useful while also allowing developers to be productive. The secondary purpose is to comply with IEC62304:2006+A1:2015 .  \n[In order to assist auditors and regulators, we have included section references to IEC62304:2006+A1:2015 as well as occasional comments throughout this document. These references and comments are always placed inside square brackets, and they are not present","cbCairBRfS4dvZbg","https://ap.wps.com/l/cbCairBRfS4dvZbg","pdf",265240,"English","# Purpose\n# Overview\n## Definitions\n## Development Life Cycle Model\n## Roles and Responsibilities\n## Related Documents\n## Development Standards\n## Development Methods\n## Development Tools\n## Testing Plan\n## Quality Assurance\n## Risk Management\n# Activities\n## Activity Diagram\n## Planning\n## Requirements Analysis\n## Architectural Design\n## Risk Assessment\n## Risk Control\n## Division of Labor\n## Release Planning\n## Detailed Design\n## Unit Implementation and Testing\n## Integration\n## Integration and System Testing\n## Release\n## Problem Analysis\n## Prepare Problem Report\n## Problem Investigation\n# Appendices","[{\"question\":\"What is the primary purpose of the Software Plan for PROJECT?\",\"answer\":\"The plan helps developers ensure PROJECT is safe and useful while allowing developers to remain productive.\"},{\"question\":\"Who is the document primarily written for?\",\"answer\":\"It is written primarily for software developers.\"},{\"question\":\"What does the document state about the project’s safety classification?\",\"answer\":\"PROJECT is assigned a Class C software safety class, meaning death or serious injury could occur if the software fails, and related software items are presumed to have the same class.\"}]","Software Plan - Plan-001 - Development and risk management activities | PDF",1789231788,6]