• Journal of Technology Innovation
• /
• v.14 no.1
• /
• pp.1-30
• /
• 2006

The purpose of this paper is to analyze the organizational design and management of product development in creating new product architecture by an established firm. For the purpose, the paper put up the organizational design in the process of PDA(Personal Digital Assistant) development of Sharp and Casio which were Japanese major PDA firms in 1990s. PDA is the product born through architectural change from Electronic Organizer. Prior research on the product architecture change and organizational adaptation emphasized that an established firm is difficult to adapt to new product architecture due to the restriction of prior technology or organizational inertia. For overcoming these problems and successful development of new product architecture, organizational design and management in the process of product development becomes essential. In case of Sharp, corporate development project team had been used to overcome the restrictions from architectural knowledge accumulated through previous product. After launching first new PDA by corporate development project team, Sharp created a new division and pushed an evolution of PDA, when new PDA market start to grow up rapidly toward a major market segmentation. As a result, Sharp was able to build up stable PDA project trajectory. However, Casio was late for three years in launching of new PDA architecture because previous division charging of Electronic Organizer tried to develop first new PDA. Casio's PDA development was prohibited by engineers of previous division because new PDA architecture was inferior on user interface and display definition. That is, Casio's first PDA development was restricted by architectural knowledge of previous product.

• The KIPS Transactions:PartD
• /
• v.12D no.6 s.102
• /
• pp.857-862
• /
• 2005

MND(Ministry of National Defense) has developed MND AF(Ministry of National Defense Architecture Framework) and CADM(Core Architecture Data Model to guarantee interoperability among defense information systems. But, it is very difficult to manage architecture product documented through MND AF and CADM. So, there Is necessity for development of modeling tool and repository system which can develop architecture products and manage architecture product informations in common repository In this paper, we developed architecture product management system which supports development and management of meta model and architecture product of MND AF and CADM. Through architecture product management system architect of each agency can construct architecture product in a more effective and efficient way with modeling method and a user can search and refer useful architecture product informations using query function. Also, architecture product management system provides the basis for system integration and interoperability with integration, analysis and comparison of architecture product.

• Proceedings of the Technology Innovation Conference
• /
• 2005.06a
• /
• pp.44-68
• /
• 2005

The purpose of this paper is to analyze the organizational design and management of product development in creating new product architecture by an established firm. For the purpose, the paper put up the organizational design in the process of PDA(Personal Digital Assistant) development of Sharp and Casio which were Japanese major PDA firms in 1990s. PDA is the product born through architectural change from Electronic Organizer. Prior research on the product architecture change and organizational adaptation emphasized that an established firm is difficult to adapt to new product architecture due to the restriction of prior technology or organizational inertia. For overcoming these problems and successful development of new product architecture, organizational design and management in the process of product development becomes essential. In case of Sharp, corporate development project team had been used to overcome the restrictions from architectural knowledge accumulated through previous product. After launching first new PDA by corporate development project team, Sharp created a new division and pushed an evolution of PDA, when new PDA market start to grow up rapidly toward a major market segmentation. As a result, Sharp was able to build up stable PDA project trajectory. However, Casio was late for three years in launching of new PDA architecture because previous division charging of Electronic Organizer tried to develop first new PDA. Casio's PDA development was prohibited by engineers of previous division because new PDA architecture was inferior on user interface and display definition. That is, Casio's first PDA development was restricted by architectural knowledge of previous product.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W production technology, and support technology development. In case of USA, CMU/SEI (Carnegie Mellon University / Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• Journal of Korean Institute of Industrial Engineers
• /
• v.39 no.1
• /
• pp.1-9
• /
• 2013

The current manufacturers have generated tremendous amount of digitized product data to efficiently share and exchange it with other stakeholders or various software systems for product development. The digitized product data is a valuable asset for manufacturers, and has a potential to support high level strategic decision makings needed at many stages in product development. However, the lack of studies on extraction of key performance indicators(KPIs) from product data management(PDM) databases has prohibited manufacturers to use the product data to support the decision makings. Therefore this paper examines a possibility of an architecture that supports KPIs for evaluation of product development performances, by applying multidimensional product data model and on-line analytic processing(OLAP) to operational databases of product data management. To validate the architecture, the paper provides a prototype product data management system and OLAP applications that implement the multidimensional product data model and analytic processing.

• Journal of Korean Institute of Industrial Engineers
• /
• v.41 no.2
• /
• pp.162-172
• /
• 2015

This paper proposes a Product Data Management (PDM) system architecture that supports end-user computing for small and medium businesses (SMBs) in Korea to build and maintain efficient and sustainable information systems for their product development. Its open database with relational tables enables existing common application programs such as Microsoft office suites to access product data in PDM systems. In addition, the interactive query processor provided by database management systems helps design engineers to build ad hoc queries in standard SQL database language to response different data requirements during their product development. The PDM architecture with the open database allows design engineers or technical staffs in SMBs to build and maintain their application programs for product development by themselves. To show the feasibility of the proposed architecture, this study implemented a prototype PDM system based on the architecture and database, and represents real-world product data with the implemented PDM system.

• Journal of Institute of Control, Robotics and Systems
• /
• v.13 no.3
• /
• pp.256-262
• /
• 2007

In mass customization, the focus is variety and customization through flexibility and quick responsiveness. Mass customizers seek to provide personalized, custom-designed products at low prices to give customers exactly what they want and to provide sufficient variety in products and services. The idea of the product family is the most adequate approach to realize mass customization. An understanding of customer needs using functional decomposition becomes necessary to enhance the performance of the product family. This paper focuses on functional architecture modeling based on customer need regarding sub-functions for the product family. A quantitative functional model captures product functionality and customer need. Based on customer need ratings and sub-function, a product-function matrix was created. Additionally, a product-product matrix was generated to provide a similarity index among product families. A case study for implementing the functional architecture modeling was performed on the single use cameras.

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.773-782
• /
• 2007

Software produce line engineering is a method that prepares for future reuse and supports seamless reuse in the application development process. Analyzing the commonality and variability between products in a product line is one of the essential concerns that must be considered when building a product line. In this paper, we suggest to combine a product line engineering approach with RFID applications technology. More concretely, common activities are identified among the RFID-enable applications and the variability in the common activities is analyzed in detail. Then, we suggest reusable product line architecture as a product line asset. In addition, as a tool for supporting this research, a framework which provides both reusable product line architecture for REID applications and the components that implement concrete realization of the architecture is developed. Sharing a common architecture and reusing assets to deploy recurrent services may be considered an advantage in terms of economic significance and overall quality.

• Journal of Advanced Marine Engineering and Technology
• /
• v.32 no.4
• /
• pp.611-617
• /
• 2008

In ubiquitous environments, the content adaptable services can be dynamically provided to adapt the frequent changes of contexts. These services have common things that the kinds of context factors are limited to ubiquitous environment, though the contexts are flexible. To reuse service architecture can be reasonable for effective adaptable service. In this paper, we design a software architecture with product line techniques for content adaptable applications in ubiquitous environment. Description of product line is to define variation points and their variants, to find out the dependencies between them and to keep the model based architecture, their alternatives.