Toolbox for User-Centered Specification of VR Systems

2019 ◽  
Author(s):  
Andreas Liebal ◽  
Heidi Krömker ◽  
Atif Mahboob ◽  
Christian Weber
Keyword(s):  
Product Development ◽  
Development Process ◽  
Low Cost ◽  
Product Development Process ◽  
Full Potential ◽  
Product Model ◽  
Specific Product ◽  
Marketing Tool ◽  
Main Components ◽  
Definition Of

Abstract Breaking into the consumer market, Virtual Reality (VR) has now penetrated wide areas of the industrial market. Rapidly developing technologies are opening up new application possibilities with low cost and high quality solutions. Although VR has been used exclusively as a marketing tool in companies up to now, it is still being extended to support all areas of the complete product development process. However, this is also accompanied by the difficulty to manage the amount of functionalities and design options associated with VR. Developers of such VR systems must nevertheless maintain an overview of the multitude of technological and content-related possibilities and bring them in line with the requirements of VR customers or VR users. At the same time, VR customers must also have an idea of the technological possibilities and formulate their vision of a VR system as precisely, completely and goal-oriented as possible. In the end, both sides must find a common level of communication in order to record the characteristics of the VR system in the form of a requirement specification or an offer. Factors such as different terminologies and different views about the product development process along with the diverse knowledge about VR functionalities on both sides complicate this process. This article is intended to show the concept for a toolbox that supports the definition of a customer-specific VR solution. This shall exploit the full potential of VR for the customer’s specific product development process in VR. The generic product development process will be studied and the VR application areas will be located. In this regard, a classification of the main components of VR systems is performed. The goal of such a classification is to establish a relationship between the product model (along with product specific properties and relationships) and the VR system components. As the field of VR does not yet have an established set of standardized terms, a definition of all terms in this context can help to improve communication between customer and developer. This article shows how a toolbox for agencies and development departments must be structured so that the VR developer can design, evaluate, calculate and develop a complex VR system in a customer-oriented way. Furthermore, the vision of the toolbox presented in this paper also has the goal that the VR customer can specifically formulate his/her requirements in a customer-specific way that leads to an easier understanding for VR developer and eventually to a VR solution. Finally, the possibility of extension of the presented toolbox structure is discussed to automatically generate specification proposals and suitable technology recommendation based on the problem at hand.

Serienreifmachung in der Nutzfahrzeug-Industrie*/Attaining production-readiness - Standardization in the commercial vehicle industry: problems, challenges and solutions

2015 ◽  
Vol 105 (03) ◽  
pp. 152-155
Author(s):  
T. Steinhäußer ◽  
G. Reinhart
Keyword(s):  
Product Development ◽  
Development Process ◽  
Commercial Vehicle ◽  
Product Development Process ◽  
Definition Of ◽  
Selection Of

Aufbauend auf einer zeitlichen und inhaltlichen Abgrenzung im Produktentstehungsprozess (PEP) stellt der Fachbeitrag verschiedene Probleme vor, die bei der Serienreifmachung allgemein und in der Nutzfahrzeug-Industrie im Speziellen auftreten. Anschließend werden Herausforderungen abgeleitet, die es bei der Entwicklung eines Konzepts für die Serienreifmachung in der Nutzfahrzeug-Industrie zu bewältigen gilt.   Based on a definition of the process of attaining production-readiness in the context of the product development process, this article presents several problems that occur during the process of attaining production-readiness in general and specifically in the commercial vehicle industry. Furthermore, a selection of challenges is derived from the presented problems and an approach to cope with these challenges is suggested.

Study on Ontology-Based Knowledge Integration

2010 ◽  
Vol 139-141 ◽  
pp. 1545-1549 ◽  
Author(s):  
Jia Hao ◽  
Yan Yan ◽  
Guo Xin Wang ◽  
Jian Jun Lin
Keyword(s):  
Product Development ◽  
Development Process ◽  
Knowledge Integration ◽  
Knowledge Organization ◽  
Product Development Process ◽  
Prototype System ◽  
Integration Model ◽  
The Core ◽  
Definition Of ◽  
Core Part

