• International Journal of Computer Science & Network Security
• /
• v.22 no.9
• /
• pp.143-148
• /
• 2022

Component-based software development (CBD) is a methodology that has been embraced by the software industry to accelerate development, save costs and timelines, minimize testing requirements, and boost quality and output. Compared to the conventional software development approach, this led to the system's development being completed more quickly. By choosing components, identifying systems, and evaluating those systems, CBSE contributes significantly to the software development process. The objective of CBSE is to codify and standardize all disciplines that support CBD-related operations. Analysis of the comparison between component-based and scripting technologies reveals that, in terms of qualitative performance, component-based technologies scale more effectively. Further study and application of CBSE are directly related to the CBD approach's success. This paper explores the introductory concepts and comparative analysis related to component-based software engineering which have been around for a while, but proper adaption of CBSE are still lacking issues are also focused.

• International Journal of Computer Science & Network Security
• /
• v.23 no.12
• /
• pp.187-193
• /
• 2023

Large software systems are being produced with a noticeably higher level of quality with component-based software engineering (CBSE), which places a strong emphasis on breaking down engineered systems into logical or functional components with clearly defined interfaces for inter-component communication. The component-based software engineering is applicable for the commercial products of open-source software. Software metrics play a major role in application development which improves the quantitative measurement of analyzing, scheduling, and reiterating the software module. This methodology will provide an improved result in the process, of better quality and higher usage of software development. The major concern is about the software complexity which is focused on the development and deployment of software. Software metrics will provide an accurate result of software quality, risk, reliability, functionality, and reusability of the component. The proposed metrics are used to assess many aspects of the process, including efficiency, reusability, product interaction, and process complexity. The details description of the various software quality metrics that may be found in the literature on software engineering. In this study, it is explored the advantages and disadvantages of the various software metrics. The topic of component-based software engineering is discussed in this paper along with metrics for software quality, object-oriented metrics, and improved performance.

• Journal of KIISE:Software and Applications
• /
• v.31 no.5
• /
• pp.677-696
• /
• 2004

Component-based software engineering (CBSE) composes reusable components and develops applications with the components. CBSE is admitted to be a new paradigm that reduces the costs and times to develop software systems. The high quality of component designs can be assured if the consistency and correctness among the elements of a component are verified with formal specifications. Current formal languages for components include only some parts of contracts between interfaces, structural aspects and behavioral aspects of component, component-based system, component composition and variability. Therefore, it is not adequate to use current formal languages in all steps of a component design process. In this paper, we suggest a formal language to specify component designs Component-Z. Component-Z extends Object-Z, adds new notations to specify components. It can be possible to specify interfaces, the inner structure of a component, inner workflows, and workflows among interfaces with Component-Z. In addition, Component-Z provides the notations and semantics to specify variability with variation points, variants and required interfaces. The relation between interfaces and components is defined with mapping schemas. Parallel operator is used to specify component composition. It can be possible to describe deployed components with the specifications of component-based systems. Therefore, the formal specification language proposed in this paper can represent all elements to design components. In the case study, we specify an account management system in a bank so that we show that Component-Z can be used in all steps of component design.

• The KIPS Transactions:PartD
• /
• v.8D no.1
• /
• pp.99-104
• /
• 2001

As a plan to counteract solving software crisis, the technology that is called Component Based Software Engineering (CBSE or Componentware) is introsuced. Component Based Software Developement (CBSD) Processes as one of the technique among CBSE have been proposed. Component specification activities among CBSD Processed are necessary and important for generating feusable component. However, the existing CBSD processed can't ensure the correctness in requirements are reflected. In this paper, we propose that formal activities wgich specify component using formal specification language Z which is verified with the ability of analysis and logicality. The proposed activities are composed of 5 tasks and 12 subtasks. By presenting specific 19 products, it is also proposed that component specification activities which are the base of CBSD for reusing. The proposed activities are able to improve qualities of component through correctness and verification of requirements specification of users in the early step of component-based software process.

• Journal of KIISE:Software and Applications
• /
• v.33 no.6
• /
• pp.525-538
• /
• 2006

