[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-244529-105":53,"doc-detail-244529-en":131},{"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":124,"head_meta":126,"extra_data":128,"updated_unix":130},105,"en","development-process-for-production-ready-software-based-on-rd-projects","Development Process for Production Ready Software based on R&D Projects - -","","Software bugs in safety-critical and cybersecurity-critical systems must be reduced to a negligible level due to the severe potential harm and financial costs. Established safety and cybersecurity standards address this by mandating structured development processes using proven, state-of-the-art methods. The same approach is applied to quality-managed (QM) software. The document proposes a development process that enables reuse of research artifacts, follows an extended V-model for verification and validation, and supports automotive-focused applications, scalable to similar domains.",{"@graph":63,"@context":123},[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/development-process-for-production-ready-software-based-on-rd-projects/244529/",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/development-process-for-production-ready-software-based-on-rd-projects/244529.png","ImageObject",442,249,{"name":88,"@type":89},"Margaret","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",7,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115,119],{"name":106,"@type":107,"acceptedAnswer":108},"What problem does the proposed process address in software development?","Question",{"text":109,"@type":110},"It targets reducing software bug risk—especially for safety-critical and cybersecurity-critical systems—so failures and harm are minimized to a negligible level. It also aims to lower the cost of fixing defects by discovering them earlier.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How does the process use the V-model?",{"text":114,"@type":110},"The development side follows phases from Goal Definition through Planning, Requirements, Architecture, Specification, and Implementation. The V&V side verifies corresponding artifacts through testing, integration on target hardware, and validation against requirement coverage, leading to a release recommendation.",{"name":116,"@type":107,"acceptedAnswer":117},"Which additional requirements apply for safety and cybersecurity critical projects?",{"text":118,"@type":110},"The process extends the V-model with hazard and risk analysis for safety-critical software and threat and risk analysis for cybersecurity-critical software. It incorporates automotive safety and cybersecurity standards (ISO 26262 and SAE J3061).",{"name":120,"@type":107,"acceptedAnswer":121},"How is iteration structured in the process?",{"text":122,"@type":110},"While the V-model anticipates iterative development, Scrum provides structure for iterations. Development runs in sprints of typically 2–4 weeks with planning, analysis against initial planning, and retrospectives to improve the process.","https://schema.org",{"og:url":78,"og:type":125,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":127,"canonical":78},"index,follow",{"doc_id":129,"site_id":56},244529,1791731547,{"code":4,"msg":5,"data":132},{"doc_id":129,"user_id":133,"nickname":88,"user_avatar":134,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":135,"file_id":136,"file_url":137,"file_type":138,"file_size":139,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":140,"language":141,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":142,"faqs":143,"seo_title":144,"seo_description":61,"update_tm":145,"read_time":146},137451207643,"https://ap-avatar.wpscdn.com/davatar_3d24733baf745e90a7e4bdd5f77d97b2","Development Process for Production Ready Software based on R&D Projects  \nMartin Suesskraut, Jens Schmüdderich  \n2020  \nPreprint:  \nThis is an accepted article published in HRI-EU. The final authenticated version is available online at: [https://doi.org/](https://doi.org/) [DOI not available]  \nDevelopment Process for Production Ready Software based on R&D Projects  \nBased on the Example Cooperative Risk Maps  \nMartin Süßkraut  \nSILISTRA SYSTEMS GMBH| KÖNIGSBRÜCKER STR. 124 | 01099 DRESDEN | GERMANY  \nJens Schmüdderich  \nHONDA RESEARCH INSTITUTE EUROPE GMBH | CARL-LEGIEN-STR. 30 | 63073 OFFENBACH/MAIN | GERMANY  \n1 Executive Summary  \nThe financial costs of software bugs do not require a motivation [51] . Especially in safety critical and cybersecurity critical systems the risk of failures and, hence, harm to people must be reduced to a negligible level. The standards for developing safety critical software and standards for cybersecurity critical software solve the problem of software bugs by requiring a structured software development process using stateof-the-art & proven-in-use software development approaches and techniques. The same solution also works for non-safety and non-cybersecurity critical software (called QM software development for quality managed software development) . Because the earlier bugs are discovered, the lower the cost of fixing them [52] .  \nThis document presents a software development process for QM as well as safety & cybersecurity critical software. The process provides an interface for reusing artifacts from a research project that pre-dates the software development project.  \nThe process introduced in this document focuses on application in the automotive industry based on the example project briefly introduced in Chapter 4, but can also be applied in fields with similar standards such as robotic and urban mobility. In either case, the software projects require a certain minimal size, as short-term projects with a length ofjust a few weeks and one (wo)man projects will not benefit from the outlined processes. Safety critical and cybersecurity critical projects, however, already require a structured development process which can neither be accomplished by one person nor realized in a few weeks for any meaningful projects.  \nThe software development process of this document is based on the V-model [1]:  \nThe left side of the diagram shows the creation phases from Goal Definition down to Implementation. Every phase towards the bottom becomes more concrete. Goal Definition defines the overall goal that the developed software should fulfill from a user’s point of view. The Planning phase prepares the following phases and analyses the research project for its reusability in the following phases. In the Requirements phase the requirements engineering must be done to define the resulting software in detail on the technical level. In the Architecture phase the software architecture must be defined down to the SW units. Finally, these SW units must be specified and implemented in the Implementation phase.  \nThe right side of the V-model is called V&V for Verification & Validation. This side verifies the corresponding phases on the left side. In Testing the SW units must be verified with automated unit tests, static & dynamic analysis, and code reviews. In the Integration phase the whole software (as a linked binary) must be tested on the target hardware. In the Validation phase the performed tests must be with against the requirements from the Requirement phase to determine: whether all requirements were tested successfully. From this analysis a release recommendation for management is derived. When management approves the release,  \nthe final software together with all other work products of the software development process must be archived.  \nChapter 5 describes the V-model for QM software development projects. Part of the Goal Definition is a Hazard and Risk Analysis to determine whether the software ","cbCaih9iP82eePYQ","https://ap.wps.com/l/cbCaih9iP82eePYQ","pdf",1613111,76,"English","# Executive Summary\n## Costs and standards for software bugs\n## Structured process spanning research-to-software reuse\n## V-Model for development and V&V\n## Extensions for safety and cybersecurity requirements\n## Supporting processes and agile iteration with Scrum","[{\"question\":\"What problem does the proposed process address in software development?\",\"answer\":\"It targets reducing software bug risk—especially for safety-critical and cybersecurity-critical systems—so failures and harm are minimized to a negligible level. It also aims to lower the cost of fixing defects by discovering them earlier.\"},{\"question\":\"How does the process use the V-model?\",\"answer\":\"The development side follows phases from Goal Definition through Planning, Requirements, Architecture, Specification, and Implementation. The V\\u0026V side verifies corresponding artifacts through testing, integration on target hardware, and validation against requirement coverage, leading to a release recommendation.\"},{\"question\":\"Which additional requirements apply for safety and cybersecurity critical projects?\",\"answer\":\"The process extends the V-model with hazard and risk analysis for safety-critical software and threat and risk analysis for cybersecurity-critical software. It incorporates automotive safety and cybersecurity standards (ISO 26262 and SAE J3061).\"},{\"question\":\"How is iteration structured in the process?\",\"answer\":\"While the V-model anticipates iterative development, Scrum provides structure for iterations. Development runs in sprints of typically 2–4 weeks with planning, analysis against initial planning, and retrospectives to improve the process.\"}]","Development Process for Production Ready Software based on R&D Projects - - | PDF",1789218601,27]