Unified Modeling Language Computer Science Essay

Many of the researches in the country of patterning agent based system have described assorted ways of how to plan an agent based with Unified Modeling Language.Agent based systems consists of new techniques and constructs like agent migration, agent messaging, bureau etc. To plan these constructs which are given by agent base system, research workers have proposed different mold and design techniques of patterning an agent based systems.To theoretical account these new constructs few new patterning techniques have been proposed but most of the proposed techniques are the extension to UML diagrams.

In this paper we will discourse different agent base patterning techniques with UML, and besides present their comparing.

Introductionand Background

Unified modeling linguistic communication is widely accepted, as a designing linguistic communication which represents designing of object oriented package systems [ 1 ] . As system package need different mold tools and diagrams to pattern the package system, same is the instance with agent based system, it besides need patterning tools and techniques to pattern the agent base system design [ 2 ] .

The agent research workers are really much interested in planing techniques of patterning the agent based package systems. Agents are little package plans, which helps us to work out assorted jobs. Agent can work independently or with other agent ‘s cooperation to assist accomplish a undertaking.

UML: The incorporate scheduling linguistic communication UML is used to plan the object oriented package systems.UML is used to plan the graphical representation of an object oriented system in the signifier of different diagrams.

Top Writers
Writer Jennie
Verified expert
4.8 (467)
Bella Hamilton
Verified expert
5 (234)
Bella Hamilton
Verified expert
5 (234)
hire verified writer

The chief constituents of UML constitute histrions, database scheme, activities etc. UML is used to pattern simple package systems, client waiter systems, and besides distributed systems. The development of UML is traveling under Object Management Group ( OMG ) .

UML diagrams can be automatically transferred in other diagrams while utilizing the backend linguistic communication as JAVA which the OMG besides supports. Extensibility is the chief characteristic that the UML supports, therefore it is easy to widen with the aid of the characteristics like profiles and stereotyping.

UML is acquiring matured twenty-four hours by twenty-four hours, and the OMG is presenting new releases of UML. The latest is UML 2.3 which was released by the OMG in May 2010 [ 12 ] . This specification includes the superstructure that define the notation of the diagrams, the nucleus meta-model, OCL for specifying regulations, and in conclusion the UML diagram interchange. [ 12 ]

There are many tools available for pulling of UML notations like ArgoUML, Umbrello, Magic draw UML etc.

Extensibility of UML: Agent based systems have used UML as a mold linguistic communication because it is easy to widen and provides most of the design elements for mold of a system. The chief characteristics of UML that are used for extension are as follows.

Profile ( UML ) : UML theoretical accounts can be extended and customized as per the user sphere, with the aid of profiling. The chief purpose of profile is to give the extensibility characteristic to the UML with which a user can widen the UML as per its specific demand for the specific sphere. Profiles can be applied to different categories, attributes etc.

Stereotype ( UML ) : Stereotype is the UML characteristic which is used for the extensibility of UML in the specific user spheres. This allows the coder to widen the UML theoretical accounts therefore utilizing their predefined characteristics and using limitations to suit the object and theoretical accounts with regard to specific spheres. A stereotype is represented by “ & lt ; & lt ; & gt ; & gt ; ” and placed over the name of the component.

Agents and Multi-Agents: Agents are package plans that can work with the user defined stairss or can besides work autonomously to carry through set of work and instructions. Agents can besides work with unreal intelligence and besides can larn from the environment. Agents can larn with the external environment with the aid of detectors and other techniques, this can take to working of the agent autonomously and it besides helps the agents to take the determinations with respects to the environment. Decision devising of the agent helps the agent to work autonomously, and agent can besides predefined the things or can foretell the behaviour of the environment which is coming their manner. Agent has besides the characteristic of mobility where the agent besides can migrate to other bureaus and besides work in the staccato environment. Agent can work with the low bandwidth, and it besides prefers the agent oriented package development over the client waiter base package development.

Agent can besides larn from the environment with the aid of detectors, therefore responding to the environment with the learned information and besides foretelling the environment ‘s behaviour with the informations that it has obtained with the aid of the detectors [ 13 ] . Intelligent agents are those which learn from the environment and execute the operation and take the determinations on behalf of the user needs, this besides include some degree of automaticity while making the undertakings [ 14 ] .

Whereas the multi agent system consists of a set of agents there are working in coordination to accomplish a user defined end or a undertaking [ 5 ] . Multi agent system besides communicates with each other with some standardised communicating linguistic communication like ACL [ 5 ] .

Section 2, define the UML based agent package development techniques. Section 3 outlines the parametric quantities of study ; Section 4 describes the treatment subdivision sing the techniques and parametric quantities while Section 5 describes the decision and future work.

UML based Agent Software Development Techniques

UML 2.0 and Agents: How to Construct Agent-based Systems with new UML Standard

In this paper [ 6 ] , the writers define how agents can be modeled in the UML. The writers focus on all the diagrams available in the UML. The writer picks every diagram one by one get downing from the structural diagram so the behavioural diagrams. The writers foremost explain UML diagram ‘s original mold so defines patterning for agent based package. The writers use illustrations to depict the agent based mold.

