• Journal of Korea Game Society
• /
• v.6 no.4
• /
• pp.47-53
• /
• 2006

In the game development differently with general software development, game planers, programers, and graphic designers, the specialists of the various fields, accomplished one team and they are advanced all to their goal. So it is very difficult for the development participants to communicate each other accurately and efficiently. For successful game development, all development participants should understand accurately the contents of the game design document. Specially the game mechanics as a major part of game design, requires the no-error contents, the no-error expression, and the no-error readings to all development participants because it contains almost game-play logic. It becomes more difficult for the development participants to understand accurately the game mechanics which becomes larger and complicated as the size of game development becomes larger. And configuration management of the game mechanics becomes more complicated and inefficient. In this paper, we propose a new representation method of game mechanics using UML notations for solving this problem. The proposed method satisfies the visual expression and the logical expression simultaneous for the requirements of the game mechanics because of UML notations. And the proposed method could be an efficient management of configuration because the management is based on the UML model management. The proposed representation of game mechanics of "Capture The Dude" game, shows good visual expression and good logical expression.

• Journal of Korea Multimedia Society
• /
• v.3 no.3
• /
• pp.290-297
• /
• 2000

For verifying consistency and completeness of some UML diagrams as a representative of the graphic notations for object-oriented designs, we first give an analysis of some UML diagrams and apply simple ER model to the UML diagrams. Next, we formally define this graphical representation as a set of sets and a set of functions. According to the semantics of these functions, we derive a set of rules to assure the consistency and completeness of this graphical representation. These rules will be included with a CASE tool, which possesses both the diagramming facility and the consistency and completeness checking capability.

• The Journal of the Korea Contents Association
• /
• v.15 no.8
• /
• pp.1-8
• /
• 2015

Arduino is an open-source prototyping platform. It has been used in diverse areas including media-art, simulation and interaction devices. The Arduino application does not provide an effective form of software design specification, since it is basically developed in C Programming language. In this paper, we propose a design method for the Arduino applications using the extension mechanism of the UML(Unified Modeling Language). The proposed method is enable to specify the main function of Arduino applications like digital I/O and analog I/O in UML notations.

• The Transactions of The Korean Institute of Electrical Engineers
• /
• v.58 no.12
• /
• pp.2492-2497
• /
• 2009

In this paper, a user application based on ZigBee is developed using UML. Conventional development procedure for an application using ZigBee stack requires a tremendous effort, since a developer has to study programming interfaces and analyze sample code to modify and add necessary code. In this study, a sample user application based on ZigBee is modeled using UML and embedded software code is generated using an automatic code generation tool. If the application development method using UML proposed in this paper is used, it is possible for a user to easily develop an application using powerful notations of UML diagrams without paying attention to the details of complex programming code.

• Journal of Advanced Navigation Technology
• /
• v.15 no.6
• /
• pp.1180-1186
• /
• 2011

For verifying consistency and completeness of some UML diagrams as a representative of a graphical notations for object-oriented designs, I first give an analysis of some UML diagrams and apply some verifying rules to the UML diagrams. In this paper, I design effective verifying system which possesses both diagramming facility and the consistency and completeness checking capability. The verifying system uses a set of frames to represent internal diagramming information.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.11
• /
• pp.2965-2980
• /
• 1999

There are several models and the corresponding diagrams to express software system in many kinds of viewpoints, but these are supposed to be integrated and implemented into only one system. Therefore, the software modelers should have the models ensuring the consistency between information in software development life cycle. To support the robust models for modelers using OO modeling methods, i.e. UML, and CASE tools, the meta models of the software architecture and the consistency rules between the models are suggested in this thesis. Finally, the rules are implemented in the OO CASE tool, DEBUTO(Design By UML Tool). It supports UML1.1 notations and has visual modeling editors that enable users make their own software model.

• Asia pacific journal of information systems
• /
• v.14 no.1
• /
• pp.79-100
• /
• 2004

