Recent literature in Systems Engineering has suggested the use of "value" to drive decision-making activities during preliminary design, in particular when choosing technologies and components for a complex system. However, to correctly evaluate design trade-offs, a visual link has to be established between the results of the value model and a product shape/geometry. This paper proposes the use of color-coded 3D CAD models to support the visualization of value analysis results in a Stage-Gate® process. The approach has been developed and exemplified within a case study related to the design of an aero-engine component, and has been demonstrated using SIEMENS NX HD3D Visual Reporting. The results of verification activities conducted in a laboratory setting show that the use of color-coded 3D CAD models increases the decision makers' awareness of value-related information in a Stage-Gate process.Keywords: value driven design, value visualization, color-coding. DOI: 10.3722/cadaps.2013.xxx-yyy INTRODUCTIONAll designs are created for a purpose. When dealing with well-defined and known problems, this purpose is well mirrored by the product requirements, which provide a good enough basis to identify the best of the available design alternatives. However, in long and complex new development processes that involve several supply chain partners, the purpose is often lost when requirements are cascaded down to suppliers and sub-contractors [16]. This causes component manufacturers to develop local optimal solutions that minimize cost, rather than to target innovative technologies that might add value to customers' and stakeholders' processes. In this context, measuring requirements fulfilment is no longer sufficient to assess the "goodness" of a design [7][13], rather more qualitative criteria need to be considered to better understand the value of a solution from a system viewpoint [37].Recent literature in Systems Engineering [24] and Value Driven Design (VDD) [12] has promoted the use of "value" as a driver for decision-making activities in preliminary design. The ambition is to use "value" to provide a measurable approximation of the level of fulfillment of the overall system needs ensured by a design solution [8]. In practice, so called "value models" are built to quantitatively
Abstract. The importance of Requirements Engineering in a Systems/Product Life Cycle context does not get the attention it deserves. Requirements definition practices mainly concentrate on defining functionality and selecting conditions for systems so that the system is sold successfully. Use-case modeling, which is part of the Unified Modeling Language, is getting a lot attention these days. It defines scenarios of system usage to reach a specified goal. Unified Modeling Language is widely used in software development projects but the Use-case modeling is only applied to requirements discovery. This paper describes the increased value of Use-cases when using them in a wider scope, in the context of a Systems/Product Life Cycle. The paper starts with an introduction on Requirements management and Use-case modeling, followed by some facts on the value of combining Usecase modeling and Requirements managemen. Finally statements are made on the value of Requirements management and Use-case modeling in Product Life-Cycle context. Requirements ManagementThe Requirement management process, an element of Systems Engineering, is an activity applicable through the whole of a product/system life-cycle. It starts with the identification of requirements, functional baselines and architectures for the preferred system concept. It successively refines these into more detailed requirements at component level. A requirement is defined as a capability or condition that shall be met by a system or a component to satisfy a contract, standard, specification, or any other imposed document. One of the main sources for this process are customer needs and developers' ideas. Executing a requirements management process results in well organized and base lined sets of requirements for a product/system, usually stored in documents. Requirements Specification trees are developed when projects follow a formal Systems Engineering process. The project objective, as defined in the top-level specification, is then analyzed top-down to a specification at sub-system level. The Requirements Management process:• Identifies and captures the requirements applicable to the system • Analyzes and decomposes requirements into clear, unambiguous, traceable and verifiable requirements • Allocates the requirements to the appropriate component within the system hierarchy and/or to the appropriate organizational entities • Derives lower-level requirements from higher-level requirements in the system hierarchy • Establishes the method of verification of each requirement • Ensures that the product complies with the requirements MANAGING COMPLEXITY AND CHANGE!
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.