Widening UML for Agents

In this paper [ 1 ] , the writers focus on AUML, i.e. , Agent based UML. The writers provide a superimposed attack to pattern behavioural protocols for the agent package. The writers foremost define extension in two UML chief constituents, i.e. , Packages and Templates ; so the writers takes UML interaction diagrams one by one and provides extensions in it to do it feasible for agent package patterning. In the terminal, the writers besides provide extension in the deployment diagram to specify the agent package deployment. The writers use illustrations to explicate every extension.

Agent UML Class Diagrams Revisited

In this paper [ 2 ] , the writer focuses on UML category diagram for agent package patterning. The writer foremost defines the bing UML category diagram so provides extension for the agent package. The writer extremely analysis the agent inactive theoretical account and provides utile compartments in UML category diagram to do it helpful for patterning agent package. In the terminal, the writer besides compares the work with the bing work [ 7 ] and shows how the paper ‘s work is better than the bing.

A Systematic Approach for Mobile Agent Design Based on UML ( Class and Sequence Diagrams )

In this paper [ 3 ] , the writers use category and sequence diagram to pattern Mobile based agent package. The writers propose a new UML profile which is used for agent mold. The writers provide a comprehensive Book Search instance survey to explicate their technique. In the terminal, the writers besides evaluate their technique.

Agent UML: Formalism for Stipulating Multiagent Software Systems

In this paper [ 7 ] , the writers focus on both inactive and behavioural facets of agent patterning with UML. The writers propose some extension in category diagram harmonizing to the demands of the agent. The writers so relate the drawn-out category diagram with province and sequence diagram for the actions implementation sing agents. The writers provide a brief overview of the technique with the aid of a instance survey. The writers besides propose some extensions sing different concepts of sequence diagram and province machine. In the terminal, the writers besides evaluate their work.

Towards an extension of UML 2.0 to pattern nomadic agent-based Systems

In the article [ 14 ] , the writer extended UML theoretical account and proposed extensions to pattern nomadic agent based systems. Harmonizing to the writer the nomadic systems have some of import constructs that should besides be incorporated in agent based UML theoretical accounts. These constructs include migration, cloning and the locations. Different UML theoretical accounts are used to represents these constructs through stereotyping. The UML theoretical account that represents these constructs are: usage instance diagram, sequence diagram, category diagram, province chart diagram, activity diagram and deployment diagram. Mobile electronic stock exchange is used as a instance survey to pattern migration, cloning and locations on the above mentioned UML diagrams.

Towards Development of Agent Class Diagrams as an Integrative Approach for AUML Extension

In the article [ 15 ] , the writers provide extension to pattern multi agent system semantics by utilizing agent category diagram. The agent category diagram usage FIPA based AUML category diagram and supply extensions in category diagram that captures the semantics of agents and multi agents systems. Agent category diagrams abstract sentence structure was presented and their challenges and future research were besides discussed.

A UML based attack for patterning and implementing multi agent system

In the paper [ 16 ] , the writers present an agent-oriented mold linguistic communication known as MAS-ML ( Multi Agent System Modeling Language ) and turn outing its function execution in JAVA. The Meta theoretical account based extension been proposed that extends category and sequence diagram utilizing stereotypes. The extension atMeta theoretical account degree generalizes the architecture of multi agent systems and helps to bring forth JAVA codification from MAS-ML theoretical accounts specifically category and sequence diagram, Both the diagrams were specifically choose to stand for both the inactive and behavioural facets of the systems.

Exploiting UML in the design of Multi Agent Systems

In the paper [ 17 ] , the writers present a multi agent system on patterning agent through category and join forcesing diagrams as protocol and function diagrams. The diagrams were chosen to stand for both the inactive and behavioural facets of the agent. Ontological architecture of both the theoretical accounts was created and at Meta degree stereotypes were applied.

UML for Agent-Oriented Software Development: The Tropas Proposal

In the paper [ 18 ] , the writers present a multi agent system patterning methodological analysis called Tropas. The Tropas support four stages of package development, early and late demands, architectural and elaborate design utilizing i* model. The constructs used to pattern all the four stages are histrions and their functions. i* model theoretical account the system utilizing UML stereotype which subsequently on transferred to category diagram, sequence diagram and province diagram.

Analysis Parameters

Type of Software Agent Represented

This parametric quantity focuses on which package agent type is used. The possible values for this parametric quantity are Social, Autonomy, Re-active, Pro-active, and Internal. If the technique focuses on all the diagrams so the value would be All.

Application of Agent

This parametric quantity tells about the type of application for which agent is modeled. The possible values for this parametric quantity are Agent, Mobile-agent, and Multi-agent.

UML Model ( s ) Used

This parametric quantity provides the information about which UML diagrams are used in technique. The possible values for this parametric quantity are Class, Object, Composite Structure, Component, Deployment, Use instance, and Interaction ( Interaction Overview, Sequence, Communication, State Machine, and Activity ) . If the technique focuses on all the diagrams so the value would be All. This parametric quantity may hold more than one values assigned.

