• Journal of KIISE:Software and Applications
• /
• v.29 no.9
• /
• pp.605-618
• /
• 2002

The CBD (Component Based Development) is a requisite technique for the Time-To-Market, and a highly reusable component should be provided to develop a variety of domain applications with the use of components. To increase the reusability of components, they should be developed by analyzing requirements of many different kinds of domains. However, to analyze requirements of a variety of domains related to the components to be developed and to include them inside the components will give burden to developers. Also, providing only general components that have common facilities for the several domains is not easy to accomplish the time-to-market since there are other domains that the developers have to develop. As such, developing common component through the analysis of several domains at the time of the CD (Component Development) does not always guarantee high reusability of the component, but gives burden to developers to develop another development since such components have common functions. Considering this, this paper proposes the component customization technique to reuse common components as well as special components. The reusability of the component can be increased by providing changeability of the attribute, behavior and message flow of the component. This customization technique can change the message flow to integrate developed components or to provide new functions within the component. Also, provides a technique to replace the class existing within the component with other class or to exchange the integrated component with the component having a different function so that requirements from a variety of domains may be satisfied. As such, this technique can accept the requirements of several domains. As such, this customization technique is not only the component with a common function, but it also secures reusability components in the special domain.

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

• Journal of KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.589-604
• /
• 2006

Software product lines (SPL) are recently an emerging software reuse paradigm, which helps organizations develop their products from reusable core assets rather than from scratch. For developing these assets, understanding commonality and variability (C&V) is essential. A feature-oriented approach has been used extensively for C&V analysis in the SPL. However, this contains no proposal to systematically identify features and provide the rationale for the features. Further, the approach does not directly show how the results of C&V analysis will satisfy an organization's high-level business goals and provide the rationale for the C&V. Therefore, this paper presents a domain analysis method for the SPL based on goals, scenarios, and features in order to overcome some of the deficiencies and limitations of the feature-oriented approach. In particular, the paper proposes a domain requirements model (DRM) and a domain requirements modeling method based on the DRM. This method has been applied to the home integration system (HIS) domain to demonstrate its feasibility with a supporting tool, namely IDEAS. Our approach makes it possible to systematically identify the features and provide the rationale for both the features and the C&V.

• Journal of Korean Society of Environmental Engineers
• /
• v.28 no.11
• /
• pp.1154-1161
• /
• 2006

Air drying equipment was built as a device for reduction of dewatered cake from wastewater and waterworks sludge and to reproduce it by reusable matter. Dewatered cake was supplied into the air drying equipment which operated by air velocity of 80 m/sec, air rate 30 $m^3/min$ and air temperature of $40^{\circ}C$, and dried to produce the dried powder. The air drying equipment was composed of the air ejector which made high-speed fluid field, and cyclone which made circling fluid field. Dewatered cake was crushed at the high-speed zone as first step, and formed into dried powder of sphere shape by the collision between particles at the circling fluid zone.. Wastewater sludge with water content of 82.5 wt% was supplied 1.0 kg/min into air drying equipment and produced the dried powder which had the water content of 62.3 wt% and mass median diameter of 2.4 mm after process. At that time, it was analyzed that water removal rate was 0.1 $H_2O{\Delta}kg/min{\cdot}DS$ kg and air consumption was 170 $m^3/DS$ kg. Under same experimental conditions, when waterworks sludge was dried, water content of dried powder decrease to 47.5 wt% and mass median diameter decrease 2.1 mm and water removal rate increase 0.13 $H_2O{\Delta}kg/min{\cdot}DS$ kg. Air consumption increase 180 $m^3/DS$ kg with comparison to the results of wastewater sludge. Therefore, this technology was evaluated that drying the dewatered cake of waterworks sludge was more efficient than wastewater sludge, and also economical sludge handling technology due to drying the cake by only air.

• Journal of the Korean Society for Marine Environment & Energy
• /
• v.17 no.1
• /
• pp.42-45
• /
• 2014

