00480nas a2200157   4500008004100000022001400041245006200055210005800117260004200175300000800217490000700225100001900232700002100251700002000272856003000292       2020                        eng d  a1927-032100aEditorial: Rapid Product Development and R&D (March 2020)0 aEditorial Rapid Product Development and RD March 2020  aOttawabTalent First Networkc03/2020  a3-40 v101 aKunttu, Iivari1 aCamarda, Charles1 aPerttula, Antti  utimreview.ca/article/133102108nas a2200217   4500008004100000022001400041245009400055210006900149260004200218300001000260490000700270520146200277653001001739653001701749653002101766653001501787653001701802100002001819700002101839856003001860       2020                        eng d  a1927-032100aEnabling Rapid Product Development through Improved Verification and Validation Processes0 aEnabling Rapid Product Development through Improved Verification  aOttawabTalent First Networkc03/2020  a25-360 v103 aFierce competition in consumer electronics market has raised a lot of challenges for product development. Products now must enter to the market as fast as possible. The verification and validation (V&V) process is normally the most resource-demanding activity in product development (PD), and thus also has huge potential for improvement. The V&V process is traditionally executed near the end of the development process, and is one of the most critical activities because it identifies design errors. Error correction for a nearly complete product is often difficult and therefore can cause unexpected delays in product delivery. Performing V&V activities in early phases of the PD process and utilising V&V methods other than testing has proven to be a good approach to reduce risks associated with taking a long time to reach the market. However, V&V can only be carried out when verifiable requirements exist. This paper focuses on the importance of moving V&V activities to each phase of PD by defining the requirements for components and modules. In addition, we explore how some of product-level requirements can be verified before a product has been integrated, and explain the difference between definitions of verification and validation requirements. Finally, we present the idea of changing the focus of verification activities from being set-based in the early phase of development, to being point-based when the product is close to completion.10aagile10arequirements10aset-based design10avalidation10aVerification1 aPerttula, Antti1 aKukkamäki, Joni  utimreview.ca/article/133402510nas a2200229   4500008004100000022001400041245009400055210006900149260004200218300000900260490000700269520180800276653001902084653000802103653003002111653002102141100002502162700002402187700001902211700002002230856003002250       2020                        eng d  a1927-032100aRapid Learning and Knowledge-Gap Closure During the Conceptual Design Phase – Rapid R&D0 aRapid Learning and KnowledgeGap Closure During the Conceptual De  aOttawabTalent First Networkc03/2020  a5-150 v103 aNew product development strategies, such as set-based concurrent engineering design (SBCED) or set-based design (SBD), have demonstrated improved ways to address knowledge gaps in alternate design concepts prior to the decision to select a single concept for development. Most of the corpus in this field addresses engineering product development that relies on systems and subsystems with years of prior experience in testing, development, and operation. These often have known or existing solutions, and use state-of-the-art (SOA), or near SOA technology. In addition, most papers do not dive into the details of how knowledge was attained to rapidly close critical knowledge gaps. This paper attempts to explain how a research-based method to construct knowledge can accelerate the knowledge capture critical for developing solutions to extremely challenging problems. This rapid R&D methodology enables a rapid acquisition of critical knowledge to understand potential failure modes of concepts in a set-based way. Thus, it enables intelligent decisions for the selection of the final concept as well as the continuous maturation of parallel concepts. The continuous, parallel maturation of multiple concepts enables effective off-ramps in the design process as requirements and new knowledge arise in the course of the development program, without incurring excessive rework, cost growth, and schedule creep. The goal of this paper is to describe a method that accelerates the generation of critical knowledge early in the conceptual design phase, as a way to close knowledge gaps quickly, and thus enable intelligent design decisions and concept selections early in the product development cycle. The methodological descriptions are illustrated with case examples from NASA technology development.10aknowledge gaps10aR&D10aRapid product development10aset-based design1 aCamarda, Charles, J.1 aScotti, Stephen, J.1 aKunttu, Iivari1 aPerttula, Antti  utimreview.ca/article/1332