• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

• Journal of KIISE:Software and Applications
• /
• v.35 no.2
• /
• pp.70-80
• /
• 2008

Today, businesses have to respond with flexibility and speed to ever-changing customer demand and market opportunities. Service-oriented architecture (SOA) is the best methodology for minimizing the complexity and the cost of enterprise-level infrastructure and for maximizing the productivity and the flexibility of an enterprise. Most of the enterprise-level SOA delivery strategies deal with the top-down approach, which organization has to define the business processes, to model business services, and to find the required services or to develop new services. However, a lot of peoples want to maximally reuse legacy component-based systems as well as to deliver SOA into their organizations. In this paper, we propose a bottom-up approach for identifying business services with proper granularity. It can improve the reusability and maintenance of services by considering not data I/O of components of legacy applications but GUI event patterns. Our proposed method is applied to MIS with 129 GUIs and 13 components. As a result, the valiance of the coupling value of components is increased five times and three business services are distinctly exposed. It also provides a 49% improvement in reducing the relationship problems between services over a service identification method using only partitioning information of components.

• Journal of Korea Multimedia Society
• /
• v.11 no.5
• /
• pp.710-727
• /
• 2008

Service-oriented computing systems have been issued by their properties of reducing software development time and effort by reusing functional service units. The reusability of services can effectively promote through loose coupling between services. But strong associations of object-oriented systems such as inheritance and aggregation create a rather tight coupling between objects. The component-based systems without inheritance and aggregation create a loose coupling between components. Thus components provide service realization at runtime using the functionality provided by their interfaces. Therefore legacy component-based systems need to have service-oriented computing concept in order to support functional service units efficiently. Also, conventional methods for service-oriented computing system have not suggested the clear classification of service layers, the clear service identification guideline introducing service layers and a service mapping method between serviceces of each layer. Therefore we suggest the service classification and the identification guideline of business view and implementation view introducing layers and propose a mapping between two views. That is, we research service layers, service identification, diversified service sizes and a service mapping method between services of each layer. This can be applied to legacy component-based system to extend to the service-oriented computing system.

• The Journal of Society for e-Business Studies
• /
• v.8 no.3
• /
• pp.241-257
• /
• 2003

XML is a global standard for the Internet and e-business, and its use is growing in proportion to the spreading speed of e-Commerce. Thus, a policy for providing more safe security service for exchanging e-documents within e-Commerce is necessary. XKMS, one of XML security specification, defines the protocol for distributing and registering public keys for verifying electronic signatures and enciphering e-documents of e-Commerce applications with various and complicate functions. In this paper, we propose X-KISS service reference model and implement service component based on standard specification. Also describes the analysis and security of XML key information service for safe e-Commerce, paying attention to the features of XML based security service. This reference model supported include public key location by given identifier information, the binding of such keys to identifier information. The client service component controls the number of locate threads and validate threads to analyze the minimum requirements of real-time key retrievals. This service modeling offers the security construction guideline for future domestic e-business frameworks.

• Proceedings of the Korea Association of Information Systems Conference
• /
• 2005.05a
• /
• pp.266-272
• /
• 2005

비즈니스 전략 및 환경이 정적인 환경에서 동적인 환경으로 변화의 필요성이 요구되는 유비쿼터스 환경에 제공되는 서비스가 언제, 어디서나, 쉽게 접근하기 위한 이동성을제공하기 위한 기술로 모바일 서비스의 중요성이 대두되고 있다. 현재 웹 서비스에서 사용하고 있는 요청-응답방식의 모바일 환경에서 일관성을 유지하기 힘들다. 서비스 지향 아키텍처를 기반으로 이동성을 고려한 아키텍처를 정의할 필요가 있다. 따라서 에이전트 컴퓨팅아키택처에 의해 상호운영성이 높은 모바일 에이전트 컴퓨팅을 통하여 모바일 환경에서 사용자의 접근을 용이하게 하고 컴포넌트를 이용한 개발의 효율성을 향상시킬 수 있어야 한다. 본 논문에서는 PDA 서비스를 위해 모바일 에이전트를 이용하여 이를 위한 컴퓨팅 환경을 제공하기 위해서 모바일 에이전트 아키텍처를 정의하고 각 레이어에서 식별된 컴포넌트를 개발하기 위한 프로세스를 제시하고자 한다.

• The KIPS Transactions:PartC
• /
• v.10C no.6
• /
• pp.769-778
• /
• 2003

