THE DESIGN OF EMERGENCY DECISION SUPPORT SYSTEM

FANG YINGHAN School of Economics&Management

Shenyang Ligong University Shenyang, 110159, China

BAO LINA School of Economics&Management

Shenyang Ligong University Shenyang, 110159, China

Abstract—In order to develop a high degree of software reuse, system architecture flexibility, we studied the emergency decision support system which will be quickly to be changed. Based on the domain engineering method, the knowledge of UML modeling, and feature-oriented domain analysis technology, the component development method of emergency decision support system is presented. We have been building a vertical cross-section cutting, component knit, hierarchical design of the component model. Component model can be combined according to user needs to improve the efficiency of such system development and quality.

Keywords-Emergency decision support system, Domain engineering, Object oriented Method

I. INTRODUCTION

Now many software developers are facing the main problem that is to design software modules with different functions. The modules allow users to assemble their own needs more “pragmatic” system [1]. Currently there are a lot about the reusable software development method [2-4]. In order to significantly reduce the software development process of repetitive work and reduce development costs, we use the software industrial production means based on a software architecture approach as the core, component-based software to software reuse as a means [5]. Here we study the combination of the components of emergency decision support system development method by using UML modeling tools and areas of engineering. And we used cross-section cut, components knit, hierarchical design of component-based in accordance with the field of project development steps approach to ensure the flexibility of component replacement. UML modeling tools are used to determine the boundaries of emergency decision support system. The method is more effective to avoid the various coupling and improve the independence of the functional components and external interfaces present a unified, consistent with the current standards for component development.

II. THE EMERGENCY DECISION SUPPORT SYSTEM

AND THE OVERVIEW OF THE FIELD OF

ENGINEERING

Emergency decision support system is to help decision makers to development a series of emergency assist decision after the public emergency.

Its main purpose is to reduce the harm caused by public emergency level, restatement affected people, to prevent the incident or further expansion of the incident or further

expansion of the derivative. Emergency decision support system consists of data, models, reasoning, data mining and human-computer. The domain engineering used to create the basic foundation of basic skills and the process for a group of similar projects or similar system. It covers the establishment of reusable software components in all activities [6], and promotes “the re-use in production, the assembly in use”. There are areas of domain engineering, domain design and implementation of three aspects of the field. It established the significance of emergency decision support system is reflected in that the requirements analysis, design and implementation can reuse the existing areas of engineering products. Therefore, the system can reduce software development costs and improve development efficiency. Based on the proven, standardized reusable components to assemble the system, we improve the reliability and configuration easily of the software system, and promote standardization of the software.

III. COMPONENT DEVELOPMENT METHODOLOGY

Here we used the feature-oriented domain analysis method ( FODA method) [7]. Among them, there are many ways in the field of analysis. For example, [8] proposed RUCS method and [9] proposed OO-SRWM development model based on the model. Based on cross cut by vertical, components knit, hierarchical design of the technical architecture, system components decomposition in two levels: the business component and service component. Business component is the completion of the overall specific business functions. It is more in line with the needs of end-user components. But the business component granularity is a little thick, multiple service components can be “woven” together. Service component is a technology-oriented package unit. And its system architecture is based on hierarchical design. Its components are divided by business operations across the different layers. From the top to the bottom layer, it is interactive layer, determine the layer, coordination layer, processing layer and data source layer in turn. And every level has a certain number of service components. System development process is to start around the decomposed component, developers’ division of labor is also based on the component. From a software architecture perspective, the service component is its “cross-cutting element” and business component is the “vertical cutting unit”.

2012 International Conference on Industrial Control and Electronics Engineering

978-0-7695-4792-3/12 $26.00 © 2012 IEEE

DOI 10.1109/ICICEE.2012.310

1170

IV. EMERGENCY DECISION COMPONENT

DEVELOPMENT PROCESS

Domain analysis includes the identification of areas of the border, identifying information sources, determining what needs to be shared widely in the field of the system, and which are variable. So we can establish the field of model. Based on the analysis, geographical information, disaster assessment, relief strategy is common to the general emergency decision system functions. But different types of disaster on the rescue strategy will be different, these functions can be mapped to the corresponding segments the business component. Finally we can determine which components are reusable. How can we get the system boundary by using UML model? The example shown in Fig. 1.

Fig.1 Emergency Decision Support System Use Cases

We can obtain the domain model fragments as a example of rescue strategy. Shown in Fig.2, it indicated with * is variable characteristics which can be accepted or rejected based on disaster specific application system.

Fig.2 Domain Model fragments Emergency Decision Support

