• Asia pacific journal of information systems
• /
• 제9권1호
• /
• pp.115-142
• /
• 1999

Legacy applications are valuable assets that should be integrated into next generation business systems. To gain this advantage, progressive companies can reverse engineer the legacy business operations. This paper presents a form-driven object-oriented reverse engineering(FORE) methodology by the use of business forms to recover semantics of legacy applications. They retain the user-oriented contents of business and thus are easily understandable. Our form driven object-oriented reverse engineering methodology consists of five phases: form and usage analysis, form object slicing, object structure modeling, scenario design, and model integration. Knowledge about form structure and user interaction with legacy applications is used to capture the design semantics. An object model, which consists of an object structure model and scenario results from such form knowledge. The resulting object model is more likely to help reverse engineers understand and reuse legacy systems.

• Journal of Information Technology Applications and Management
• /
• 제9권1호
• /
• pp.85-96
• /
• 2002

Nowadays an information exchange on XML such as B2B electronic commerce is spreading. Therefore the systematic and stable management mechanism for storing the exchanged Information is needed. For this goal there are many research activities for connection between XML application and relational database. But because XML data have hierarchical structures and relational database can store only flat-structured data, we need to store XML data in object-oriented database that support hierarchical structure. Accordingly the modeling methodology for storing XML data in object-oriented database is needed. In order to build good quality application systems, modeling is an important first step. In 1997, the OMG adopted the UML as its standard modeling language. Since industry has warmly embraced UML, its popularity should become more important in the future. So a design methodology based on UML is need to develop efficiently XML applications. In this paper, we propose a unified design methodology for XML applications based on object- oriented database using UML. To this goal, first we introduce a XML modeling methodology to design W3C XML schema using UML and second we propose data modeling methodology for object-oriented database schema to store efficiently XML data in object-oriented databases.

• 대한전자공학회논문지
• /
• 제27권8호
• /
• pp.1231-1238
• /
• 1990

Though the studies on object-oriented software design which software component corresponds to phrases appearing in sentences of natural language have been going on, the design methodology has not been clearly set up yet. In this paper, the module structure of good quality was found not only by nouns that indicate class of object but also by subdividing sentences. I also suggested objected-oriented methodology observing the interdependency between objects and their relationships, and assessed the control problem of lift as an example.

• 한국정보처리학회논문지
• /
• 제6권6호
• /
• pp.1556-1562
• /
• 1999

융통성 있는 소프트웨어 개발을 위해 많은 객체지향방법론들이 제공되어 지고 있으나, 이러한 객체지향방법론들은 자동적으로 재사용을 제공하거나 건실한 소프트웨어 시스템을 만들지 못하고 있다. 따라서 이러한 객체지향 방법론들은 개발자에게 상세한 설계지침을 제공하지 못하고 있으며, 분석·설계자들로 이런 문제점들을 인정하고 방법론들을 향상시켜 나가려고 노력하고 있다. 이와 같이 분석·설계자들의 노력을 줄여 주면서 설계단계의 정보를 재사용할 수 있도록 제공하고자 하는 것이 설계패턴의 개념이며, 이러한 설계패턴과 객체지향 방법론은 상호 보완적인 관계를 가지면서 시스템을 개발하는데 유용한 설계 길잡이의 역할을 한다. 이에 본 논문에서는 객체지향 방법론 중에서 가장 많이 다루어지고 있는 OMT 방법론과 Gamma가 제안한 설계패턴 중 Facade, Mediator, Observer의 세 가지 설계패턴에 대한 상호작용을 보여주고, OMT방법론 내에 설계패턴을 적용함으로써 구체적인 설계지식과 재사용에 대한 명확한 해법을 제안한다.

• 한국정보처리학회논문지
• /
• 제6권3호
• /
• pp.622-632
• /
• 1999

As the complexity of software development is increasing due to networking, multimedia, and diverse system architecture, the need for effective software development methodology is increasing. Especially, due to software standard and internalization of software market, it is necessary to accept international quality such as ISO 9000-3. In addition, object oriented development methodology is required due to rapid propagation of OO technology and standardization. Recently, UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we UML was accepted by the OMG as standard object-oriented modeling language for distributed environment. When we develop Java and CORBA-based software, often UML is applied to Java and CORBA-based projects. However, current structural or OMT-based object-oriented methodologies. In this paper, we proposed UML-based development and concrete guidelines for each phase in order to apply UML to software development practically and effectively. Also, we define the transition guidelines and semantics between various development tasks. In addition, the analysis and design techniques of user interface and system development techniques needed in Web application development are presented.

