• Proceedings of the Korea Society of Information Technology Applications Conference
• /
• 2002.11a
• /
• pp.163-170
• /
• 2002

해체 데이터베이스 구조 설계를 위하여 입력과 출력 항목 및 평가 대상 항목을 선정하였다. 해체 활동으로부터 발생되는 수많은 해체 정보들을 코드화하였다. 데이터베이스 구축에 사용되는 설계 도구들을 검토한 후 20 여가지 설계 도구들 중 범용적으로 사용되고 있는 모델링 도구를 이용하여 사용자 요구사항으로부터 도출된 주요 해체 정보들간의 관계를 ERD(Entity Relationship Diagram)를 사용하여 규명하였으며, DFD(Data Flow Diagram)를 이용하여 해체 DB 시스템의 프로세스 흐름을 파악하였다. 해체 데이터베이스 구현의 원할한 진행을 위해 프로토타입을 설계하였다.

• Proceedings of the Korea Society for Industrial Systems Conference
• /
• 2002.11a
• /
• pp.163-170
• /
• 2002

해체 데이터베이스 구조 설계를 위하여 입력과 출력 항목 및 평가 대상 항목을 선정하였다. 해체 활동으로부터 발생되는 수많은 해체 정보들을 코드화하였다. 데이터베이스 구축에 사용되는 설계 도구들을 검토한 후 20여가지 설계 도구들 중 범용적으로 사용되고 있는 모델링 도구를 이용하여 사용자 요구사항으로부터 도출된 주요 해체 정보들간의 관계를 ERD(Entity Relationship Diagram)를 사용하여 규명하였으며, DFD(Data Flow Diagram)를 이용하여 해체 DB 시스템의 프로세스 흐름을 파악하였다 해체 데이터베이스 구현의 원할 한 진행을 위해 프로토타입을 설계하였다.

• Proceedings of the Korea Society of Information Technology Applications Conference
• /
• 2002.06a
• /
• pp.85-86
• /
• 2002

• Journal of Information Technology Applications and Management
• /
• v.17 no.3
• /
• pp.1-24
• /
• 2010

Most of enterprises depend on a data modeler during developing their management information systems. In formulating business requirements for information systems, they widely and naturally use the interview method between a data modeler and a field worker. But, the discrepancy between both parties would certainly cause information loss and distortion that lead to let the systems not faithful to real business works. To improve or avoid modeler-dependant data modeling process, many automated data design CASE tools have been introduced. However, since most of traditional CASE tools just support drawing works for conceptual data design, a data modeler could not generate an ERD faithful to real business works and a user could not use them without any knowledge on database. Although some CASE tools supported conceptual data design, they still required too much preliminary database knowledge for a user. Against these traditional CASE tools, we proposed a Requirement-Oriented Entity Relationship Model for automated data design tool, called ROERM. Based on Non-Stop Methodology, ROERM adopts inner systematic modules for complete and sound ERD that is faithful to real field works, where modules are composed of interaction modules with a user, rules of schema operations and sentence translations. In addition to structure design of ROERM, we also devise detailed algorithms and perform an experiment for a case study.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.21 no.3
• /
• pp.175-195
• /
• 1996

In conventional analysis methods, data and process are loosely coupled for building information systems. Several object oriented approaches have been proposed to integrate data and process. However, object oriented analysis requires a radical paradigm and thus system analysts find difficulties in generating object models direcctly from end users. To alleviate these difficulties, this paper proposes a methodology for deriving an object model by using structured analysis results. Objects are obtianed primarily from entities in Entity-Relationship Diagram. Methods are obtained through the analysis of the relationship between processes and data stores in Data Flow Diagram Methods are assigned to the objects by using object/process matrices. A real-life case is illustrated to demonstrate the usefulness of the methodology.

• The Journal of the Korea Contents Association
• /
• v.9 no.5
• /
• pp.61-75
• /
• 2009

Generally, the development of the database application includes the requirement analysis phase of creating ERD (Entity Relationship Diagram) and process models, coding, and testing. From the above phases, the analysis phase is not most formalized. It is usually hard task because (1) customers don't know the details of the desired system; (2) developers can't with ease understand the business logic of the customers; (3) the outcomes of the analysis, which are ERD and process models, are not easy to understand to the customers. This paper propose that the executional forms, which are better to understand the systems, should be presented to the customers instead of the ERD. These forms should accept the data input so that customers can review the various aspects of the outcome models. The developers should be able to instantly implement the business logic and also should be able to visually demonstrate the logic in order to get the details of it. For this goal, the customer supplied business logic should be able to be implemented by the references between forms, actions, constraints from the perspective of the data flow. The customers try to execute the forms implementing the business logic and review their supplied logic find new necessary business logic of their own. Iterating these processes for the requirement analysis would result in the success of the analysis which is sufficiently detailed without conflicts.

• IE interfaces
• /
• v.15 no.4
• /
• pp.391-400
• /
• 2002

The internet call systems using CTI(Computer Telephony Integration) functions are designed with system configuration, DFD(Data Flow Diagram) and ERD(Entity Relationship Diagram) in this paper. The internet call systems are constructed to cooperate with conventional CTI call center. The internet phone calls occurred from the web browser of customer can be connected throughout VoIP gateway and PBX to many counselors. The internet call systems can provide various services; customer information service, escorted browsing service, text chatting service, text sharing service, conference service, and statistical analysis service.

• IE interfaces
• /
• v.18 no.4
• /
• pp.465-476
• /
• 2005

Evolutionary operation is a useful tool for improving full-scale manufacturing process by systematically changing the levels of the process variables without jeopardizing the product. This paper presents a system design for the evolutionary operation software called 'evolutionary optimizer'. Evolutionary optimizer consists of four modules: factorial design, many variables, mixture, and mean/dispersion. Context diagram, data flow diagram and entity-relationship modelling are used to systematically design the evolutionary optimizer system.

• Journal of Information Technology Application
• /
• v.3 no.2
• /
• pp.67-82
• /
• 2001

The ILOF project addresses the needs of logistics industrial organizations to reduce information processing time, improve added and residual value of information and reduce processing and transportation costs. It deals with the information supply chain information systems shared by vertical partner as important entity, whose performance and optimization very significantly affects the efficiency and performance of logistics industries. This paper deals with logistics information exchange systems based on supply chain management, focusing on sharing database and processes between partners such as shipper, logistics broker, transportation company, shipping company etc., for smoothing the information flow, enhancing consumer service and reducing communication fee and labour costs. The significance of contribution of this research is the provision of a model for logistics information exchange including entity relationship diagram, data flow diagram and functions which is able to facilitate the formulation of a customer driven supply chain information network, there by enhancing the competitive edge of companies in logistics industries on local and global basis.

• Journal of Korean Institute of Industrial Engineers
• /
• v.42 no.3
• /
• pp.241-248
• /
• 2016

Plant life cycle consists of design, construction, certification, operation, and maintenance phases, and various and enormous plant life cycle data is involved in each phase. Plant life cycle data should be linked with each other based on its proper relationships, so that plant operators can access necessary plant data during their regular operations and maintenance works. Currently, the relationships of plant life cycle data may not be defined explicitly, or they are scattered over several plant information systems. This paper proposes high level design of a plant life cycle data management system based on pre-defined plant life cycle database design. ISO-15926 standard is adapted for the database design. User-interface designs of the plant life cycle data management system are explained based on analysis of plant owners' requirements. A conceptual design of the database is also described with the entity-relationship diagram.