Field analysis is to identify the areas of business components and service components based on the model in the field. In the development process, the layered architecture achieves the division of functions, improve development efficiency and reduce the complexity of the

system and enhance system scalability, reusability, and maintainability. Based on hierarchical component strategy of domain engineering, each layer corresponds to the service component layers in emergency decision support system architecture (shown in Fig.3).

Fig.3 The field of emergency decision support system

Decision-making interactive display components correspond to interaction layer. It is the interaction of people and the window controls the page flow and calls on business services. Through the above methods, decision-making information displayed to the decision makers, policy makers issued through the interface of various rescue strategies.

Judgement decision-making component corresponds to determine the layer. It is used to judge on the decision-making functions, reflect the decision rules, provide data for decision-making, and decide making information, knowledge and the processing capabilities in order to meet the needs of decision-making. So it can ensure that decision-making data and information display is effective and reasonable decisions.

Intergrated management decision-making components correspond to the coordination layer. According to the scale and complexity of practical problems in decision-making process of decomposition, it is decomposed, scheduling and

1171

control. And it is responsible for data, models and knowledge of the three components of organic integration.

Decision-making data processing components correspond to processing layer. This layer contains the basis for decision support and data management systems operating unit. The data which has been collected is stored, converted and absorbed into a variety of information in this layer. Technology which is the more critical is the construction for model base system and ETL processes. Decision-making data mining algorithms for the default rules can refer to [10].

Decision-making data conversion components correspond to the data source layer. It is used to convert the organization of heterogeneous data into a unified data format, and solve the problem of information integration system. Based on Decision support system, the data environment is often physical dispersed, heterogeneous database systems. In such a heterogeneous environment, if there is no uniform, interface good, strong and inclusive technologies to provide data for different systems conversion and processing services, decision support system is difficult to achieve real integration. Therefore heterogeneous environments must solve the problem of date con version. Based on domain model and software architecture software architecture, we can obtain component model, identifying,

developing and organizing the field of reusable components. There are the areas of implementation of the content.

Construction of the emergency decision support system for the field structure, you can establish “cross-section of the

vertical cut, weave structures, hierarchical design” component architecture. Decision-making function of the

various sub-fields in the form of business deploys components. Therefore, a business component completes the operation through the various levels of collaborative

decision-making functions to service members. The various levels of service components are resolved based on the

specific environment and application server components. Fig.4 is the area of decision support component model.

Fig.4 The field of decision support component model

In order to achieve the purpose of reuse, component library can be used on the field of reusable relationship between the evolution of computing and software, refer to [11].

V. SUMMARIES

Based on domain engineering thinking, through the UML modeling tool and feature-oriented modeling, we get the field of reusable components. These components assembled into a new system much faster than using traditional software development methods speed, and software quality can be guaranteed. Implementation of components is transparent to the user. Therefore, the components can adapt to different individual needs. The functional requirements as long as the user need, it can easily meet requirements of the components to assemble into the new system. In practice, how to effectively manage the component library, to implement the framework of component library for software support, and to extract the components is need to in-depth study.

REFERENCES

[1] MEDVIDOVIC N, TAYLOR RN. A Classification and Comparison

Framework for Software Architecture De-scription Languages[J]. IEEE Transactions on Software Engineering, 2000, 26(1),PP: 70-93.

[2] PRIETO-DIAZ R. Status Repot: Software Reusability[J]. IEEE

Software, 1993, 10(3) ,PP: 61-66. [3] TEIXEIRA HV, BRAGA RM, WERNER CM. Model-Based

generation of business component architectures [J]. Proc of the 30th

EUROMICRO Con.f IEEE Computer Society Press, 2004, 5(2) ,PP: 176-183.

[4] HOAG JE, THOMPSON CW. Architecting RFID middle-ware[J].

IEEE Internet Computing, 2006, 10(5) ,PP: 88-92. [5] CAI X, LYU MR, WONG KF, et a1. Component Based Software

Engineering: Technologies, Development Frame-works and Quality

Assurance Schemes[C]. Proceedings of the Seventh Asia-Pacific Software Engineering Conference,2000,PP: 372-379.

[6] CRNKOVIC I. Component-Based software engineering New

challenges in software development[J]. Software Focus, 2001, 2(4) ,PP: 127-33.

[7] KANG KC, COHEN SG, HESS JA, et al. Feature- Oriented domain

analysis (FODA) feasibility study [M]. Technical Report, CMU/SEI-90-TR-21Software Engineering Institute, Carnegie Mellon University,

1990.

1172