This paper firstly discussed the definition of knowledge integration in the field of product development and proposed the multidimensional knowledge integration model which could be the guidance during the implementation of knowledge integration. Subsequently the framework of knowledge integration is presented, three layer (the enterprise distributes resources layer, enterprise managed knowledge layer and product development process layer) in the framework are explanted respectively. The ontology is introduced to provide the semantic fundament for the framework. The structure of integrative ontology is studied and constructed with OWL(Ontology Web Language). The ontology plays an important role in knowledge organization and knowledge service and it’s the core part of the whole framework. At last a prototype system based on the previous techniques is developed and basically fulfills knowledge integration in product development process.

Conceptual Product Development

1996 ◽  
Author(s):  
Gritt Ahrens ◽  
Oliver Tegel
Keyword(s):  
Product Development ◽  
Development Process ◽  
Product Development Process ◽  
Conceptual Modelling ◽  
Function Structure ◽  
Industrial Practice ◽  
Technological Support ◽  
Definition Of ◽  
Product Specifications ◽  
Different Parts

Abstract The importance of conceptual modelling more and more becomes recognized in the industrial practice, since it is commonly known that it is during that phase of the product development process where fundamental choices are made that have a strong influence on the result of the development — the process! The process of product development can only be efficient if it is basically put into practice methodically. The time additionally invested in the first steps of the methodical process of product development as it is described in the German guideline VDI 2221 prevents from forgetting important specifications or even overseeing possible ways of solution. This way the phase of conceptual modelling can result in a saving of time needed for product development due to fewer iteration loops for the correction of mistakes in later phases of the process and an increase of the product quality, too. The prerequisite of the efficiency of conceptual modelling is a definition of the product specifications which is as precise as necessary and as abstract as possible in order not to restrict the amount of solutions in an unnecessary way. Looking at the functions a product to be developed has to fulfill, the requirements list serves as a basis for the definition of function structures in which all functions and the relationships amongst each other are defined. This function structure can be utilized not only for the description of the product in an abstract way, but also for structuring the development process as well. With the definition of interfaces between parts of the product, implicitly interface specifications for the work on different parts of the product are defined. The function structure, therefore, can be used as a tool for management in the product development process. Because of this, the information summarised in these documents must be available throughout the entire development process the information technological support of these tools should be standard. Nevertheless, common CAD-Software does not support any step of conceptual modelling. In this paper an information technological support for conceptual modelling is also presented. Furthermore, it is shown what kind of changes in and extensions of common CAX-Systems would be necessary for the realisation of this theory.

scholarly journals Designing for Informal Learning: The Case of a Mobile E-Reader

2019 ◽  
Vol 10 (1) ◽  
pp. 91-102
Author(s):  
Jason K. McDonald
Keyword(s):  
Product Development ◽  
Informal Learning ◽  
Design Process ◽  
Development Process ◽  
Case Reports ◽  
Product Development Process ◽  
Design Decisions ◽  
End Point ◽  
Definition Of ◽  
Subscription Service

This case describes the redesign of a mobile eReader application. The purpose of the redesign was to convert an existing eReader from a means of only reading books into a tool for informal learning. The case reports how the design team’s definition of informal learning evolved throughout the product development process, and how design deci-sions were influenced by this changing definition. Over the period of time covered in the case, the eReader evolved from a tool used for reading eBooks, into one meant for personal study, and then into a product that supported serendipitous discovery of inspiring material (built under a philosophy that informal learning meant that people were able to discover interesting and uplifting material without exerting effort to find it). The end point of the eReader’s evolution was as a subscription service for the company’s eBooks and digital audiobooks, to allow customers to continually use them for educational purposes. This case is structured around the four iterations of the eReader design process. Each iteration reports how design decisions were made and what kind of results were achieved.

