A Graphical Development Method for Multiagent Simulators

Matsumoto, Keinosuke; Maruo, Tomoaki; Murakami, Masatoshi; Mori, Naoki

doi:10.5772/8965

Cited by 5 publications

(2 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…On the other hand, hand coding of all codes of TPS (we call it a conventional method) is carried out as the comparison of quantity of efforts. We introduce a method (Matsumoto et al, 2010) how to quantify the amount of development efforts: It supposes that equal amount of efforts to add one node by the model editor and to describe one line of source code. The number of nodes of UML diagrams that are needed for applying the proposed method and the rate of automatic generation of Cast source codes are computed.…”

Section: Contents Of An Experimentsmentioning

confidence: 99%

A Model-Driven Systems Development Method for Management Information Systems

Matsumoto¹,

Mizuno²,

Mori³

2010

Proceedings of the International Conference on Knowledge Engineering and Ontology Development

View full text Add to dashboard Cite

Keywords:Model-driven development, Model theory approach, UML, Graphic diagrams, Transaction processing system.Abstract: Traditionally, a Management Information System (MIS) has been developed without using formal methods. By the informal methods, the MIS is developed on its lifecycle without having any models. It causes many problems such as lack of the reliability of system design specifications. In order to overcome these problems, a model theory approach was proposed. The approach is based on an idea that a system can be modeled by automata and set theory. However, it is very difficult to generate automata of the system to be developed right from the start. On the other hand, there is a model-driven development method that can flexibly correspond to changes of business logic or implementing technologies. In the model-driven development, a system is modeled using a modeling language such as UML. This paper proposes a new development method for management information systems applying the model-driven development method to a component of the model theory approach. The experiment has shown that a reduced amount of efforts is more than 30% of all the efforts. MODEL THEORY APPROACHThis chapter explains the model theory approach (Takahara & Liu, 2006). According to Takahara et al., automata can describe arbitrary information systems. The model theory approach is proposed as a development method of management information 10 Matsumoto K., Mizuno T. and Mori N..

show abstract

Section: Contents Of An Experimentsmentioning

confidence: 99%

A Model-Driven Systems Development Method for Management Information Systems

Matsumoto¹,

Mizuno²,

Mori³

2010

Proceedings of the International Conference on Knowledge Engineering and Ontology Development

View full text Add to dashboard Cite

show abstract

“…In existing research [11,12] specific to multiagent systems, a method for model-driven development that limits the types of systems under development and is specialized for them has been proposed. In contrast, the proposed method has the advantage of allowing the developer to provide role information for model components and transformation rules without limiting the scope of use of the system under development.…”

Section: Selective Design Of Model Transformation Rulesmentioning

confidence: 99%

Applying Component‐Based Technologies to Model‐Driven Software Development

Mizuno

Matsumoto

Mori

2015

Elect Comm in Japan

Self Cite

View full text Add to dashboard Cite

SUMMARYImproving the reusability of models and increasing automatic code generation efficiency are problems in model-driven development. In order to solve these problems, we apply component-based development technologies that have mainly been developed at the software implementation level to the modeling level. In the proposed approach, functionally relevant model elements are packaged as a component, and the modeling of software is performed by associating them with the model components. The role of a model becomes clear by introducing the concept of a component, and the reusability of model components is improved by externalizing the dependencies between the components. In addition, flexible model transformation rules united with the roles of models can be designed. As a result, the proposed method is able to generate more source code automatically. The validity of the proposed approach is verified through application experiments. C⃝

show abstract