• Proceedings of the Korea Database Society Conference
• /
• 1998.09a
• /
• pp.525-543
• /
• 1998

This paper proposes a conceptual taxonomy of architectures far workflow management systems. The systematic classification work is based on a framework for workflow architectures. The framework, consisting of generic-level, conceptual-level and implementation-level architectures, provides common architectural principles for designing a workflow management system. We define the taxonomy by considering the possibilities for centralization or distribution of data, control, and execution. That is, we take into account three criteria. How are the major components of a workflow model and system, like activities, roles, actors, and workcases, concretized in workflow architecture？ Which of the components is represented as software modules of the workflow architecture？ And how are they configured and operating in the architecture？ The workflow components might be embodied, as active (processes or threads) modules or as passive (data) modules, in the software architecture of a workflow management system. One or combinations of the components might become software modules in the software architecture. Finally, they might be centralized or distributed. The distribution of the components should be broken into three: Vertically, Horizontally and Fully distributed. Through the combination of these aspects, we can conceptually generate about 64 software Architectures for a workflow management system. That is, it should be possible to comprehend and characterize all kinds of software architectures for workflow management systems including the current existing systems as well as future systems. We believe that this taxonomy is a significant contribution because it adds clarity, completeness, and "global perspective" to workflow architectural discussions. The vocabulary suggested here includes workflow levels and aspects, allowing very different architectures to be discussed, compared, and contrasted. Added clarity is obtained because similar architectures from different vendors that used different terminology and techniques can now be seen to be identical at the higher level. Much of the complexity can be removed by thinking of workflow systems. Therefore, it is used to categorize existing workflow architectures and suggest a plethora of new workflow architectures. Finally, the taxonomy can be used for sorting out gems and stones amongst the architectures possibly generated. Thus, it might be a guideline not only for characterizing the existing workflow management systems, but also for solving the long-term and short-term architectural research issues, such as dynamic changes in workflow, transactional workflow, dynamically evolving workflow, large-scale workflow, etc., that have been proposed in the literature.

• The Journal of Information Technology and Database
• /
• v.5 no.1
• /
• pp.97-108
• /
• 1998

This paper proposes a conceptual taxonomy of architectures for workflow management systems. The systematic classification work is based on a framework for workflow architectures. The framework, consisting of generic-level, conceptual-level and implementation-level architectures, provides common architectural principles for designing a workflow management system. We define the taxonomy by considering the possibilities for centralization or distribution of data, control, and execution. That is, we take into account three criteria. How are the major components of a workflow model and system, like activities, roles, actors, and workcases, concretized in workflow architecture. Which of the components is represented as software modules of the workflow architecture\ulcorner And how are they configured and operating in the architecture\ulcorner The workflow components might be embodied, as active (processes or threads) modules or as passive (data) modules, in the software architecture of a workflow management system. One or combinations of the components might become software modules in the software architecture. Finally, they might be centralized or distributed. The distribution of the components should be broken into three: Vertically, Horizontally and Fully distributed. Through the combination of these aspects, we can conceptually generate about 64 software Architectures for a workflow management system. That is, it should be possible to comprehend and characterize all kinds of software architectures for workflow management systems including the current existing systems as well as future systems. We believe that this taxonomy is a significant contribution because it adds clarity, completeness, and global perspective to workflow architectural discussions. The vocabulary suggested here includes workflow levels and aspects, allowing very different architectures to be discussed, compared, and contrasted. Added clarity is obtained because similar architectures from different vendors that used different terminology and techniques can now be seen to be identical at the higher level. Much of the complexity can be removed by thinking of workflow systems. Therefore, it is used to categorize existing workflow architectures and suggest a plethora of new workflow architectures. Finally, the taxonomy can be used for sorting out gems and stones amongst the architectures possibly generated. Thus, it might be a guideline not only for characterizing the existing workflow management systems, but also for solving the long-term and short-term architectural research issues, such as dynamic changes in workflow, transactional workflow, dynamically evolving workflow, large-scale workflow, etc., that have been proposed in the literature.

• Earthquakes and Structures
• /
• v.12 no.2
• /
• pp.223-236
• /
• 2017

Seismic assessment and rehabilitation of Monumental Buildings constitute an important issue in many regions around the world to preserve cultural heritage. On the contrary, many recent earthquakes have demonstrated the high vulnerability of this type of structures. The high nonlinear masonry behaviour requires ad hoc refined finite element numerical models, whose complexity and computational costs are generally unsuitable for practical applications. For these reasons, several authors proposed simplified numerical strategies to be used in engineering practice. However, most of these alternative methods are oversimplified being based on the assumption of in-plane behaviour of masonry walls. Moreover, they cannot be used for modelling the monumental structures for which the interaction between plane and out-plane behaviour governs the structural response. Recently, an innovative discrete-modelling approach for the simulation of both in-plane and out of-plane response of masonry structures was proposed and applied to study several typologies of historic structures. In this paper the latter model is applied with reference to a real case study, and numerically compared with an advanced finite element modelling. The method is applied to the St.Venerio church in Reggiolo (Italy), damaged during the 2012 Emilia-Romagna earthquake and numerically investigated in the literature.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.24 no.4
• /
• pp.408-417
• /
• 2021

