• The Journal of Society for e-Business Studies
• /
• v.7 no.3
• /
• pp.219-240
• /
• 2002

The various software engineering techniques have been appeared in order to cope with the software crisis since 1980's. Currently, the research against the techniques likes the Design pattern, Component which improve the software's re-use are spread out. Also S/W Development Process are interested intensively which attempts the quality and a increasing productivity of software development with the basic policy. The design pattern is the solution against the problem which occurs repeat in a specific area. Many design pattern are developed and researched, but the method which accommodates the developed design pattern efficiently in the phase of analysis and design software development process is not good enough, so it is the actual applying technique is difficult. In this paper we suggest and the “UML components+” which is a efficient component development process from customizing EJB based the J2EE using the “UML Components” which is a component development methodology. Applying J2EE pattern efficiently with UML components+, there is a possibility of efficiency in the component development based pattern.

• The Journal of Information Technology
• /
• v.12 no.2
• /
• pp.31-37
• /
• 2009

Component-based software development [CBSD] is a new paradigm of recent software development. CBSD was started from reuse of software and study on software component technique. In order to improve produce and quality of software development, there is study on reuse of components lively and how to develop, share, and manage components effectively. In this study, I would like to suggest a method that is able to simply test a new application system by developing systems developed individually into components, registering them, and combining them.

• Journal of Information Technology Services
• /
• v.5 no.1
• /
• pp.177-190
• /
• 2006

Since their first inception a few decades ago, software components have received much attention mainly due to their alleged benefits of quality and productivity improvement. Despite this, it is yet to be agreed upon what and how components should be designed. This paper aims to bridge the gap by proposing a collaborative process where the voice of the customer is captured and documented by employing the event and entity models. These requirement elements (WHAT) are cross-tabulated in three relation matrices in accordance with the weights provided by the business users. The requirements are fed into the algorithm invented by the authors to optimize the component grouping (HOW). This collaborative process has been successfully validated at an enterprise wide software development project. The process was effective to help the users more actively involved in the design of the system and made the whole process faster and more adaptive to the changes.

• Journal of information and communication convergence engineering
• /
• v.21 no.1
• /
• pp.24-31
• /
• 2023

The solid-state drive (SSD) possesses higher input and output speeds, more resistance to physical shock, and lower latency compared with regular hard disks; hence, it is an increasingly popular storage device. However, tiny components on an internal printed circuit board (PCB) hinder the manual detection of malfunctioning components. With the rapid development of artificial intelligence technologies, automatic detection of components through convolutional neural networks (CNN) can provide a sound solution for this area. This study proposes applying the YOLOv5 model to SSD PCB component detection, which is the first step in detecting defective components. It achieves pioneering state-of-the-art results on the SSD PCB dataset. Contrast experiments are conducted with YOLOX, a neck-and-neck model with YOLOv5; evidently, YOLOv5 obtains an mAP@0.5 of 99.0%, essentially outperforming YOLOX. These experiments prove that the YOLOv5 model is effective for tiny object detection and can be used to study the second step of detecting defective components in the future.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.5
• /
• pp.1388-1400
• /
• 2000

An important technical issue in recent software development is to make needed software by the composition of components that are assemblable, and configurable, and independently extracted. The main advantage of component-based software development is reducing development time and cost. It is more cost-effective in development time to use components that are already developed than developing from scratch. There are two ways of component-based software development: one is to compose self-developed components, and the other is to by the components developed by third-parties and compose them. In the second case, existing non component programs must can be used for reuse in the component development. In this paper, we approach two methods for increase of reusability of Java program. First, we suggest the technique of extracting the elements suitable for the Beans component model from Java program, and then we show a process and a guideline of converting the extract elements into the Beans component model. Second, we suggest a technique of automatically extracting component information from the Java Beans component, expressing them in XML, its is possible to reuse the efficient component environment.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.8 no.3
• /
• pp.11-22
• /
• 2012

GIS have expanded the use-range to the various application area with the advantage of interface environment, the various geographical operation. topological analysis by the friendly user. Early GIS software was developed as monolithic tool in which all functions packed in the same software. But, these GIS software have the problems of the high cost of constructing system, closely related system architecture and the reusability. And there is a lack of interoperability between them because most of them have their own unique data format according to their practical application fields. So Component is a unit that it is cohesive software package which is able to be developed and arranged independently and connected with another component for necessary system composition. In this paper, we analyze the requirements for component design and component specifications based on the extracted components. Commonly used to extract components from the requirements of the GPS component-based development process is presented. These components extracted by the process can be used to assemble components only. In particular, applications for developers to add features specific case without affecting the other components that can be modify the component.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.29 no.4A
• /
• pp.399-414
• /
• 2004

In this paper, an evolution of software reliability engineering in a large-scale software project is summarized. The considered software consists of many components, called functional blocks in software of switching system. These functional blocks are served as the unit of coding and test, and the software is continuously updated by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components in software reliability and reliability evolution. We analyze the static characteristics of the software related to software reliability using collected failure data during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of system software, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto(G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources fur a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

• Journal of Internet Computing and Services
• /
• v.7 no.6
• /
• pp.1-10
• /
• 2006

A software development using components reuse is an useful method to reduce the software development cost. But a retrieval method by the keyword and category classifications is difficult to search an exact matching component due to components complexity in component reuse. Therefore, after different existing methods are examined and analyzed, an effective classification and retrieval method using XML specifications and the system architecture of components integrated management based on it are presented. Many discording elements of DTD which is component meta-expression exist in components retrieval. To compensate it, this retrieval method using estimations of precision and concision is effective one to catch considerable matching preference components. This method makes possible to retrieve suitable components having better priority due to searching similar matching components that are difficult in an existing keyword matching method.

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

Component Based Software Development has been recognized as a new software development paradigm, and received much attention among researchers. However, it requires software architecture based development to assure component reusability and efficient software development. This paper proposes the Component Based 4+1 View Model of software architecture to support component based software development. It is redefined on the basis of the existing 4+1 view model of software architecture developed by Kruchten. Also, we describe the elements of the view model in detail with UML. This architecture constructs the foundation of component based software such as increasing the understanding of software and providing the information about how the components interact with each other. It can be done by exposing the context for the use of software components to each views.

• Electronics and Telecommunications Trends
• /
• v.14 no.4 s.58
• /
• pp.1-9
• /
• 1999

In this paper, we summarize the lessons learned from the applications of the software reliability engineering to a large-scale software project. The considered software is the software system of the TDX-10 ISDN switching system. The considered software consists of many components, called functional blocks. These functional blocks serve as the unit of coding and test. The software is continuing to be developed by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components to software reliability and with the analysis of the reliability evolution. We analyze the static characteristics of the software related to software reliability using failure data collected during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of software of the TDX-10 ISDN system, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto (G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources for a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.