• Journal of Astronomy and Space Sciences
• /
• v.31 no.3
• /
• pp.265-276
• /
• 2014

The application of software engineering is not common in the development of astronomical observation system. While there were component-wise developments in the past, large-scale comprehensive system developments are more common in these days. In this study, current methodologies of development are reviewed to select a proper one for the development of astronomical observation system and the result of the application is presented. As the subject of this study, a project of operation software development for an astronomical observation system which runs on the ground is selected. And the output management technique based on Component Based Development which is one of the relatively recent methodologies has been applied. Since the nature of the system requires lots of arithmetic algorithms and it has great impact on the overall performance of the entire system, a prototype model is developed to verify major functions and performance. Consequently, it was possible to verify the compliance with the product requirements through the requirement tracing table and also it was possible to keep to the schedule. Besides, it was suggested that a few improvements could be possible based on the experience of the application of conventional output management technique. This study is the first application of the software development methodology in the domestic astronomical observation system area. The process and results of this study would contribute to the investigation for a more appropriate methodology in the area of similar system development.

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

CBD(Component-Based Development)는 이미 존재하는 소프트웨어 컴포넌트를 조립함으로써 시스템을 개발하는 방법이다. 컴포넌트를 이용하여 시스템을 개발하는 것은 개발시간과 비용을 줄이고, 생산성을 향상시키는 등 여러 가지 장점을 가진다. 그러나 여러 벤더에 의해 개발된 컴포넌트를 조립하는 것은 쉬운 일이 아니다. 이를 위해 컴포넌트가 어떤 문맥에서 사용되는지 이해하는 것이 필요하며 이 문맥은 아키텍쳐에 의해 결정된다. 따라서 본 논문에서는 컴포넌트 기반 개발을 위한 도메인 아키텍쳐를 제안한다. 도메인 아키텍쳐는 도메인을 구성하는 컴포넌트와 그들간의 관계에 대한 정보를 제공함으로써, 어플리케이션 개발을 쉽게 한다. 또한 도메인 아키텍쳐는 관련된 여러 시스템을 위한 아키텍쳐이므로, 도메인 아키텍쳐 상의 컴포넌트는 재사용이 높다.

• Proceedings of the Korea Society for Simulation Conference
• /
• 1999.10a
• /
• pp.7-11
• /
• 1999

Farmer 모델에 의하여 정의된 망관리 시스템 에이전트의 구성모델을 인터페이스 명세모델로의 매핑에 대하여 서술하였다. 인터페이스 명세모델은 컴포넌트 기반 개발 (Component Based Development)에서 구현과 설계를 구분하기위하여 제시하는 모델로서 본 논문에서는 TMN 에이전트 설계의 예로서 설명하였다. 특히 Farmer 모델에서의 측면의 개념을 반영하기 위하여 측면 인터페이스(Aspect Interface)의 개념을 도입하였다.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.11 no.3
• /
• pp.926-930
• /
• 2010

This paper is about a development framework, which is required to develop of security system is based on component. With applying of SDLC(system development life cycle) of information system, the application of information security products DLC is required at this point of time. In this paper, we review NIST requirement specification of development method, requirement criteria of SDLC in each stage, and major security guidelines of risk assessment. Also we are reviewed major security element of SDLC, and to aid understanding of security framework based on component, present the relationship fo security design and DFD in respect of spoofing for the outside entity based on threat tree STRIDE.

• Journal of Information Technology Services
• /
• v.5 no.3
• /
• pp.165-172
• /
• 2006

In this paper, we designed a new type of X-internet framework by using Flash component and server service API and analyzed its performance. Proposed X-internet framework uses Flash MX Professional 2004, Java, and software which opened middleware and database. Since proposed framework use the server service API that we developed in this paper and Flash player, this framework does not need server module. Proposed framework enables to obtain design with dynamic user interface compare to Web application and enables to reduce development time. In analytical results, it has been shown that proposed x-internet framework have efficient characteristics such as network traffic, low development cost and dynamic user interface implementation. Since proposed X-internet framework can operate in environment of current developer friendly, it is useful for development of various new application programs and we confirm it through Flash web mail implementation by using proposed x-internet framework.

• Journal of KIISE:Software and Applications
• /
• v.26 no.9
• /
• pp.1105-1113
• /
• 1999