Agent Application Coverage

This parametric quantity focuses on the coverage of agent application. The possible values for this parametric quantity are Inactive and Behavioral.

UML Version

This parametric quantity tells about the version of UML considered in the mold of agent. The possible values for this parametric quantity are the available UML versions, i.e. , 1.0, 1.1, 1.2, 2.0, 2.2.

Extension/Profile

This parametric quantity tells about whether the technique provides some extension in the bing UML diagram for agent mold or proposes new profile for the agent patterning utilizing UML. The possible values for this parametric quantity are Extension and Profile.

Automated

This parametric quantity tells whether the technique is automatable or non. The term automatable means that the paper already provides information about it mechanization. The possible values for this parametric quantity are Yes and No.

Case Study

This parametric quantity tells whether the paper presents any instance survey to depict the presented technique or non. The possible values for this parametric quantity are Yes and No.

Software Life Cycle Phase

This parametric quantity tells about which package life rhythm stage is addressed which patterning agent utilizing UML. Some of the technique focuses on design stage while some ever provides the execution inside informations. The possible values for this parametric quantity are Inception, Design, Implementation, Deployment, Testing, and Maintenance. The parametric quantity may hold more than one value assigned.

Discussion

This paper presents the comparative analysis of the agent based package patterning techniques. In mention 1,3,6,14,15,17,18 the type of package agent representation is non mentioned while in mention 2 type of agent represented is Internal, Proactive, Reactive, in 7 it is proactive and reactive, in 16 it is merely proactive. In 6, 1, 7,15,16,18 application of agent is multi-agent, while in 2 it is nomadic agent and in 14 both multi-agent and nomadic agents. 6,14 techniques defines all UML diagrams, while the other techniques define little set of diagrams like interaction, deployment, category, sequence etc. Most of the techniques like 6, 3, and 7,16,17,18define the agent coverage as both inactive and behavioural. Most of the techniques are based on UML version 2.0 and are largely extensions to it based on stereotypes and profiles. All techniques except 14 define some instance survey. Techniques 2,16 are automated sing the agent based UML mold.

Decision and Future Work

Agent are package plans, which are designated to make a specific piece of work, likewise multi-agents excessively are package plans that composed of multiple interacting intelligent agent. Agents have some of import features which includes liberty, local positions, decentalisation etc. In order to pattern agents these features need to be modeled exactly and meaningfully both in term of abstract sentence structure and semantics. UML is a modeling linguistic communication, which in its current signifier does n’t able to pattern agents meaningfully. Though the extension in current UML has beenan on-going research and rather active these yearss as shown in Table 1, but still its deficiencies in completeness and demand to be investigated more.

The countries that can be genuinely revisited includes: agent application coverage, extensions at meta-level utilizing stereotypes and mechanization.

Ref.No

Type of Software Agent Represented

Application of Agent

UML Model ( s ) Used

Agent Application Coverage

UML Version

Extension/Profile

Automated

Case Study

Software Life Cycle Phase

[ 6 ]

Not Mentioned

Multi-agent

All diagrams

Static & A ; Behavioral

2.0

Extension

No

Yes

Design & A ; Implementation

[ 1 ]

Not Mentioned

Multi-agent

Interaction, Deployment

Behavioral

2.0

Extension

No

Yes

Design & A ; Deployment

[ 2 ]

Internal, Pro-active, Re-active

Agent

Class

Inactive

1.5

Extension

Yes

Yes

Design & A ; Implementation

[ 3 ]

Not Mentioned

Mobile-agent

Class, Sequence

Static & A ; Behavioral

2.0

Profile

No

Yes

Design

[ 7 ]

Pro-active, Re-active

Multi-agent

Class, State Machine, Sequence

Static & A ; Behavioral

1.3

Extension

No

Yes

Design

[ 14 ]

Not Mentioned

Multi Agent Mobile

All diagrams

Inactive

2.0

Extension

No

Yes

Design

[ 15 ]

Not Mentioned

Multi-agent

Class diagram

inactive

Not UML based

Extension in AUML

No

No

Design

[ 16 ]

Pro active

Multi-agent

Sequence and category diagram

Static & A ; Behavioral

2.0

Extension through stereotypes

Yes

Yes

Design

[ 17 ]

NotA Mentioned

Multi-agent

Sequence and category diagram

Static & A ; Behavioral

2.0

Extension through stereotypes

No

Yes

Design

[ 18 ]

Not Mentioned

Multi-agent

Sequence, category and province diagram

Static & A ; Behavioral

2.0

Extension through stereotypes through i* model

No

Yes

Requirement and Design

Table 1: Comparative Study Summary on Modeling agent Based Systems with UML

Cite this page

Unified Modeling Language Computer Science Essay. (2020, Jun 02). Retrieved from http://studymoose.com/unified-modeling-language-computer-science-new-essay

Are You on a Short Deadline? Let a Professional Expert Help You
HELP ME WITH WRITING
Let’s chat?  We're online 24/7