XKMS(XML Key Management Specification), one of XML Security specification, defines the protocol for distributing and registering public keys for verifying digital signatures and enciphering XML documents of web service applications with various and complicate functions. In this paper, we propose XML Key Information protocol service model and implements reference model of protocol component based on standard specification. Also describes the analysis and security method of Key Information Service(XKIS) for Secure XML Web Service,paying attention to the features of XML based security service. This protocol component supported includes public key location by given identifier information, the binding of such keys to edentifier information. This reference model offers the security construction guideline for future domestric e-Business Frameworks.

• The KIPS Transactions:PartD
• /
• v.11D no.1
• /
• pp.133-142
• /
• 2004

The next generation of web applications will need to be larger, more complex, and flexible Agent-oriented systems have great potential for these e-commerce applications. Agents can dynamically discover and compose e-services and mediate interactions. Development of software agents with CBD (Component Based Development) has proved to be successful in increasing speed to market of development Projects, lowering the development cost and providing better qualify. In this thesis, we propose a systemic development process for software agents using component and UML (Unified Modeling Language). We suggest a etA (e-business Agent) CBD reference architecture for layer the related components through identification and classification of general agent and e-business agent. We also propose the ebA-CBD process that is a guideline to consider the best features of existing agent oriented software engineering methodologies, while grounding agent-oriented concepts in the same underlying semantic framework used by UML. We first developed the agent components specification and modeled it with Goal, Role, Interaction, and Architecture Model. Based on this, we developed e-CPIMAS (e-Commerce Product Information Mailing Agent System) as a case study that provides the product information's mailing service according to proposed process formality. We finally describe how these concepts may assist in increasing the efficiency reusability, productivity and quality to develop the business application and e-business agent.

• Journal of the Korea Computer Industry Society
• /
• v.5 no.4
• /
• pp.531-540
• /
• 2004

Development of Web service application requires the interoperability between various heterogeneous systems, extensibility to allow modification of business environment not of user interface, maintainability, flexibility and reusability As the properties of CBD (Component Based Development) have gradually become clear, attention has started to turn the smooth technology and methodology to solve the existing problems and issues the dynamic responds for the distributed web environments. In this paper, we identify some of the major architectural affecting CBD and describe the Design and Implementation of Security Framework for Application Server with Components. We identify the candidate components, model it using UML and layer it on the architecture. The frameworks will Provide the various security functions, such as incorporating with legacy security systems, supporting of J2EE, JAAS and Kerberos and assisting in increasing the tailorability of component.

• Smart Media Journal
• /
• v.6 no.2
• /
• pp.42-49
• /
• 2017

It is important to realize automation services by communicating in IoT with humans, objects & objects, and forming a common network. People used web like the most powerful network way to sharing things and communication. Therefore the efficiency method communication between each device and the web in IoT could be different from ones. The best method for high quality software product in web applications is software reuse ; Modules, classes, patterns, frameworks, and business components are reusable elements of various perspectives. Components is plugged with others through well-defined interfaces, which can overcome the operation and complexity of application development. A web-based distributed environment for IoT applications is a standard architecture use information collected from various devices for developing and using applications. For that reason, the network management which manages the constituent resources for the best service control in IoT application is required as a sub-layer support service in most applications as well as individual applications. In this paper, we measure to develop a network management system based not only by components but on heterogeneous internetworks. For procedure this, we clarify a component architecture for classifying and classify also the component needed in the IOT and network domain or order the type of real network management system.

• KIISE Transactions on Computing Practices
• /
• v.23 no.9
• /
• pp.535-541
• /
• 2017

Today, the scale of the computer software market has increased, and massive sized software has been developed to satisfy diverse requirements. In this context, software complexity is increasing and the quality of software is becoming more difficult to manage. In particular, software reuse is important for the improvement of the environments of legacy systems and new system development. In this paper, we propose a method to reuse modules that are certified by quality. Reusable levels are divided into code area (method, class, and component), project domain, and business levels. Based on the coupling and cohesion of software complexity, we propose a reusable module extraction mechanism with reusability metrics, which constructs a visualization of the "reusable module's chunk" based on the method and class levels. By applying reverse engineering to legacy projects, it is possible to identify reusable modules/objects/chunks. If these modules/objects/chunks are to be reused to develop an extension system or similar new system, we need to ensure software reliability in order to reduce the time and cost of software development.