Advanced product planning: a comprehensive process for systemic definition of new product requirements

Bid management: A systems engineering approach

“…Consequently, the information acquired and associated knowledge can be highly tacit Informal information channels Macdonald & Williams (1993) Interfacing with 'information gatekeepers' from customer organizations can result in more effective capture of the relevant technical requirements and this can help in the early identification of emerging technical and business opportunities Workshops and groups Macaulay (1996) This specific method of engaging with the customer is a particularly useful approach to understanding complex technical requirements, however, it can de difficult to document the findings. In this regard, the use of structured consultations and syndicate exercises is suggested Soft systems methodology Checkland & Scholes (1990) Application of systems thinking through a seven-step model, which can be used to reduce complex technical requirements to less complex sub-areas that can then be captured and documented Structured systems analysis and design method Stevens, Myers & Constantine (1974) Formal software requirements methodology involving data modeling, which results in physical data and process design; can be used for capturing highly structured and complex requirements Waterfall lifecycle model Neill and Laplante (2003) This structured approach is used specifically for generating software requirements and when applied to proposal management would be carried out through interrogating technical specifications available from industry or government sources Goal oriented approach Navarro, Letelier, Mocholi & Ramos (2006) Formalistic approach involving the development of metamodels that allow goal oriented system requirements to be captured; relevant to software architecture development Systemic definition Agouridas, McKay, Winand, & de Pennington (2008) This highly structured and comprehensive approach builds up a series of stakeholder aligned frameworks that allow detailed capture and subsequent management of new product requirements collated in order to build up an improved picture of the emerging requirements. There will also be, however, a wealth of nonexplicit knowledge or tacit knowledge that can also be collected.…”

Rethinking Service Design: A Socio-Technical Approach to the Development of Business Models

“…Solutions now need to target customers whose needs and demands are changing. A vital step in the development of product-service systems is concerned with understanding customer needs [ 6 ], and translating them into design requirements [ 3 ]. Manufacturing organizations now need to focus more on the quality of their products and services to ensure they address the needs and requirements of customers, i.e., moving from a technical-product focus, to a service-customer focus.…”

“…Many authors propose processes for engineering design [ 13 , 55 , 66 ]; a common feature of all of these processes lies in an early focus on the problem to be addressed and the formulation of design requirements [ 3 ]. More recently, product-service system researchers have begun to propose similar processes for product-service system design.…”

7.4.3 Understanding Airlines' Value Perceptions for Value‐Based Requirements Engineering Of Commercial Aircraft

“…There are already a set of processes and methods available in literatures and industrial practices for RE (Agouridas et al 2008, Bayus 2007, De Chazelles et al 2004, Pahl and Beitz 2007, Ulrich and Eppinger 2007. As our intention is to focus on value at RE stage and not to depart from available good practice, the approach is proposed in parallel to the traditional RE processes and methods.…”