• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.705-714
• /
• 2001

The computing systems of today expanded business trade and distributed business process Internet. More and more systems are developed from components with exactly reusability, independency, and portability. Component based development is focused on advanced concepts rater than passive manipulation or source code in class library. The primary component construction in CBD. However, lead to an additional cost for reconstructing the new component with CBD model. It also difficult to serve component information with rapidly and exactly, which normalization model are not established, frequency user logging in Web caused overload. A lot of difficult issues and aspects of Component Based Development have to be investigated to develop good component-based products. There is no established normalization model which will guarantee a proper treatment of components. This paper elaborates on some of those aspects of web application to adapt user requirement with exactly and rapidly. Distributed components in this paper are used in the most tiny size on network and suggest the network-addressable interface based on business domain. We also discuss the internal and external specifications for grasping component internal and external relations of user requirements to be analyzed. The specifications are stored on Servlets after dividing the information between session and entity as an EJB (Enterprise JavaBeans) that are reusable unit size in business domain. The reusable units are used in business component through query to get business component. As a major contribution, we propose a systems model for registration, auto-arrange, search, test, and download component, which covers component reusability and component customization.

• Journal of KIISE:Software and Applications
• /
• v.29 no.10
• /
• pp.694-702
• /
• 2002

An application in Component-Based Software Development (CBSD) is built by 'composing'two kinds of components; One is a component that is made by current developer himself, and the other is a component that is from other developments. We define the former as a 'White-box component' and the latter as a 'Black-box component.' The error from the composition can be said to be caused by interactions of Black-box components and White-box components. This paper proposes a new testing technique for composition errors, and applies the technique to Enterprise Java Beans component architecture. Our technique selects test cases by injecting a fault only into the specific parts of a White-box component. This specific parts for injecting a fault are selected by analyzing composition patterns, and lead to make our test cases have a good effectiveness. We show the effectiveness of our test cases through an experiment. Moreover, we also mention an automation tool for our technique.

• 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

• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1172-1184
• /
• 2003

At present, new techniques based on different component reference models for the integration of component and system of different platforms, such as EJB and COM+, are introduced. The operation between the components in the identical component platform is realized by the composition at the source level. In case of the different component platform, however, it is impossible to use combined components in real condition although they are components of similar domain. In this paper we proposed a solution for the composition problem by using component transformation methodology based on model between EJB and COM+ components which are different components. For the composition between EJB and COM+ components, we compared and analyzed each reference model, then proposed the Virtual Component Model which is implementation independent and the Implementation Table for the mutual conversion. Reffering to the Virtual Component Model and the Implementation Table, we can generalize each Implementation model to the Virtual Component Model, make the Virtual Component Model which is implementation independent through the virtual component modeling, transform EJB and COM+ components selectively. Proposing the effective Model Transformation method to the different component platform, we can combine EJB and COM+ components.

• Proceedings of the Korea Database Society Conference
• /
• 2002.10a
• /
• pp.403-416
• /
• 2002

워크플로우 관리 시스템은 정부나 기업과 같은 조직의 작업을 처리하기 위한 비즈니스 프로세스를 컴퓨터를 기반으로 자동화함으로서 작업의 효율을 높이고 비용을 절감한다. 현재에 이르러 이런 워크플로우 시스템을 사용하는 조직들이 점차 거대화되어 가고 네트워크의 발달과 인터넷의 출현으로 인하여 워크플로우 시스템이 처리하여야 하는 작업의 수와 고객과 작업자 수 등이 빠른 속도로 증가하는 추세이다. 이런 추세에서 워크플로우 시스템은 거대 조직 환경에 적합한 워크플로우 시스템 아키텍쳐를 필요하게 된다. 이에 본 논문은 거대 조직 환경을 관리할 수 있는 워크플로우 관리 시스템으로 워크케이스 기반의 초대형 워크플로우 시스템의 아키텍쳐를 설계 및 구현 하고자 한다. 그리고 워크플로우 시스템 아키텍쳐를 분류, 분석하여 장단점을 가려내어 이를 기반으로 워크플로우 시스템 아키텍쳐의 성능을 예측하여 워크케이스 기반 워크플로우 시스템 아키텍쳐가 본 논문에서 제안하는 초대형 워크플로우 시스템의 아키텍쳐라는 것을 예측하여 본다. 또한 초대형 워크플로우 시스템을 위하하부 구조로 EJB(Enterprise Java Beans)를 사용하고 사용 이유를 기술한다. 본 논문에서는 이런 워크케이스 기반의 초대형 워크플로우 시스템 아키텍쳐를 위하여 개념적인 단계와 설계 단계, 구현 단계로 나누어 설계 및 구현을 하며 개념적인 단계에서는 워크케이스 기반 워크플로우 시스템 아키텍쳐에 대하여 상세히 기술하고 설계단계에서는 전체적인 기능 정의와 초대형 워크플로우 시스템의 구조를 설계한다. 그리고 구현 단계에서는 워크케이스 기반의 초대형 워크플로우 시스템 아키텍쳐를 실제 구현하기 위한 환경을 선택하고 구현 단계의 문제점들과 해결책을 기술한다. 다 솔레노이드방식 감압건조장치로 건조한 표고버섯으로 품위에 대한 유의성 검증결과, 표고버섯의 경우 온도별로는 색택과 복원률, 건조실 내부 압력별로는 수축률, 복원률에서 유의차가 있는 것으로 나타났다. 라. 본 연구에서 구명된 감압건조특성을 기초로 하여 배치식 감압건조기를 설계 제작에 활용하고자 한다.ational banks. Several financial interchange standards which are involved in B2B business of e-procurement, e-placement, e-payment are also investigated.. monocytogenes, E. coli 및 S. enteritidis에 대한 키토산의 최소저해농도는 각각 0.1461 mg/mL, 0.2419 mg/mL, 0.0980 mg/mL 및 0.0490 mg/mL로 측정되었다. 또한 2%(v/v) 초산 자체의 최소저해농도를 측정한 결과, B. cereus, L. mosocytogenes, E. eoli에 대해서는 control과 비교시 유의적인 항균효과는 나타나지 않았다. 반면에 S. enteritidis의 경우는 배양시간 4시간까지는 항균활성을 나타내었지만, 8시간 이후부터는 S. enteritidis의 성장이 control 보다 높아져 배양시간 20시간에서는 control 보다 약 2배 이상 균주의 성장을 촉진시켰다.차에 따른 개별화 학습을 가능하게 할 뿐만 아니라 능동적인 참여를 유도하여 학습효율을 높일 수 있을 것으로 기대된다.향은 패션마케팅의 정의와 적용범위를 축소시킬 수 있는 위험을 내재한 것으로 보여진다. 그런가 하면, 많이 다루어진 주제라 할지라도 개념이나 용어가 통일되지 않고