A Method for the Evaluation of the Suitability of Specific Product Development Processes for Parallelization

1997 ◽  
Author(s):  
Gritt Ahrens
Keyword(s):  
Product Development ◽  
Design Process ◽  
Development Process ◽  
Product Development Process ◽  
Project Leader ◽  
Specific Product ◽  
3D Cad ◽  
Cad System ◽  
Development Processes

Abstract A method for the parallelization of the working steps of an existing product development process is discribed. The procedure which is based on the design methodology as described by Pahl and Beitz provides a framework of rules and guidelines which enable the project leader to judge in which phase of a development and design process the introduction of Simultaneous Engineering is profitable. In a case study of a German manufacturer of tubomachines and its subcontractor the developed method is validated by the example of the development and design process of a geared compressors. The reorganized process was tested using a commercially available 3D-CAD-System in order to simulate the design tasks and a commercially available PDM-System for the handling of the data produced.

Application of Data Maturity in Product Development Process Control

2011 ◽  
Vol 58-60 ◽  
pp. 657-661
Author(s):  
Qiu Zhong Zhou ◽  
Hao Yu Zha
Keyword(s):  
Quantitative Analysis ◽  
Product Development ◽  
Development Process ◽  
Process Management ◽  
Structure Design ◽  
Product Development Process ◽  
Maturity Level ◽  
Collaborative Product Development ◽  
Product Model

In the concurrent and collaborative product development process, the realization of quantitative analysis and overall control of the development process management is the key and the difficulties in the current study. Through describes the concept and role of data maturity, a new methods to quantitative analysis and overall control of collaborative product development process based on the idea of data maturity was proposed in this paper. Base on the explanation of the theory of data maturity to control the process, the differences and relationship between data maturity and milestone was analyzed. The division method of data maturity level was discussed, and the corresponding relationship between each data maturity level and completion degree of the digital product model was illustrated also. In addition, the overall form of the product collaborative development process based on data maturity was provided. Finally, the detailed process between product structure design, process design and tooling design driven by each data maturity were explored, which realized the quantitative analysis and overall control of the product development process.

scholarly journals SHEDDING LIGHT ON CUSTOMER REQUIREMENT SPECIFICATIONS, FUNCTIONAL SPECIFICATIONS AND REQUIREMENTS LISTS – HOW ENGINEERS LEARN THE CORRECT DOCUMENTATION OF REQUIREMENTS

2015 ◽  
Author(s):  
Ilyas Mattmann ◽  
Sebastian Gramlich ◽  
Hermann Kloberdanz
Keyword(s):  
Product Development ◽  
Engineering Students ◽  
Development Process ◽  
Product Development Process ◽  
Customer Requirement ◽  
Specific Product ◽  
Customer Needs ◽  
Functional Specification ◽  
Requirement Specifications ◽  
Technical Products

Engineering students face a confusion of requirements and product properties during task clarifi-cation in product development projects. As requirements are mainly documented in the form of desired product properties, customer needs and expectations may not be sufficiently considered during the development of new and innovative products.This paper presents the results of a systematic litera-ture analysis of existing requirement documentation forms and analyses the documentation process as it is taught to engineering students. Requirements are often documented through a tripartite process of translating customer ex-pectations from the customer requirement specification to the functional specification, while the requirements list provides the base for the product development process. The contents of these documents appear theoretically different, however, they are barely distinguishable from each other in practice.Therefore, the paper provides a new model-based un-derstanding for the documentation of requirements through gradual concretisation of requirements during the product development process, leading gradually from customer needs and expectations to requirements. Engi-neering students must be able to gradually concretise requirements then document desired product properties to avoid early fixation on specific product properties. Un-dergraduate and graduate engineering students should be taught to consider requirements according to the pro-posed approach as it enables prospective engineers al-ready in the early phases of their engineering education to design highly complex technical products. Thus, the model provides a valuable base for formally supported requirements documentation and the systematic determi-nation of product properties

Sign in / Sign up

Export Citation Format

Share Document