This paper describes the quality attributes of an integrated simulation software for weapon systems named Advanced distributed simulation environment(AddSIM). AddSIM is developed as a key enabler for Defense Modeling & Simulation(M&S) systems which simulate battlefields and used for battle experiments, analyses, military exercises, training, etc. AddSIM shall provide a standard simulation framework of the next Defense M&S systems. Therefore AddSIM shall satisfy not only functional but also quality requirements such as availability, modifiability, performance, testability, usability, and others. AddSIM consists of operating softwares of hierarchical components including graphical user interface, simulation engines, and support services(natural environment model, math utility, etc.), and separated weapon system models executable on the operating softwares. The relation between software architectures and their quality attributes are summarized from previous works. And the AddSIM architecture and its achievements in the aspect of quality attributes are reviewed.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.13 no.1
• /
• pp.129-134
• /
• 2013

Previous research is focus on testcase generation automation using message sequence diagram based on metamodel. but that research is not enough for testcase genaeration automation using state diagram based metamodel. so in this paper is adopt Model Driven Architecture (MDA) mechanism for using metamodel and model transformation. and we suggest testcase automation mechanism using state diagram in UML. we will decrease cost of embedded software design and testcase genaration and increase quality of embedded software using metamodel mechanism.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.317-327
• /
• 2007

In this paper, a systematic approach of developing detail 00 designs from Component-and-Connector Architectures (CCAs) is proposed. In this approach, an intermediate model between the architecture model and the detail design model specified with class diagrams or sequence diagrams is introduced to narrow the wide gap between the two abstraction levels. Once a CCA is designed, candidate classes and their relationships are identified per each architectural element. In order to show the efficacy of this approach, we apply it to an industry software development project and verify that quality attributes supported by the CCA are equally maintained by the detail design.

• The Transactions of The Korean Institute of Electrical Engineers
• /
• v.56 no.12
• /
• pp.2247-2250
• /
• 2007

This paper presents an automated API translator for embedded software development based on a model-driven approach. Since MDA(Model Driven Architecture) provides little support for the development of embedded software, we propose a new approach containing its advantages. First, we define #generic APIs# which do not depend on any RTOS#s but provide most of typical RTOS services. We can describe RTOS-related behaviors of target application using these generic APIs in a CIC(Common Intermediate Code). Then, we propose a transformation tool for translating between a CIC using generic APIs and a C-code for specific RTOS. The proposed API translator converts them using XML transformation rule which is defined outside. It indicates that an API translator extends to other RTOS#s by modifying or adding the transformation rule. From the experiment. we validate the proposed method.

• Journal of Korean Institute of Industrial Engineers
• /
• v.39 no.1
• /
• pp.1-9
• /
• 2013

The current manufacturers have generated tremendous amount of digitized product data to efficiently share and exchange it with other stakeholders or various software systems for product development. The digitized product data is a valuable asset for manufacturers, and has a potential to support high level strategic decision makings needed at many stages in product development. However, the lack of studies on extraction of key performance indicators(KPIs) from product data management(PDM) databases has prohibited manufacturers to use the product data to support the decision makings. Therefore this paper examines a possibility of an architecture that supports KPIs for evaluation of product development performances, by applying multidimensional product data model and on-line analytic processing(OLAP) to operational databases of product data management. To validate the architecture, the paper provides a prototype product data management system and OLAP applications that implement the multidimensional product data model and analytic processing.

• Magazine of the Korean Society of Agricultural Engineers
• /
• v.43 no.5
• /
• pp.83-92
• /
• 2001

As a result of the recent water resources crisis, development of water management automation system becomes important. This system should be developed with open architecture in order to flexibly meet the spacial and time change of irrigation water demand. Thereby, water management automation system requires open architecture and suitable software program. This study presents an application of object-oriented methodology for Open Water Management Program(OWMP). Accordingly, OWMP provides a high degree of reliability which allows modification of parameters by change of region or time to be possible. OWMP consists of Data Base Management System(DBMS) and Model System. DBMS makes it possible to analyze data related with planning water schedule and establishing database. Model System calculates reservoir inflow, reservoir effluent and basin water demand. An operator decides the reservoir operation with results of Model System and DBMS. OWMP could be adapted to the planning and decision for saving water.

• Journal of KIISE:Software and Applications
• /
• v.34 no.8
• /
• pp.697-707
• /
• 2007

Since embedded software is very dependent for target hardware architecture, characteristics of the platform must be considered when designing the software. Furthermore, MPSoCs consists of heterogeneous hardware components that are specified in micro level. Thus mapping of embedded software for MPSoCs should be considered the characteristics. In this paper, we provide an approach to automatic mapping PIM (Platform Independent Model) of an embedded software to PSM(Platform Specific Model) for MPSoC(Multi Processor System On Chip) and verify its effectiveness with simulation. In the proposed approach, tasks are derived from an object oriented model based on the UML (Unified Modeling Language). And then the types of the derived tasks are identified. With the identified types and inter relationship between tasks, the tasks are assigned to appropriate heterogeneous hardware components. We expect that the approach improve accuracy of the assigning and concurrency of the deployed software.