Component-Based Software Engineering (CBSE) is widely accepted as new paradigms for building applications with reusable assets. Mismatch problems occur while integrating the assets and make a burden in CBSE. Therefore, a larger-grained reuse unit than a component such as a framework is required, and it consists of relevant components, connectors and domain-specific architecture. The benefits of frameworks over components are commonly known, however, the key elements and internal structure of framework has not been clearly defined. We believe most of the framework models proposed in recent works remain at conceptual level. In this paper, we propose a practical-level framework reference model, and define key elements of frameworks. The research goal is to precisely identify concrete elements of a framework, inter-connection of components within a framework, extended notion of connectors, and tailored meaning of architecture In a framework. Hence, the proposed framework can be practically implemented in common object-oriented languages and with middleware such as lava, J2EE, CORBA Component Model (CCM) and NET.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.2
• /
• pp.9-18
• /
• 2002

SECOS(SoonChunHyang E-Commerce System) is the e-commerce system which was developed by e-commerce software research center in soonchunhyang univ. The system was composed of payment system, retrieving system and framework being used to combine these systems. The modules in the system was composed of components which was developed by CBSE(Component Based Software Engineering) method. In this paper. we implement the Role Based Access Control(RBAC) component for access control of SECOS. We use Attribute Certificates(ACs) in order to implement RBAC in the distributed retrieving system, and implement Attribute Authorities(AAs) which can provide ACs. The Proposed system is implemented by EIB component based JAVA.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.489-491
• /
• 2000

컴포넌트 기반의 소프트웨어가 개발되어짐에 따라 소프트웨어공학 측면에서 컴포넌트 기반의 소프트웨어 개발을 위한 컴포넌트 기반 소프트웨어공학(CBSE: Component Based Software Engineering)에 대한 연구가 진행되고 있다[1]. 컴포넌트 기반의 소프트웨어를 개발하는데 있어서 최대한 효율성과 생산성을 증가시키기 위해서는 개발초기, 즉 요구사항 분석단계에서 기존에 개발되어진 컴포넌트들 중에 사용자가 요구하는 역할을 수행하는 적절한 후보 컴포넌트를 추출할 수 있어야 한다. 따라서 본 논문에서는 XML의 특성을 활용한 요구사항과 컴포넌트 명세 언어를 정의하고 이를 통해 정형화된 요구사항으로부터 시스템 개발에 필요한 컴포넌트들을 추출하는 방안을 제시하고자 한다.

• International Journal of Computer Science & Network Security
• /
• v.22 no.2
• /
• pp.115-122
• /
• 2022

Component adaptation is widely recognized as one of the main problems of the components, used in component based software engineering (CBSE). We developed methods to adjust the components classified by the keywords. Three main methods are discussed in this article those methods are combined with several domain component interfaces, high level simple notation for the adapter design patterns. The automated process for classifying high-level components are using adaptation is novel to software engineering domain. All Specifications and many technologies for re-using software, CBD and further developments have been emerged in recent years. The effects of these technologies on program quality or software costs must be analyzed. The risk concerns a single technology and must identify its combinations. In this paper, we are going to discuss the methods to adapt components of different technologies

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10c
• /
• pp.337-339
• /
• 2000

CBSE(Component Based Software Engineering)은 소프트웨어 엔지니어링 세계에서 소프트웨어 개발 패러다임으로 바뀌고 있다. 이 영향은 전자상거래 소프트웨어의 개발에도 미치고 있다. 본 논문의 전자상거래 전문 검색 시스템은 이전의 IHWA(Information Harvest WArehouse) 검색엔진을 기초로 한다. 본 논문에서 CBSD에 입각해 IHWA 기반의 사용자 훈련가능한 전자상거래 검색 시스템의 새롭게 수정된 컴포넌트 구조를 소개한다. 전체 시스템 구조는 UML을 사용해 모델링 되었다.

• Journal of Internet Computing and Services
• /
• v.3 no.4
• /
• pp.71-82
• /
• 2002

Recently. component-based software development is getting accepted in industry as a new effective software development paradigm, Since an introduction of component-based software engineering(CBSE) at later 90's, the CBSD research has focused largely on component modeling, methodology, architecture and platform, However. as the number of components available on the market increases, it becomes more important to make metrics to measure the various characteristics of components. In this paper. we propose metrics for measuring the complexity, customizability, and resuability of software components, Complexity of metrics can be used to evaluate the complexity of components Customizability is used to measure how efficiently and widely the components can be customized for specific requirements organization, Resuability can be used to measure the degree of features that is reused in building applications.