@article {1334,
	title = {Enabling Rapid Product Development through Improved Verification and Validation Processes},
	journal = {Technology Innovation Management Review},
	volume = {10},
	year = {2020},
	month = {03/2020},
	pages = {25-36},
	publisher = {Talent First Network},
	chapter = {25},
	address = {Ottawa},
	abstract = {Fierce 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.},
	keywords = {agile, requirements, set-based design, validation, Verification},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/1334},
	url = {timreview.ca/article/1334},
	author = {Antti Perttula and Joni Kukkam{\"a}ki}
}
@article {887,
	title = {Building Cyber-Resilience into Supply Chains},
	journal = {Technology Innovation Management Review},
	volume = {5},
	year = {2015},
	month = {04/2015},
	pages = {19-27},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {The article discusses how an organization can adopt an information-centric approach to protect its information shared in one or more supply chains; clearly communicate the expectations it has for a direct (Tier 1) supplier to protect information; and use contracts and measurement to maintain the protection desired. Building on this foundation, the concept of resilience {\textendash} and that of cyber-resilience {\textendash} is discussed, and how an information-centric approach can assist in creating a more cyber-resilient supply chain. Finally, the article concludes with five steps an organization can take to improve the protection of its information:  i) map the supply chain; ii) build capability; iii) share information and expertise; iv) state requirements across the supply chain using standards, common frameworks, and languages; and v) measure, assess, and audit.},
	keywords = {cyber-resilience, cybersecurity, direct suppliers, indirect suppliers, information-centric approach, procurement, requirements, resilience, supply chain, Tier 1 suppliers},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/887},
	url = {http://timreview.ca/article/887},
	author = {Adrian Davis}
}
@article {649,
	title = {Sustainability and Governance in Developing Open Source Projects as Processes of In-Becoming},
	journal = {Technology Innovation Management Review},
	volume = {3},
	year = {2013},
	month = {01/2013},
	pages = {40-45},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Sustainability is often thought of as a binary state: an open source project is either sustainable or not. In reality, sustainability is much more complex. What makes this project more sustainable than that one? Why should it be assumed in the first place that sustainability is a prolonged state of an ingraced project? The threads are pulled from their yarns in many directions. 

This article attempts to reconceptualize some assumed notions of the processes involved in developing open source software. It takes the stance in favour of studying the fluctuant nature of open source and the associated artefacts, not as well-defined objects, but as commons that are continually built upon, evolved, and modified; sometimes in unexpected ways. Further, the governance of these commons is an ongoing process, tightly linked with the way in which these commons are allowed to further develop. This perspective of "in-becoming" is useful in understanding the efforts and processes that need to be provided to sustainably govern the development of open source projects and the advantages for managing requirements derived therein. 
},
	keywords = {becoming, emergence, governance, open source, Ostrom, processes, requirements, sustainability},
	issn = {1927-0321},
	doi = {http://doi.org/10.22215/timreview/649},
	url = {http://timreview.ca/article/649},
	author = {Daniel Curto-Millet}
}
