• 기술혁신연구
• /
• 제14권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.

• 정보처리학회논문지D
• /
• 제12D권6호
• /
• pp.857-862
• /
• 2005

현재 국방부에서는 국방정보체계간 상호운용성을 보장하기 위해 아키텍처산출물을 쉽고 일관성이 있게 개발할 수 있는 국방아키텍처프레임워크와 개발된 아키텍처산출물을 저장하는 핵심아키텍처데이터모델을 개발하였다. 하지만 작성된 아키텍처산출물을 문서로 관리하기에는 많은 어려움이 존재함으로, 아키텍처를 모델링할 수 있고 모델링된 정보를 공통의 저장소에 관리할 수 있는 모델링 도구 및 리포지토리 시스템이 필요하다. 본 논문에서는 국방아키텍처프레임워크와 핵심아키텍처데이터모델의 메타모델과 아키텍처산출물 작성 및 관리를 지원하는 아키텍처산출물 관리 시스템을 개발하였고 기존 시스템과 비교 평가하였다. 이를 통해 각 기관의 아키텍처개발자가 아키텍처산출물을 모델링 방법으로 보다 쉽고 일관성 있게 작성하고 관리할 수 있으며, 다양한 질의를 통해 시스템에서 관리되는 아키텍처산출물 정보를 유용하게 검색 및 조회하여 의사결정에 참조할 수 있다. 또한 작성된 아키텍처산출물을 통합하고 분석 및 비교하여 정보체계간 상호운용성과 비용 절감을 지원한다.

• 기술경영경제학회:학술대회논문집
• /
• 기술경영경제학회 2005년도 27회 하계학술발표회 논문집
• /
• 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.

• 한국IT서비스학회지
• /
• 제4권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.

• 한국IT서비스학회지
• /
• 제5권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.

• 대한산업공학회지
• /
• 제39권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.

• 대한산업공학회지
• /
• 제41권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.

• 제어로봇시스템학회논문지
• /
• 제13권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.

• 정보처리학회논문지D
• /
• 제14D권7호
• /
• pp.773-782
• /
• 2007

소프트웨어 프로덕트 라인은 소프트웨어 재사용에 대한 활동들을 미리 계획하고 개발 프로세스의 연속적인 부분으로 이루어지도록 지원하기 위한 방법이다. 이 방법에서 가장 중요한 기술은 관련된 시스템들, 즉 도메인에서 공통성과 가변성(commonality and variability: C&V)을 분석하고 관리하는 것이다. 본 논문에서는 소프트웨어 프로덕트 라인 방법과 RFID 적용 기술을 결합시키고자 한다. 즉, 각 기업 또는 도메인마다 RFID 기술을 도입하려고 할 때, 애플리케이션이 공통적으로 처리해야 하는 활동들을 식별하고 각 활동들이 가지는 가변요소들을 분석하여, 이를 재사용 가능한 소프트웨어 프로덕트 라인 아키텍처로 자산화 하는 방법을 제시한다. 또한 이를 실현하기 위하여 재사용 가능한 프로덕트 라인 아키텍처를 모델링 할 수 있고 식별된 공통된 기능들을 재사용 가능한 컴포넌트로 제공해주는 프레임워크를 개발한다. 공통된 아키텍처를 공유하고 반복적인 기능들을 자산으로 만들어 재사용하는 것은 경제적인 측면과 품질에서 상당한 이점을 가져다 준다.

• Journal of Advanced Marine Engineering and Technology
• /
• 제32권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.