• The KIPS Transactions:PartD
• /
• v.13D no.7 s.110
• /
• pp.931-938
• /
• 2006

It is important to operate an education resources which could be integrated to an system. But most of existing education information system was not developed with standardization. It is need the core education asset and reusable education service to make a good education system. Consequently, it is needed to use Sharable Content Object Reference Model(SCORM) based contents managing in order to reuse the contents of education. And it needs assembling and producing method with reusable core asset of education system to develop the application program for education. In this thesis, we study the Teaching-Learning supporting system to support systematic education resources. Teaching-Learning support system is developed of educational domain assess through development process based on Model Driven Architecture(MDA) and core asset on each stage. Application program of education is developed using MDA automatic tool through analyzing and designing for contents storage which is based on contents meta model. We finally can develop the application software of education with low cost and high productivity by raising the reusability of education contents and by using the core asset to the whole development process.

• 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 KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• 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.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.643-645
• /
• 2001

B2C 쇼핑몰 시스템의 경우 사용자 인터페이스에 관련된 부분에서만 차이를 보일 뿐 시스템의 기능적인 요구사항과 아키텍처는 유사하며 재사용 가능한 컴포넌트나 COTS 제품을 사용하여 시스템의 많은 부분을 구축할 수 있다. 따라서 쇼핑몰 시스템 구축 시 매번 각 기능들을 설계하고 구현하는 것은 중복 투자를 하는 것과 같다. 이에 본 논문에서는 B2C 소핑몰 시스템의 공통 요구사항을 기반으로 B2C 쇼핑몰 시스템 구축을 위한 프로덕트 라인을 제시한다. 쇼핑몰 시스템 구축에 프로덕트 라인을 적용한다면 중복 투자를 줄이고 미리 준비한 COTS 제품이나 컴포넌트를 사용하여 좋은 품질의 시스템을 빠르게 구축할 수 있다. B2C 쇼핑몰 시스템의 프로덕트 라인을 제시하기 위해 프로덕트 라인의 Core Asset Development 프로세스를 수행하여 쇼핑몰 시스템에 특화된 Product Line Scope, Core Assets, Production Plane을 정의하였다. B2C 쇼핑몰 시스템의 Product Lien Scope는 웹 상에서 물건 판매, 주문 정보 접수, 고객 정보 관리 등의 공통점과 가격의 고정 여부, 검색 등 기타 기능, 공동구매 기능 등의 차이점으로 정의할 수 있다. Core Asset는 B2C 쇼핑몰 시스템의 아키텍처와 시험 및 설계 방법, 재사용 가능한 컴퍼넌트 목록 등이 있다. 마지막으로 Production Plan은 각각의 Core Asset의 부착 프로세스를 연결하여 제시한다. B2C 쇼핑몰 시스템의 Production Plan은 프로젝트 계획, 아키텍처 정체, 사용자 인터페이스 프로토타핑, 컴포넌트 획득, 구현, 통합 및 테스팅, 운영 단계로 구성된다.

• Journal of KIISE:Software and Applications
• /
• v.32 no.8
• /
• pp.717-729
• /
• 2005

Product Line Engineering (PLE) consists of two phases; Core Assets Development and Application Engineering. The core asset development is to model common features of members in a domain and to develop them. The application engineering is to effectively generate an application by instantiating the core asset. Today, PLE research mainly focuses on developing core assets, whereas activities and instructions for application engineering are weakly defined. Moreover, instructions of application engineering are not enough to be practically applied. To widely apply PLE to industry, researches on systematic and practical methods such as instantiation processes, instructions, and artifacts are needed. In this paper, we propose a practical PLE process, instructions, and artifacts about each activity. And then, we also present a case study to show applicability and practicality of the process proposed in this paper.

• Journal of KIISE:Software and Applications
• /
• v.33 no.12
• /
• pp.1008-1021
• /
• 2006

Product line engineering(PLE) is one of the recent and effective reuse approaches that enables developing a number of applications by instantiating a core asset. Elements of a core asset are product line architecture(PLA), component, and decision model. Among these elements, PLA is the key element since it defines the overall structure of the core asset. Although numerous PLE methodologies have been introduced, it is still unclear what should be the elements of a PLA and how to systematically instantiate it for specific applications. Formal specifications can play a key role in defining detailed and precise instantiation process. In this paper, we first present a meta model of PLA and show how to specify PLA in a formal language, Object-Z. Then, we propose instantiation rules using formal specification and those rules precisely define constraints for instantiating PLA. By applying the proposed formal specification, we believe PLA instantiation can be carried out precisely and correctly, yielding high quality software development.

• Korean Journal of Construction Engineering and Management
• /
• v.12 no.4
• /
• pp.40-49
• /
• 2011

A number of BTL projects for educational facilities have been augmented because of the increase of newtown development and deflationary policy of class size for learning efficiency. As the operation and maintenance costs rapidly increase, the budget for operation and maintenance is expected to be short. Therefore the asset management maximizing asset value is required to clarify the budget plan and distribution and provide a qualitatively high service. The main objective of this research is to establish asset valuation process in educational facilities delivered by BTL project. In order to meet the research objective, the asset valuation process is established by literature reviews, expert advice, and lessons learned from the developed countries. The developed process includes depreciation by internal accounting law, the core element of valuation, and asset valuation process. The results of the research will be help to offer the qualitatively high service and explain the standard of budget plan. It will assist commencing the asset management system.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.328-341
• /
• 2007

When the decision to initiate a software product line has been taken, the first step is the domain analysis describing the variability in the requirements, the second important step is the definition of a domain architecture that captures the overall structure of a series of closely related products. A domain architecture can be a core asset in product line by describing the commonalities and variabilities of the products contained in the software product line. The variabilities, which are identified at each phase of the core assets development, are diverse in the level of abstraction. Therefore, it is important to clearly define, systematically identify, and explicitly represent variability at the architectural level. However, it is difficult to identify and represent the variability which should be considered at the architecture level, because these may be appeared in architecture elements and in architecture configuration. In this paper, we suggest a method of developing domain architecture as a core asset in product line where commonality and variability are explicitly considered. First of all, we will describe a domain architecture metamodel that can explicitly define commonality and variability concepts by extending the Object Management Group's ($OMG^{TM}$ Reusable Asset Specification eRAS) model. Using the domain architecture metamodel, architecture elements are defined and the variations that can be identified at the architecture level are classified into two types in according th abstract level. Additionally, we describe a domain architecture where commonality and variability are explicitly considered on basis of this metamodel.

• Journal of KIISE:Software and Applications
• /
• v.32 no.9
• /
• pp.835-846
• /
• 2005

A Product Line (PL) is a set of products (applications) that share common assets in a domain. Product Line Engineering (PLE) is a set of principles, techniques, mechanisms, and processes that enables the instantiation of produce lines. Core assets, the common assets, are created and instantiated to make products in PLE. Model Driven Architecture (MDA) is a new software development paradigm that emphasizes its feasibility with automatically developing product. Therefore, we can get advantages of both of the two paradigms, PLE and MDA, if core assets are represented as PIM in MDA with predefined automatic mechanism. PLE framework in the PIM level has to be interpreted by MDA tools. However, we do not have a standard UML profile for representing core assets. The research about representing PLE framework is not enough to make automatically core assets and products. We represent core asset in PIM level in terms of structural view and semantic view. We also suggest a method for representing architecture, component, workflow, algorithm, and decision model. The method of representing framework with PLE and MDA is used to improve productivity, applicability, maintainability and qualify of product.