• Journal of Software Engineering Society
• /
• v.25 no.1
• /
• pp.11-18
• /
• 2012

Characteristic of decommissioning target facility investigate and understand is very important. because radioactive materials occurs in the decommissioning and dismantling, so it is difficult to use a general dismantling method. Decommissioning nuclear facilities, the characteristics of the target of research to predict the amount of decommissioning waste, decommission projects costing is largely utilized. For this purpose, we developed DEFACS(Decommissioning Facility Characterization DB System) that manage characteristic of decommissioning target facility. But nuclear facility decommissioning takes long time. so we inevitably developed system during decommissioning works, it occurs many system changes. For this reason, it is difficult to apply general development process, so we take CBD process that divide CD(Component Development) and CBSD(Component Based Software Development) for handling change of requirement. it make Component of the overall system for changes to minimize changes by strengthening the independence of components and processes due to changes in requirements were to minimize stopping of the process.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.241-248
• /
• 2003

CBD(Component Based Development)가 소프트웨어 개발의 새로운 패러다임으로 주목을 받으면서 최근 수년간 CBD를 적용한 소프트웨어 개발이 증가하고 있다. 국방과학연구소에서는 국방 소프트웨어 개발을 위한 표준 방법론으로 제시하고자 '국방 CBD 방법론'을 개발하고 있다. 본 논문에서는 '국방 CBD 방법론'에 대하여 소개한다. 방법론의 개발 프로세스 및 특징을 설명하고, 국방정보체계 개발에 적용되고 있는 국제 표준과의 연관성을 설명한다. 또한 방법론의 적용 사례로서 시범 개발한 상황보고 저작기를 소개한다. 웹 환경에서 컴포넌트 기반의 분산 시스템으로 구축된 상황보고 저작기의 아키텍쳐에 대해 설명하고, 웹 서비스 기술의 활용 사례를 설명한다.

• 한국IT서비스학회:학술대회논문집
• /
• 2002.06a
• /
• pp.152-157
• /
• 2002

컴포넌트 기반 개발 프로세스는 그 동안의 구조적 분석/설계 기법과 정보공학, 객체지향 등의 공학적 분석기술을 수용하고 있다. 따라서 CBD를 적용하려는 조직은 다양한 소프트웨어 공학적 기법과 아키텍처 설계 기술들을 습득해야 하였다. 또한 CBD의 핵심 역량인 반복적 개발 프로세스와 아키텍처 설계 역량을 갖추기 위해 각 개발업체 들은 CBD기술의 도입초기에 상당한 혼돈과 어려움을 겪어야 했다. 이에 본 논문에서는 CBD를 조직차원에서 습득하고 적용하는 과정을 5개의 단계로 나누고 각 단계의 목표를 설정한 컴포넌트 개발 프로세스 성숙도 모형을 제시한다. CDMM(Component based Development capability Maturity Model)으로 명명한 본 개발 능력 성숙도 모형은 소프트웨어 개발조직이 CBD를 습득하기 위해 어떤 단계를 거쳐야 하는지 또한 컴포넌트 개발을 위한 핵심기술이 어떤 것들인지를 제시한다. 이는 향후 CBD를 확산시키고 컴포넌트 기술을 통한 생산성향상과 소프트웨어 개발비 절감을 위해 기업과 국가의 정책적 지표로 활용할 수 있을 것이다.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.2
• /
• pp.211-223
• /
• 2005

The current software development type is based on CBD (Component Based Development). However, it requires a new component model that can support rapid and accurate component information on the web due to the cost increase of building new components using CBD. The purposed of this paper is to promptly develop an application on the web which fulfills users' demand and to provide specific interface regarding the small scales of distributed component in business domains. The e-BCOS(e-Business Component System) is the agent system for the users to register distributed components and to search component information, which would increase reusability through the e-business component development of distributed components in business domains and help the users understand the information about the component. Moreover, XML is employed for specification which allows smooth specification sharing and delivery to satisfy users' variable demands.

• Journal of KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.760-772
• /
• 2004

