Modeling Multi-Agent Systems using UML

DataGramaZero - Revista de Ciência da Informação, 2009

Este artigo destaca o uso da Unified Modeling Language, UML na especificação de modelos baseados em ontologias na representação de domínios de conhecimento, enfatizando a importância da semântica e do tratamento da linguagem padronizada para que o conhecimento do domínio possa ser organizado e compartilhado. Finalmente, este artigo tem como objetivo estabelecer uma conexão entre as temáticas: modelagem orientada a objetos e ontologias.

2000

The Uni ed Modeling Language, UML, is a high-pro le approach to modelling systems. The semantics of the models are expressed in metamodels. These are evolving under the direction of the Object Management Group (OMG). As the UML becomes more mature and is taken up by a wider range of practitioners, the need for focused variants of the approach, targeted to speci c types of system or development phases has been recognised by OMG.

In some sciences, especially in the study of the so-called complex systems, computer programs play an important role as scientific equipment. In the case of computer simulations the programs under use can be seen as experimental devices built in software. The Multi-Agent Modelling Language (MAML) is one of the efforts to ease the development of agent-based simulations for scientist holding their expertise in other fields than computer science.

Frontiers of Information Technology & Electronic Engineering, 2016

The unified modeling language (UML) is one of the most commonly used modeling languages in the software industry. It simplifies the complex process of design by providing a set of graphical notations, which helps express the objectoriented analysis and design of software projects. Although UML is applicable to different types of systems, domains, methods, and processes, it cannot express certain problem domain needs. Therefore, many extensions to UML have been proposed. In this paper, we propose a framework for integrating the UML extensions and then use the framework to propose an integrated unified modeling language-graphical (iUML-g) form. iUML-g integrates the existing UML extensions into one integrated form. This includes an integrated diagram for UML class, sequence, and use case diagrams. The proposed approach is evaluated using a case study. The proposed iUML-g is capable of modeling systems that use different domains.

IBM Systems Journal, 2000

The Unified Modeling Languaget (UMLt) industry standard has recently undergone a major upgrade, resulting in a revision called UML 2. The primary motivation for this revision was to make UML better suited to model-driven developmente (MDDe), an approach to software development in which software models play a vital role. This requires a modeling language that is not only highly expressive but also capable of specifying models that are precise and unambiguous. In this overview article, we describe the key developments in UML 2 and the rationale behind them, and we explain how they help meet the needs of MDD. These new capabilities can be grouped into two distinct categories: (1) internal and architectural changes required to support MDD and (2) new modeling features. This paper is a revised version of a Web article, ''Unified Modeling Language Version 2.0,'' which was published on March 21, 2005, by developerWorkst, IBM Corporation.

2011

A solid architectural vision is a key discriminator in the success or failure of a software project. This paper discusses how to describe architecture through a set of design viewpoints and how to express these views in the UML. In this paper we mainly focused on the standardization of UML for software development process with the discussion of benefits of UML. Object-oriented analysis (OOA) is concerned with developing software engineering requirements and specifications that expressed as a system's object model (which is composed of a population of interacting objects), as opposed to the traditional data or functional views of systems. The goal of this paper is to combine the respective strengths of powerful, specialized (architectural-based) modeling approach (UML) with a widely used general (design-based) approach. Also some weaknesses have been discussed so that existing modeling can be optimized for better architecture development.

2005

The diversity of multi-agent systems creates the need for tools and methodologies to achieve their designs. UML has been proposed as a new approach for agent modeling, yet it does not support the concept of agents. This paper describes a UML profile that we defined for Multi-Agent Systems MAS. In order to support the definition of this profile the ArgoUML

2006

In this paper a design process for agent oriented software design is presented that uses the Unified Modeling Language. It starts with use-case diagrams in which at a certain level of abstraction some use-case are identified with agents (agents identification phase). Then the structure of the agents is designed in a class diagram. Each class in this diagram contains all the methods that the following description of the agents' behaviors phase proves necessary. These two phases are iterated to introduce all the behaviors. The whole process can be repeated until all the requirements have been implemented.

Way back in the late twentieth century-1997 to be exact-the Object Management Group (OMG) released the Unified Modeling Language (UML). One of the purposes of UML was to provide the development community with a stable and common design language that could be used to develop and build computer applications. UML brought forth a unified standard modeling notation that IT professionals had been wanting for years. Using UML, IT professionals could now read and disseminate system structure and design plans-just as construction workers have been doing for years with blueprints of buildings. It is now the twenty-first century-2003 to be precise-and UML has gained traction in our profession. On 75 percent of the resumes I see, there is a bullet point claiming knowledge of UML. However, after speaking with a majority of these job candidates, it becomes clear that they do not truly know UML. Typically, they are either using it as a buzz word, or they have had a sliver of exposure to UML. This lack of understanding inspired me to write this quick introduction to UML 1.4. When you are finished reading you will not have enough knowledge to put UML on your resume, but you will have a starting point for digging more deeply into the language.

2008