• 한국전산구조공학회:학술대회논문집
• /
• 한국전산구조공학회 1995년도 봄 학술발표회 논문집
• /
• pp.160-169
• /
• 1995

This study presents an application of object-oriented methodology for structural dcsign process. A prototype system of integrated a structural design system is developed by introducing a structural analysis object model(SAOM) and structural design object model(SDOM). The SAOM module. which is modeled as a part of structural member, performs structural analysis using FEM approach and the SDOM module checks structural members based on Korea steel design standard. Above mentionedmodelsareabstraclencapsulatibleandreusable.

• 산업공학
• /
• 제16권1호
• /
• pp.70-84
• /
• 2003

Recently, object-oriented techniques have been used more and more for developments of an information system. But, established object-oriented methodologies are hard to express a business process of various abstract degrees in the analysis level and independent components of the system. They have difficulties in developing a large-scale information system of manufacturing industry such as PDM and CIM. This paper proposes an information system development methodology that imports the object-oriented IDEF0 (OOIDEF0) function model in analysis level. This methodology is made up of requirements gathering, system analysis, system design, and implementation. In requirements gathering level, organization diagram and interview technique are used for input data of OOIDEF0 function model. The OOIDEF0 function model, the interface model and function descriptions are made out in analysis level. Information objects and implementation objects are designed on the basis of the OOIDEF0 function model in design level. The database is built and programming is accomplished in implementation level. In order to prove the consistency and efficiency of the proposed methodology, the PDM system for ship production is modeled and prototyped.

• 대한전자공학회:학술대회논문집
• /
• 대한전자공학회 2000년도 ITC-CSCC -2
• /
• pp.723-726
• /
• 2000

In this paper, we present an abstract object-oriented plat-form model .suitable for the real-time distributed telecommunication system. The proposed platform is constructed upon the extended version of the real-time, distributed operating system, SROS(Scalable Real-time Operating System), that is developed at ETRI and successfully operated in the ATM switching system for several years. The object-oriented software development and maintenance methodology will resolve the current software crisis in the area of telecommunication and switching systems due to the everlasting maintenance about the huge amount of the existing software and the ever increasing needs for the better and new communication services. In general, an object-oriented software platform realizes the object-oriented methodology and possesses many good aspects like high productivity, better reusability, easy maintenance, et at. The platform is also designed to present the distributed multimedia service in addition to real-time event delivery. Recently, we have been implementing a couple of prototype bated on the proposed platform. Reflecting the evaluation results from these prototypes, the final platform specification will be determined.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제27권5호
• /
• pp.488-498
• /
• 2000

객체지향 방법론들은 이해하기 쉽고 확장성이 우수한 모델을 제공하기 때문에 현재 크고 복잡한 소프트웨어를 개발하기 위해서 널리 사용되고 있다. 객체지향 방법론들을 개발에 적용하기 위해서는, 첫째 개발방법론으로부터 과제 특성에 맞는 개발방법을 구성해야 하며, 둘째 이로부터 개발절차를 구성하여야 한다. 그러나 현재 제시되고 있는 객체지향 방법론들에서는 개발방법과 개발절차를 구성하는 과정을 개발자들의 이해와 직관에 의존하고 있다. 이를 개선하기 위해서 본 연구에서는 변용가능한 객체지향 방법론을 제안함으로써, 개발방법 구성의 문제를 체계적으로 지원하고자 한다. 개발방법의 구성을 체계적으로 지원하기 위하여 본 연구에서는 개발방법 구성의 문제를 계획구성의 문제로 변환하여 계획구성 기법을 적용한다. 계획구성의 과정에서 개발하고자하는 소프트웨어의 구조와 특성을 기술하는 아키텍쳐를 입력으로 받아들여 이에 적합한 개발방법이 계획된다. 아키텍쳐는 소프트웨어 개발과정에서 일관되게 유지되어야 하는 결정들을 기술하기 때문에 이를 중심으로 개발방법을 구성함으로써 소프트웨어의 특성을 효율적으로 반영할 수 있다.

• Journal of Information Technology Applications and Management
• /
• 제12권1호
• /
• pp.21-34
• /
• 2005

Object-oriented paradigm has required the fundamental changes in the developers' practice and orientation. However. the relevant literature has not still provided the solid practical methodology but created some myths regarding Use Case modeling. In this study. we attempt to 'demythologize' some key aspects of Use Case Modeling by describing what we have observed in our research and practice. In order to identify the developers' perceptions. the survey methodology was utilized. By discussing the differences between what must be done and what has been done. this study provides rich insights into the better understanding of the Use Case modeling and the successful development of object-oriented systems.