• IE interfaces
• /
• v.16 no.spc
• /
• pp.127-131
• /
• 2003

Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.18 no.11
• /
• pp.2593-2599
• /
• 2014

The way of mobile apps development using open source software have been becoming increasingly popular recently. In opensource mobile User Interface components case, there is tends to much more be used than mobile functional components. Because it is more easier that the reusability for implementation of User Interface. The problem is to apply as an open source mobile components selected for this reason all of the existing two studies. It is an open source software selection process and selection procedures shelf components. We revise to conform to existing mobile components selected for the study on open source software selection process in this paper. Can help increase the productivity of the mobile app development by the open source components to meet the functional requirements when developing mobile apps that can be easily retrieved and presented the selection process of this study is effective.

• ETRI Journal
• /
• v.28 no.4
• /
• pp.525-528
• /
• 2006

In this letter, we present a design of a single chip video decoder called advanced mobile video ASIC (A-MoVa) for mobile multimedia applications. This chip uses a mixed hardware/software architecture to improve both its performance and its flexibility. We designed the chip using a partition between the hardware and software blocks, and developed the architecture of an H.264 decoder based on the system-on-a-chip (SoC) platform. This chip contains 290,000 logic gates, 670,000 memory gates, and its size is $7.5\;mm{\times}7.5\;mm$ (using 0.25 micron 4-layers metal CMOS technology).

• 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.

• The Transactions of the Korea Information Processing Society
• /
• v.1 no.1
• /
• pp.23-37
• /
• 1994

In this paper, we design and implement the prototype system, and propose the Extended Faceted Classification. Scheme and the Hybrid Retrieval Method that support classifying the software components, storing in library, and efficient retrieval according to user's request. In order to designs the classification scheme, we identify several necessary items by analyzing basic classes of software components that are to be classified. Then, we classify the items by their characteristics, decide the facets, and compose the component descriptors. According to their basic characteristics, we store software components in the library by clustering their application domains and are assign weights to the facets and its items to describe the component characteristics. In order to retrieve the software components, we use the retrieval-by-query model, and the weights and similarity for easy retrieval of similar software components. As the result of applying proposed classification scheme and retrieval model, we can easily identify similar components and the process of classification become simple. Also, the construction of queries becomes simple, the control of the size and order of the components to be retrieved possible, and the retrieval effectiveness is improved.

• 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.

• Journal of the Korea Computer Industry Society
• /
• v.10 no.3
• /
• pp.87-92
• /
• 2009

Identification of reusable software components should guide user to come up with information about candidate components when a proper component is not found. Reusable software components which is able to confidential are a few risk and more effective than redesign or encode same components about each new application program. In this paper reusable processes are considered previously. Reusable model and the method for construction are analyzed for construction reusable components and reusable components which take this method are proposed. These problem will go far toward solving the design and coding of effective program.

• 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

• Journal of Institute of Control, Robotics and Systems
• /
• v.17 no.11
• /
• pp.1074-1081
• /
• 2011

As robotics systems are becoming more complex there is the need to promote component based robot development, where systems can be constructed as the composition and integration of reusable building block. One of the most important challenges facing component based robot development is safeguarding against software component failures and malfunctions. The health monitoring of the robot software is most fundamental factors not only to manage system at runtime but also to analysis information of software component in design phase of the robot application. And also as a lot of monitoring events are occurred during the execution of the robot software components, a simple data treatment and efficient memory management method is required. In this paper, we propose an efficient events monitoring and data management method by modeling robot software component and monitoring factors based on robot software framework. The monitoring factors, such as component execution runtime exception, Input/Output data, execution time, checkpoint-rollback are deduced and the detail monitoring events are defined. Furthermore, we define event record and monitor record pool suitable for robot software components and propose a efficient data management method. To verify the effectiveness and usefulness of the proposed approach, a monitoring module and user interface has been implemented using OPRoS robot software framework. The proposed monitoring module can be used as monitoring tool to analysis the software components in robot design phase and plugged into self-healing system to monitor the system health status at runtime in robot systems.

• Journal of Information Technology Applications and Management
• /
• v.20 no.3
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.