객체 지향 소프트웨어의 확장과 더불어 소프트웨어의 재사용성의 중요도가 부각되면서 소프트웨어를 콤포넌트 단위로 구현하는 추세이다. 따라서 콤포넌트 기반의 소프트웨어 개발에서의 통합 테스트가 중요한 이슈로 떠오르고 있다. 그러나 콤포넌트들의 통합 테스트에 대한 연구는 미흡한 상태이다. 본 논문에서는 UML을 기반으로 체계적인 통합 테스트 모형을 제안하고. 나아가 본 논문에서는 "멀티미디어 정보처리 시스템"의 사례를 본 논문의 콤포넌트 통합 테스트 모형에 적용한 결과를 분석하여 기술한다. 콤포넌트 통합 테스트 모형은 UML(Unified Modeling Language)의 순서도(sequence diagram)와 협력도(collaboration diagram)를 이용하여 전체 시스템에서 UML의 사건흐름을 구성하는 콤포넌트들 사이의 인터페이스 영역에 존재하는 오류들을 추출한다. 그리고 UML을 기반으로 통합 테스트를 수행함으로써, 테스트 준비 작업을 줄이고, 기존의 UML 지원 도구들과 연계하여 테스트 자동화 도구의 구현을 앞당길 수 있다. 또한 시스템의 순차적 흐름 뿐 아니라, 동시에 수행되는 흐름에 대한 정보까지 모두 수용하여 테스트함으로써, 콤포넌트 기반의 분산 환경의 특성에 적합하다. Abstract As the object-oriented approach to software development becomes more mature, software development from pre-existing, independently developed components becomes an important aim of software engineering. Therefore, integration testing becomes an important aspect of component-based software development. However, there has been little work done in the area of the component-based integration testing. In this paper, we propose the "component integration test model" which is based on UML. Furthermore, we describe a case study on "Multimedia Information Processing System" conducted to analyse the result from which our model is applied. Our model extracts the faults, which exist in interfaces of components, using sequence diagram and collaboration diagram of UML(Unified Modeling Language). As our model is based on UML, the preparation effort for testing is reduced and its test-tools can be implemented more easily through linking existing UML tool. And our model accepts the information of concurrent flow represented by collaboration diagram as well as sequential flow, so it is more suitable to component-based distributed environment.based distributed environment.

• The KIPS Transactions:PartD
• /
• v.12D no.3 s.99
• /
• pp.385-394
• /
• 2005

In the component-based software development environment, it is important for developers who compose components to provide the information of dependence relationship between components. However it is not provided the information of dependence relationship of components. Therefore, it happens that the developer occasionally composes the components without knowing the dependence relation between the primitive components. In order to complement these disadvantages, In this paper, the design and implementation of dependence manager which provides the component dependence information for the development of integrity and persistence information system are established by defining the information about the dependence and relation between components as XML, managing them and providing a developer with the information about the dependence relationship between primitive components, we can establish. The components being created in the dependence manager show that the figure of reused matrix measurement is indicated from $89\%\;to\;95\%$, being included in confidence limits.

• Journal of Internet Computing and Services
• /
• v.9 no.5
• /
• pp.59-72
• /
• 2008

Computing systems in the modern era are expanding rapidly to include mobile-based businesses that make us of the various convergence distributed business process. This has lead to growing interest in the field of mobile embedded software development methodology, which has in turn lead to the proliferation of the embedded mobility. The use of CBD (Component Based Development) provides reusability, maintainability and portability, all of which are very important and focus issues to the business process. It also comes with the inherent productivity, quality and reliability of CBD. To make efficient use of CBD, though, clarified interface definitions for component integration are necessary. These definitions should be made up of collaborative hierarchical and horizontal architecture layers. Successful definitions should apply an effective framework made up of the architecture and process. In this paper, we describe an interface specification for small grained mobile embedded components(MEC) for the mobile embedded domain to meet maximum user requirements. We build and deploy the reconfigurable design patterns and components (in business domain categories) to make a component hierarchy and business logics for mobile embedded software. Proposed components specification plays a major role in development of the software for handling inconsistency in existing specification. It also includes plenty of specification information, using semantics and modeling based mechanisms to support business processes. We propose a development model of mobile embedded software using CBD for very complex and dynamic mobile business. We can apply it in a plug and play manner to develop the software. We verify that our framework supports very good productivity, quality and maintainability to meet the user's requirements in mobile business.

• Journal of Internet Computing and Services
• /
• v.6 no.2
• /
• pp.49-57
• /
• 2005

Connector's role between components is very important in the CBD(Component Based Development). The most connector has process ADL based rrethod was choosing FIFO method by component request. But in case many component's with various characteristics request It is difficult that this method operate efficiently, In this research, I did design and implement priority connector considering component's processing time, Also, I used Wright architecture for formal specification. Application result of proposed connector was spend more 388ms compares with existent FIFO method in total processing time. But this method could handle preferentially from components that have short processing time. Also, in case of component's waiting time in connector, existent FIFO method is 23323,1 ms and proposal method is 12731.27ms, So, proposal method could reduce waiting time for component process.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.103-110
• /
• 2002

In component-Based Software Development, the quality of indivisual component is play an important role in quality decision of the whole software. So we need the practical strategy for component testing. In general, component testing can divide focus into producer position and consumer position. In this paper, because the consumer position uses output of the producer position, testing domain is deployed in the producer position. We propose RUP based five step testing processes for component quality evaluation and implements a case study of EJB environment for appling our testing process. This paper shows that proposed five step processes are applicable to component quality evaluation.