As a part of ebXML(Electronic Business using eXtensible Markup Language) framework, BPSS(Business Process Specification Schema) has been provided to support the direct specification of the set of elements required to configure a runtime system in order to execute a set of ebXML business transactions. The BPS,' is available in two stand-alone representations, a UML version and an XML version. Due to the limitations of UML notations and XML syntax, however, current ebXML BPSS specification fails to specify formal semantic constraints completely. In this study, we propose a constraint classification scheme for the BPSS specification and describe how to formally represent those semantic constraints using OCL(Object Constraint Language). As a way to validate p Business Process Specification(BPS) with the formal semantic constraints, we suggest a rule-based approach to represent the formal constraints and demonstrate its detailed mechanism for applying the rule-based constraints to the BPS with a prototype implementation.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.13 no.9
• /
• pp.4234-4243
• /
• 2012

USN(Ubiquitous Sensor Network) application S/W has a complex characteristic that it controls various kind of sensor nodes organically based on the core modules of various target operating systems. Currently, various researches for efficient S/W development are being performed in USN application field. In order to increase S/W productivity, the method such as product line development approach to specify core common functions of applications according to the domain and develop applications with the core common functions and variant functions selected according to the workflow of applications is efficient. To apply this approach to the USN domain, characteristics of USN application S/W and product line development should be specified with one consistent view. However, it is difficult to efficiently specify the characteristics using general UML notations. In order to solve the problem, this paper proposes a method to effectively specify the characteristics of USN applications and product line development using UML profile which is the extension mechanism of UML. The proposed UML profile for produce line based USN application development enables developers to effectively develop product line based USN applications using existing UML and UML support tools without new design methods or tools which are specified for USN or product line development.

• International Journal of Computer Science & Network Security
• /
• v.21 no.4
• /
• pp.103-114
• /
• 2021

A conceptual model can be used to manage complexity in both the design and implementation phases of the system development life cycle. Such a model requires a firm grasp of the abstract principles on which a system is based, as well as an understanding of the high-level nature of the representation of entities and processes. In this context, models can have distinct architectural characteristics. This paper discusses model multiplicity (e.g., unified modeling language [UML]), model singularity (e.g., object-process methodology [OPM], thinging machine [TM]), and a heterogeneous model that involves multiplicity and singularity. The basic idea of model multiplicity is that it is not possible to present all views in a single representation, so a number of models are used, with each model representing a different view. The model singularity approach uses only a single unified model that assimilates its subsystems into one system. This paper is concerned with current approaches, especially in software engineering texts, where multimodal UML is introduced as the general-purpose modeling language (i.e., UML is modeling). In such a situation, we suggest raising the issue of multiplicity versus singularity in modeling. This would foster a basic appreciation of the UML advantages and difficulties that may be faced during modeling, especially in the educational setting. Furthermore, we advocate the claim that a multiplicity of views does not necessitate a multiplicity of models. The model singularity approach can represent multiple views (static, behavior) without resorting to a collection of multiple models with various notations. We present an example of such a model where the static representation is developed first. Then, the dynamic view and behavioral representations are built by incorporating a decomposition strategy interleaved with the notion of time.

• Proceedings of the CALSEC Conference
• /
• 2004.02a
• /
• pp.318-326
• /
• 2004

The ebXML (Electronic Business using eXtensible Markup Language) Specification Schema is to provide nominal set of specification elements necessary to specify a collaboration between business partners based on XML. As a part of ebXML Specification Schema, BPSS (Business Process Specification Schema) has been provided to support the direct specification of the set of elements required to configure a runtime system in order to execute a set of ebXML business transactions. The BPSS is available in two stand-alone representations, a UML version and an XML version. Due to the limitations of UML notations and XML syntax, however, current ebXML BPSS specification is insufficient to specify formal semantic constraints of modeling elements completely. In this study, we propose a classification schema for the BPSS semantic constraints and describe how to represent those semantic constraints formally using OCL (Object Constraint Language). As a way to verify a Business Process Specification (BPS) with the formal semantic constraint modeling, we suggest a rule-based approach to represent the formal constraints and to use the rule-based constraints specification to verify BPSs in a CLIPS prototype implementation.