• Journal of Advanced Navigation Technology
• /
• v.27 no.4
• /
• pp.429-435
• /
• 2023

The increasing complexity of avionics systems has emphasized the portability and reusability of software components. In this paper, a structural design method for IOSS (Input Output Service Segment) and TSS (Transport Service Segment) complying with the FACE (The Future Airborne Capability Environment) standard in the VxWorks 653 operating environment that satisfies ARINC 653 requirements is described. IOSS and TSS operate independently in different partitions to minimize time/space separation and the influence of other software, and to increase portability and reusability, strategy patterns among design patterns are applied. In addition, IOSS provides external interface service by applying distributed IO service structure, and among external interfaces, the ARINC 664 P7 interface of FACE-compliant equipment is placed in TSS to optimize the data movement path.

• Journal of KIISE:Software and Applications
• /
• v.32 no.2
• /
• pp.119-127
• /
• 2005

Product line analysis is an activity for analyzing requirements, their relationships, and constraints in a product line before engineering product line assets (e.g., architectures and components). A feature-oriented commonality and variability analysis (called feature modeling) has been considered an essential part of product line analysis. Commonality and variability analysis, although critical, is not sufficient to develop reusable and adaptable product line assets. Dependencies among features and feature binding time also have significant influences on the design of product line assets. In this paper. we propose a feature-oriented product line analysis model that extends the existing feature model in terms of three aspects (i.e., feature commonality and variability, feature dependency, and feature binding time). To validate the consistency among the three aspects we formally define the feature-oriented product line analysis model and provide rules for checking consistency.

• 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 Industrial Information Systems
• /
• v.9 no.1
• /
• pp.49-55
• /
• 2004

E-Learning standard SCORM has been prepared in the United States to establish the efficient operation and development of e-Learning. The learning object of the current SCORM focuses on easy development and reusability in the professor's side. In this study instead, we present a SCC (Sharable Content Collection) scheme which can provide various studying opportunities to the learners. Constructing an efficient SCC requires improving the SCO (Sharable Content Object), a key ingredient of SCORM, and analyzing the cyber lecture into components. In this way we suggest a method to improve the existing learning objects and present an e-Learning model based on SCC.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07a
• /
• pp.634-636
• /
• 2005

모바일 단말 기반 동영상 서비스 기술에 관한 연구는 현재 활발히 수행되고 있으며, 유선 인터넷 기반에서 상용화가 가능한 기술 분야까지도 모바일 단말의 성능과 무선 네트워크 플랫폼의 빠른 발전에 힘입어 모바일에 응용하고자하는 시도 또한 계속되고 있다. 현재 모바일 단말 기반 영상서비스와 관련된 기술은 하드웨어적으로 구현하여 운영되고 있다. 그러나 하드웨어 기반으로 구현되어 서비스되고 있는 현재의 서비스 형태는 새로운 동영상 코덱 알고리즘과 동영상 데이터 통신에 대한 여러 제어 구조 변화에 대하여 탄력적으로 대응할 수 없다는 단점을 지니고 있다. 따라서 하드웨어적으로 구현된 영상서비스 기술을 소프트웨어적으로 처리하기 위한 디코더 개발은 필수적이라고 볼 수 있다. 이러한 소프트웨어 디코더의 개발을 통하여 새로운 동영상 미디어 플레이어 개발과 동영상 데이터 전송 방법 및 트래픽 제어 등과 같은 부가적인 기술의 변화에 즉각적 대응이 가능하다. 또한 추가적인 하드웨어 칩의 내장에 따른 모바일 단말기의 제조 원가절감과 모바일 단말기 재사용을 통한 자원 절감에 많은 기여가 가능하다. 본 논문에서는 WIPI 플랫폼을 기반으로 컴포넌트 기반 설계를 이용한 H.264 동영상 소프트웨어 디코더를 설계한다.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.513-522
• /
• 2008

