China
Africa
Explore chapters and articles related to this topic
Other technology aspects
Published in Hanky Sjafrie, Introduction to Self-Driving Vehicle Technology, 2019
The ISO 26262 Road Vehicles—Functional Safety standard is the automotive adaptation of the International Electrotechnical Commission IEC 61508 general industry standard for functional safety [19]. In its ten parts, it outlines functional safety management, engineering processes, recommendations for different phases in product development using the V-modelV-model as reference process model, and the supporting processes. V-model is a standard process model in automotive system engineering that represents the development activities using a V shape, with specification and design on the left side, test and integration on the right side, and implementation at the bottom of the V. The V-model shows the direct relationship between each phase of the development activities and its corresponding phase of testing. Figures 6.1 and 6.2 show an overview of the ISO 26262 standard and V-model, respectively.
Waterfall model, V-model, spiral model, and other SE models
Published in Adedeji B. Badiru, Systems Engineering Models, 2019
The V-model, or the verification and validation model, is an enhanced version of the waterfall model that illustrates the various stages of the system life cycle, as shown in Figures 7.3 and 7.4. The V-model is similar to the waterfall model in that they are both linear models whereby each phase is verified before moving on to the next phase. Beginning from the left side, the V-model depicts the development actions that flow from concept of operations to the integration and verification activities on the right side of the diagram. With this model, each phase of the life cycle has a corresponding test plan that helps identify errors early in the life cycle, minimize future issues, and verify adherence to project specifications. Thus, the V-model lends itself well to proactive defect testing and tracking. However, a drawback of the V-model is that it is rigid and offers little flexibility to adjust the scope of a project. Not only is it difficult, but it is also expensive to reiterate phases within the model. Therefore, the V-model works best for smaller tasks where the project length, scope, and specifications are well defined.
Engineering design
Published in Riadh Habash, Green Engineering, 2017
On the integration stage, all domain-specific models and solutions will be integrated into overall system and all interactions will be investigated and verified. Once this is accomplished, the system, for the first time, will be tested as a unified whole to determine whether it meets its technical requirements, specified at the beginning. All engineering techniques such as CAD, CAM, and other CAE system can be engaged. Creating 3D models or running different kind of calculations is generated. While the V-model just proposes the integration on different levels of the system, the actual design process is strongly driven by so-called integration stages, which happen regularly and integrate the design status of different parts in order to test the whole system behavior and properties.
Data and model-based triple V product development framework and methodology
Published in Enterprise Information Systems, 2022
Qing Li, Hailong Wei, Chao Yu, Shuangshuang Wang
Through this brief historical review of several popular product development frameworks, it can be seen that VV&A testing, iterative improvement and model-driven have become the main features. Among these frameworks, the V model is one of the most widely used (Jan van et al. (2004); Graessler, Hentze, and Bruckmann (2018)). However, facing the rapid iteration of technological means, the increasing diversification of users’ requirements and the emergence of data science, there are still some areas for improvement in the existing V model. Bucanac (1999) argued that the V model can only address the problem of product development at the project level rather than the enterprise/organisation level, and it lacks adequate and appropriate sub-models, methodology and supporting tools. Armour (2003) mentioned that traditional V model might cause too long development time or high development cost due to lack of early prototypes. Zhang, Huang, and Ju (2020) proposed that the decomposition process of the V model will inevitably destroy the co-relations between different stages, especially facing system of system engineering problems. Within the V model, customer requirements might be easily misunderstood or not handled properly while progressing the development process (Han et al. (2016)). How to spend the least cost in the shortest time to minimise the design errors and defects passed from the previous stage to the next stage is always the focus of product development research.
Virtual commissioning for an Overhead Hoist Transporter in a semiconductor FAB
Published in International Journal of Production Research, 2020
Joo Y. Lee, Kwanwoo Lee, Sangchul Park
The V-model, an extension of the waterfall model, is an integrated development process that covers all development steps: from the analysis of user requirements to acceptance tests of the complete system (Al-Ashaab et al. 2009; Sari, Tosun, and Alptekin 2019). Generally, the V-model consists of seven major steps; (1) concept of operations, (2) requirements and architecture, (3) detailed design, (4) implementation, (5) test and verification, (6) system verification and validation, and (7) operation and maintenance. The virtual commissioning approach, proposed in this paper, enables the concurrent engineering of the detailed design and verification of the V-model. Although the proposed virtual commissioning approach is focusing on design and verification, it also can be used for other purposes including improvement, control, and optimisation. In a conventional implementation procedure of an OHT, shown in Figure 3(a), the mechanical and electrical design phases are performed sequentially. Thus, electrical designers cannot start the control programming until the mechanical design phase is finished, the main cause of delays in time to market. Another problem is that the conventional procedure (Figure 3(a)) does not include virtual commissioning. Without virtual commissioning, the OHT system will have to be stabilised solely by real commissioning, which is very expensive and time consuming. Virtual commissioning identifies and addresses design flaws and operational faults so that significant savings can be achieved. Some previous research results (Gans et al. 2009; Lee and Park 2014) show the reduction of real commissioning time by up to 75% owing to the positive effect of virtual commissioning.