• Asia pacific journal of information systems
• /
• v.9 no.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
• /
• v.9 no.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.

• Journal of the Korean Institute of Telematics and Electronics
• /
• v.27 no.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.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.6
• /
• pp.1556-1562
• /
• 1999

The various kinds of object-oriented methodology were provided for the development of flexible software. However, they do not automatically make the reusable and robust Object-Oriented software systems. The Object-Oriented mechanism is simply used as the means to obtain the aim. We have heard many complaints from the developers that methods did not give concrete design guidance. Methodologists' effort and make reusable information in the design phase. The relation between the Object-Oriented methods and the design patterns is mutually complementary, and they play a role as a valuable design guidance in the development of the Object-Oriented system. This paper show the interaction between OMT which is most well-known in the Object-Oriented Methodology and Facade, Mediator and Observer designed by Gamma. We suggest the clear solution for concrete design knowledge and reusability of them by applying design patterns to Object-Oriented Methodology.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.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.

• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 1995.04a
• /
• 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.

• IE interfaces
• /
• v.16 no.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.

• Proceedings of the IEEK Conference
• /
• 2000.07b
• /
• 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.

• Journal of KIISE:Software and Applications
• /
• v.27 no.5
• /
• pp.488-498
• /
• 2000

Object-oriented methodologies are widely used in the development of huge and complex systems since these methodologies produce the comprehensible and extensible model of systems. In order to apply an object-oriented methodology to a software development, developers should derive a method customized to a specific project from the methodology and, then, construct a development process from the method. Unfortunately, existing object-oriented methodologies lack a systematic facility for the construction of a method and a process. In this paper, we present a customizable object-oriented methodology to support the systematic derivation of a project specific method from the generic methodology. To derive a project specific method from the methodology, we transform the problem of a derivation to a planning problem and apply planning techniques. Our planning technique uses the description of an architecture that captures the structure and characteristics of a software under development as input and constructs an appropriate method with respect to the architecture. The architecture-centered construction facilitates the effective handling for the characteristics of the software since an architecture capture the decisions that must be maintained consistently during the development.

• Journal of Information Technology Applications and Management
• /
• v.12 no.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.