Component Based Development(CBD) Methodology is widely used in software development lifecycle to improve software quality. The Component Based Development(CBD) results to improve software reusability and reduce development term and cost. For this reason, lots of Enterprises are trying to make their processes to components. But, there has been few quality assurance or reusability testing action to those components. Most software component users can not know how their components are reusable and what extent their components satisfy to th eir quality requirements. For this reason, this paper suggests that software components can be measured their reusability by metrics proposed by this paper. We propose that in measuring software component reusability, there are direct metrics and indirect metrics. The results made by direct metrics are suggested to measure indirect metrics, so results to obtain reusability metrics.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.3
• /
• pp.211-235
• /
• 2004

Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System

• Proceedings of the Korea Information Processing Society Conference
• /
• 2002.11c
• /
• pp.1961-1964
• /
• 2002

현재의 소프트웨어 개발 패러다임은 전체 시스템에서 독립적인 업무 또는 기능을 수행하는 단위이고 유지보수에 필요한 교체 가능한 모듈로 재사용성과 대치성을 제공하는 컴포넌트기반 개발(CBD:Component Based Development)이 연구되고 있다. 기업이나 조직은 웹을 통한 비즈니스 기능의 확대에 따른 효과적이고 빠른 개발과 적용을 요구함에 따라, 에이전트를 통한 유연한 서비스를 제공하고자 한다. 본 논문에서는 비즈니스 영역에 대한 에이전트의 효과적인 개발과 적용을 위해 컴포넌트, e-비즈니스 에이전트, 자원, 관리 관점을 고려하여, e-비즈니스 에이전트지향 컴포넌트기반 개발 프로세스(ebA-CBD:e-business Agent oriented Component Based Development)를 제안한다. 특히, e-비지니스 에이전트의 식별과 명제를 위해 ebA-CBD 매트릭스, ebA Architecture Model과 ebA-Spec.을 제시하며, 사례를 통해 프로세스의 이해성 및 사용성을 제공하고자 한다.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.414-429
• /
• 2003

Component-based development(CBD) has been generalized in industry to master the complexity and reduce the development cost and time. However, current CBD practice is developing the component which is dependent on single application[l][2]. Therefore component variability is emphasized to reuse the component in many family members in a domain[8]. However, components are developed for the reason of replaceability rather than the reusability which is the main purpose of the component due to the insufficiency of the study of component variability definition and type[3]. In this paper, we formally specify the component variability reflecting the characteristics of the component to increase the component reusability. We define the logic variability which was recognized as the existing component variability and we propose all types of variability existing in the component by suggesting three more variability types. And we propose the component variability scope which makes us estimate and verify the number of cases of the variability when we customize the component. We propose these component variability types and scope through formal specification. By applying these techniques in developing components, we can develop high quality components reusable in many family members.

• Journal of KIISE:Software and Applications
• /
• v.32 no.3
• /
• pp.153-162
• /
• 2005

Component Based Development (CBD) is appealing as a technology to improve the productivity of software development through component reuse. Model Driven Architecture (MDA) is a new development paradigm which automatically generates application by transforming design models incrementally. Since both reusability of CBD and model transformation of MDA increase software productivity. integration of two technologies is desirable. To enable this technology integration, we need to devise a UML profile for specifying component design as a PIM. In this paper, we first define a meta-model for components, and propose a UML profile which is used to specify elements of component design as PIM. Since the proposed profile is based on Meta Object Facility (MOF) from which is MDA is derived, it is consistent and compatible with existing MDA methods and tools.

• Journal of Korea Multimedia Society
• /
• v.11 no.2
• /
• pp.237-246
• /
• 2008

According to the development of information & web technology and the amount of information increases, there have been numerous problems exposed. Although, software engineers try to overcome the limitations by using software agent and web service, there hasn't been satisfactory result in the paradigm of current software agent being a provider to the user's demand. Moreover, the latest configuration of software development is based on CBD (Component Based Development). However, to construct new component using CBD costs great deal of expenses and therefore, a new model which can acquirecomponent information on the web promptly and accurately with low expenses is required. In this paper, the repository management system which acquires and manages on the Semantic web is designed and compare them to the existing component repository management and present its analysis result. In addition, to overcome the limitations of existing component repository system; low accuracy of search result, restrictive search vocabulary and faulty information, the specific plan is presented to perform a knowledge search for the component.