Even though to discard the waste FRP (Fiber-Reinforced Plastic) is urgent and problematic, the way to do it has not been efficient. In our project team the FRP have been splitted into some layers which have different physical properties; mat and roving layers. Among those, the roving layer woven like a basket by bundles of glass fibers has been cut into reusable fibers called 'F-fiber'. F-fiber is 1 mm or 3 mm in width and 3 cm in length. It is used in fiber-reinforced concrete (FRC) with 0.5%, 0.7%, 1.0%, or 1.5% of volume ratio. Produced FRC was tested in compressive, tensile, and bending stress in contrast to the without-fiber (standard) concrete and 0.1% polypropylene reinforced concrete (PP-FRC). The tensile and bending stresses are more or less those of PP-FRC. The compressive stress, however, is similar (with 3 mm F-fiber) to or lower (with 1 mm F-fiber) than that of standard concrete. Conclusively the usage of the waste FRC in concrete is advised to be limited to the one where the compressive stress is not much critical.

• Journal of KIISE:Software and Applications
• /
• v.34 no.7
• /
• pp.635-645
• /
• 2007

Component technology has been widely accepted as an effective way for building software systems with reusable components, and Microsoft (MS) .NET is one of the recent representative component technologies. Model Driven Architecture (MDA) is a new development paradigm which generates software by transforming design models automatically and incrementally. Transformation of structural models in MDA has been successfully applied. However, transformation of dynamic models and pervasive services, such as transaction service, security service, synchronization service and object pooling are largely remains as an area for further research. The recent enterprise system has multi tier distributed architecture, and the functionality of early mentioned pervasive services is essential for this architecture. .NET platform can implement Component Object Model+ (COM+) component for supporting pervasive services by specify Attribute code. In this paper, we specify the functionalities of the COM+ component offering pervasive services, and then those functionalities are defined by UML profile. By using the profile, the Platform Specific Model (PSM) for .NET/C# is specified, and .NET components are automatically generated through our tool. The development productivity, extensibility, portability, and maintenance of software can be dramatically improved by using of the proposed methods.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.277-288
• /
• 2006

Product line engineering (PLE) is a new effective approach to software reuse, where applications are generated by instantiating a core asset which is a large-grained reuse unit. Hence, a core asset is a key element of PLE, and therefore the reusability of the core asset largely determines the success of PLE projects. A tore asset is a reusable part not a whole system, and supports not only variable functions but also common functions. However, there are limitations to evaluate reusability of core asset that has these unique characteristics. This paper proposes a comprehensive quality system for evaluating the reusability of core assets, based on ISO/IEC 9126. We first identify the key characteristics of core assets, and derive the set of quality attributes that characterizes the reusability of core assets. finally, we define metrics for each quality attribute. In addition, we provide guidelines for applying the metrics and perform a case study based on rental product line. Using the proposed quality system, reusability of core assets can be more effectively and correctly evaluated.

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

Software product line engineering is a method that prepares for the future reuse and supports to seamless reuse in application development process. Commonality and variability play central roles in all product line development processes. Reusable assets will become core assets by explicitly representing C&V. Indeed, the variabilities that art identified at each phase of core assets development have different levels of abstraction. In the past, these variabilities have been handled in an implicit manner and without distinguishing the characteristics of each core assets. In addition, previous approaches have depended on the experience and intuition of a domain expert to recognize commonality and variability. In this paper, we suggest a 2-dimensional analyzing method that analyzes the variabilities of core assets in software product line. In horizontal analysis process, the variation types are analyzed in requirements, architecture, and component that are produced at each phase of development process. In vertical analysis process, variations are analyzed in different abstract levels, in which the region of commonality is identified and the variation points are refined. By this method, the traceability of variations between core assets will be possible and core assets can be reused seamlessly.

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

• The KIPS Transactions:PartD
• /
• v.15D no.2
• /
• pp.235-246
• /
• 2008

Service-Oriented Architecture (SOA) is emerging as an effective approach for developing applications by dynamically discovering and composing reusable services. Generally, the benefits of SOA are known as low-development cost, high agility, high scalability, business level reuse, etc. However, a representative problem for widely applying SOA is the performance problem. This is caused by the nature of SOA such as service deployment and execution in distributed environment, heterogeneity of service platforms, use of a standard message format, etc. Therefore, performance problem has to be overcome to effectively apply SOA, and service performance has to be measured precisely to analyze where and why the problem has occurred. Prerequisite for this is a definition of a quality model to effectively measure service performance. However, current works on service performance lacks in defining a practical and precise quality model for measuring performance which adequately addresses the execution environment and features of SOA. Hence, in this paper, we define a quality model which includes a set of practical metrics for measuring service performance and an effective technique to measure the value of the proposed metrics. In addition, we apply the metrics for Hotel Reservation Service System (HRSS) to show the practicability and usefulness of the proposed metrics.