An approach to user knowledge and product architecture for knowledge lifecycle.

摘要

The incorporation of concepts and methods for understanding user needs in a user study and the use of them in product development are critical factors in an increasingly complex market and technological environment. The problem can be identified in three parts. First, user data from user studies cannot be effectively used in product development. Second, user knowledge is not recognized in product development. Third, the complexities of designing products for individual needs do not align well with the expectation of use. This research introduces the knowledge lifecycle interplay between the user study and product development phases. The goal of this research is to introduce a method, concept and model for the entire design process. The three proposed solutions are Object-Mediated User Knowledge Elicitation - OMUKE method, Pattern of User Knowledge - PUK, and Use Process Based Product Architecture - UPPA. OMUKE is a method proposed for capturing user knowledge. The method is built from an empirical research of existing methods (Convergent Perspective Approach), and an experimental study with the OMUKE software. Pattern of User Knowledge is a documenting tool used for transforming user knowledge into product architecture. The tool is based on the existing literature of knowledge transformation, such as Pattern Language. UPPA is a concept for mapping the use process to product architecture to match the users' expectation on operational pattern. UPPA derives from the analysis of an existing architectural framework. The results of the findings and evaluation by user-study experts indicated that the OMUKE method is consistent and effective in its identification of user knowledge. These experts recognize that user knowledge is a source for developing innovative products. The evaluation of patterns of user knowledge is evidence that function is a major factor in transforming user knowledge into product solutions. The evaluation of UPPA suggests that the concept is a means to define products that meets user needs based on user behavior. In conclusion, the method can be effectively used to capture user knowledge and use it to form the product architecture in knowledge lifecycle processes.