• Spatial Information Research
• /
• v.9 no.1
• /
• pp.107-124
• /
• 2001

The purpose of this research is to develop system and to establish methodology for managing spatial Database in Land Management Information System(LMIS). Spatial Database which is used by a various public department such as parcel survey and registry, land use planning and Land value appraisal in local government, is composed of parcel map, topographic map and zoning map. Spatial data has been constructed and managed by various department and then hard to maintain accuracy and coinsistency. So, it is important to establish the basic data management concept that source data(ex : parcel map, topographic map, zoning map, etc.) should be managed by responsible department. at the same time, application data for bussiness (ex : individual parcel price map) must be recomposed from base map by it's own objects. This is, Spatial data management system (SDMS) should be designed, developed according to this concept for managing consistency among data, reducing construction and management cost of database. Our SDMS was developed based on Open LMIS middleware architecture using OpenGIS CORBA specification for standard interface, RUP(Rational Unified Process) for development methodology, UML(Unified Modeling Language) for system design and VisiBroker, C++, CAD system for system implementation.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.383-390
• /
• 2002

System developments by components are accomplished by creating new software based on independent components having respective function. Generally, component-based software developments are expected to obtain profits caused by reuse of software, such as improvement of quality, rapid development, and efficiency of maintenance. In a component-based system, the most important goal and also key to success is to identify and construct high quality components that may increase reusability. Therefore, it is necessary for component developers to understand strong and weak points of existing component development methodologies in the aspect of identification of component, and to select the most appropriate methodology for the system to be constructed. It is also necessary for component developers to develop a new methodology enabling effective identification of independent components through modification and/or complementation of existing methodologies. The modification and complementation needs comparison and analysis of various existing methodologies. Accordingly, the this paper is to provide explanation for some widely used methodologies representing the existing component-based software development methodologies such as RUP(Rational Unified Process) of Rational company［1,9］, CBD96 of Computer Associates company［2,3］, UNIFACE of Compuware company［5］, and UML components methodology derived from extending of the component developing method of CBD96 by Cheesman and Daniels［4］. The this paper is also to point out respective problems of the representative existing methodologies. Furthermore, component identification methodologies are compared and analyzedon the whole through this paper.

• International Journal of Quality Innovation
• /
• v.7 no.2
• /
• pp.97-124
• /
• 2006

The purpose of this research is to create an expert risk-based piping system inspection model. The proposed system includes a risk-based piping inspection system and a piping inspection guideline system. The research procedure consists of three parts: the risk-based inspection model, the risk-based piping inspection model, and the piping inspection guideline system model. In this research procedure, a field plant visit is conducted to collect the related domestic information (Taiwan) and foreign standards and regulations for creating a strategic risk-based piping inspection and analysis system in accordance with the piping damage characteristics in the petrochemical industry. In accordance with various piping damage models and damage positions, petrochemical plants provide the optimal piping inspection planning tool for efficient piping risk prediction for enhancing plant operation safety.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2012.11a
• /
• pp.1500-1503
• /
• 2012

본 논문은 학부 종합설계 과목에 팀 프로젝트로, 안드로이드 어플리케이션에 소규모 소프트웨어 개발 방법론인 XP(eXtreme Programing)를 적용하고자 한다. XP는 작은 단위의 소프트웨어를 효율적으로 개발하기 위한 방법으로, RUP(Rational Unified Process)와 같은 대규모 소프트웨어 개발방법론보다 소프트웨어 개발 일정을 단축시킬 수 있고 요구사항 변경에 유연하다. 그러나 XP의 단점은 설계단계에서의 문서화가 부족한 것이다. 본 논문에서는 XP의 단점을 보완하기 위하여 설계단계에서 UML을 사용하여 문서화와 도식화를 시도하고자 한다.

• Journal of KIISE:Software and Applications
• /
• v.28 no.10
• /
• pp.720-731
• /
• 2001

Complexity metrics have been developed for the structured paradigm of software development are not suitable for use with the object-oriented(OO) paradigm, because they do not support key object-oriented concepts such as inheritance, polymorphism. message passing and encapsulation. There are many researches on OO software metrics such as program complexity or design metrics. But metrics measuring the complexity of classes at the OO analysis phase are needed because they provide earlier feedback to the development project. and earlier feedback means more effective developing and less costly maintenance. In this paper, we propose the new metrics to measure the complexity of analysis classes which draw out in the analysis based on RUP(Rational Unified Process). By the collaboration complexity, is denoted by CC, we mean the maximum number of the collaborations can be achieved with each of the collaborator and determine the potential complexity. And the interface complexity, is denoted by IC, shows the difficulty related to understand the interface of collaborators each other. We verify theoretically the suggested metrics for Weyuker's nine properties. Moreover, we show the computation results for analysis classes of the system which automatically respond to questions of the user using the text mining technique. As a result of the comparison of CC and CBO and WMC suggested by Chidamber and Kemerer, the class that have highly the proposed metric value maintain the high complexity at the design phase too. And the complexity can be represented by CC and IC more than CBO and WMC. We can expect that our metrics may provide us the earlier feedback and hence possible to predict the efforts, costs and time required to remainder processes. As a result, we expect to develop the cost-effective OO software by reviewing the complexity of analysis classes in the first stage of SDLC(Software Development Life Cycle).

• The Journal of Society for e-Business Studies
• /
• v.6 no.3
• /
• pp.209-225
• /
• 2001

This paper Proposes the individual roles for developing small web application systems based on the Client/Server architecture with the activities and artifacts of each role and cooperation. The roles of Web Server part (i.e. User Interface Designer, Web Designer, HTML Writer), the roles of Application Server part (i.e. Domain Expert, Application Developer, Tester) and the roles of DB Server part (i.e. Database Administrator, Data Designer) are described. Furthermore, the role of the Development Leader that participates in development and manages all works in project and finds the solutions of problems in project, is also discussed. The Domain Expert analyzes the domain of the application in order to send the artifacts to the Application Developer. Then the Application Developer analyzes, designs and implements the application based on the artifacts of the Domain Expert and integrates the implemented program modules. Roles are related each other in this way, and cooperate until the application development is completed. Finally, we analyzed and compared these roles with the roles of RUP(Rational Unified process) and web wave. Suggested roles in this paper turned out to be efficient compared to the roles of the existing large-scale methodology.