Service-Oriented Architecture(SOA) is an method to develop applications by developing and publishing reusable services which potentially be used in various applications, and discovering and composing right services dynamically. SOA adopts a paradigm of publish-discover-invoke, which is considerably different from object-oriented and component-based development(CBD) approaches. The service in SOA is different from function in procedural programming, object in object-oriented programming, and component in CBD, and its fundamental requirement is a high level of reusability and applicability. In SOA, service providers and service consumers are loosely coupled since the providers try to develop reusable services and the consumers try to locate right services without knowing much about the providers and their published services. Moreover, the process of searching, choosing and invoking right services is not presented in conventional programming paradigms. Therefore, conventional approaches to developing user interfaces and invoking the functionality on servers through JSP, and RMI in object-oriented programming cannot well be applicable to designing clients’ programs in SOA. Therefore, there is a high demand for a practical and systematic process for developing clients’ applications, and the such a process should be devised by considering key characteristics of services and SOA. However, little work on this area is known to date, and there has not a process for client side just except few guide lines for developing service client. In this paper, we propose a practical and systematic development process for developing clients' applications in SOA. Then, we define instructions for carrying out each activity in the process. To show the applicability of the proposed work, we show the result of applying our process in developing a services application for searching and booking hotels.

• Journal of KIISE:Software and Applications
• /
• v.36 no.6
• /
• pp.431-442
• /
• 2009

The Software Product Line (SPL) engineering is one of the most promising software development paradigms. With Feature-Oriented Reuse Method (FORM), reusable and flexible components can be built to aid the delivery of various software products such as mobile phone and digital TV applications based on commonalities and variabilities identified during Feature modeling. Model Driven Architecture (MDA) is also an emerging technology which supports developing software products to work on different platforms with platform independent models (PIM). Combining advantages of these two approaches is helpful to build a group of software products which share common Features while working on various platforms. As first step to combine FORM with MDA, we extend UML2.0 with profiles by which FORM architectures and parameterized Statecharts can be modeled. Secondly, we provide rules to examine whether Features are allocated at positions of elements of Statecharts consistently between a Feature model and a parameterized Statechart. Some rules are designed to check the consistency between FORM architectures and parameterized Statecharts. A case study on an elevator control system is provided to demonstrate the feasibility of our modeling approach and consistency checking rules.

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• The KIPS Transactions:PartD
• /
• v.17D no.1
• /
• pp.25-40
• /
• 2010

Service-Oriented Architecture (SOA) is a development paradigm for reusing services as an independent reuse unit. A service delivers a cohesive functionality through its external interface. Since services have unique characteristics which are not typically presented in conventional development approaches, there is a demand for effective approaches to developing services. Most of the current SOA methodologies presenta process where services are designed and developed from the requirements rather than reusing existing assets, which demands high cost and effort. Hence, a desirable approach is to be able to develop services by migrating from their existing legacy systems such as object-oriented system. A difficulty in this migration is that objects in object-oriented systems reveal characteristics which differ considerably from those of services. That is, objects are designed without considering commonalities among several consumers. In this paper, we first define mapping relationships between key artifacts in object-oriented system and those in SOA services. By these relationships and considering commonalities among several applications in a domain, we propose three systematic methods to migrate from object-oriented system to SOA services. Each method consists of a list of input and output artifacts and detailed guidelines which are performed in order. Through these methods, service developers can easily develop services with less effort.

• Journal of KIISE:Computing Practices and Letters
• /
• v.14 no.1
• /
• pp.52-62
• /
• 2008

As various types of embedded devices are widely used, a technology that supports reuse of applications on multiple platforms is needed in order for time-to-market development of the applications. The interface middleware is one of such technology and it hides platform dependency from application programmers. Existing interface middleware such as the MT project, Xenomai and Legacy2linux have limitation in that the APIs provided by each of these middleware are fixed to a specific operating system, and the middleware does not provide dynamic expansion of its API set. In this paper, we propose a middleware which hides operating system dependencies and enables porting of applications on various operating systems. In addition, the middleware has scalable structure so that it is suitable for resource-limited embedded systems. The overhead of the middleware, i.e., the time delay occurred by the middleware is between $0.3{\mu}sec\;and\;5{\mu}sec$ in most cases. We believe that the amount of overhead is reasonable and does not hurt the performance of applications.