Agent-Oriented Software Development: A Tropos Methodology Analysis

Desklib offers solved assignments and past papers to help students succeed.

AGENT-ORIENTED SOFTWARE
DEVELOPMENT
MITS5002
SOFTWARE ENGINEERING METHODOLOGY
ASSIGNMENT 1 AND 2

• An agent can be said as an organisation, a person or kind of software.
• An agent is having the emotions, beliefs, aims and objectives along with the positive
intentions.
• Agents can also be social, flexible and autonomous.
• The human and organisational agents cannot be able to prescribed as they can only be
described partially.
• On the other hand, the software agents can be defined as to be specific during the
implementation.
WHAT IS AN AGENT

AGENT-ORIENTED SOFTWARE
DEVELOPMENT
• The upcoming generation is going of
software engineering have to support the
dynamic and open structures where the
elements can achieve the tasks in a
diversity of operating environment.
• In agent-oriented software development
this is to consider the several areas
which are P2P computing, e-Business
and web services.
• Learning, communication, planning,
exception handling and the negotiation
are becoming the important features for
the components of the software.

THE TROPOS METHODOLOGY
• Tropos is defined as an
agent oriented
methodology which covers
the entire process of
software development.
• Tropos is mainly based on
two key ideas.
• The Tropos methodology
covers about five phases
which are named as early
requirement analysis,
architectural design, late
requirement analysis,
detailed design and
implementation.
• This is the concept which is
offered by i* which is
mainly used to model both

THE FIVE PHASES OF THE TROPOS
METHODOLOGY
• Early Requirement
Analysis
• Late Requirement
analysis
• Architectural design
• Detailed design, and
• Implementation

• This phase consist of
identifying and analysing the
intentions of the stakeholders
and them.
• In this phase we must define
the goal, actors and the goals
diagram.
• This phase mainly analyse and
understand the problem or
issue by studying the settings
of an existing organisation.
EARLY REQUIREMENT ANALYSIS

LATE REQUIREMENT ANALYSIS
• This phase mainly focuses
on the system to be with in
its own operating
environment.
• The system must represent
with the goal diagram of the
actor along with its
dependencies with the other
actors of the firm.
• The system must be
describe within its own
qualities and functions.

ARCHITECTURAL DESIGN
• This phase defines the global
architecture of the system
along with its sub systems.
• The sub systems in this are
interconnected through the
control flows and data which
are said as dependencies.
• The architectural design is
expressed in the three steps
which are define below.

DETAILED DESIGN
• This phase is describing about
the detailed design of the
software system.
• This deals with the requirement
of the agents at the micr0 level.
• In this the capability diagrams
models a ability along with a
UML activity diagrams.
• In this design each of the
components of the architecture
are defined in more enhanced
way such as in case of input,
output, control and in other
useful information.

IMPLEMENTATION
• In this phase the
implementation of the system
is define.
• In this phase the real or
original implementation is to
be carried out consistently
with the detailed design of the
system.
• In this the implementation is
done using the Jack.
• The BDI platform has been
selected for the
implementation of the system
and this is defined as Jack
intelligent agents.

CONCLUSION
• From the above presentation report, this has
been stated that the above presentation has
defined the concept of agent oriented
software development along with the concept
of agents. The presentation has briefly define
about the metho0dlogy used in the report
which is named as Tropos, which has been
categorised in five phases , and these are
defined a d described above in the
presentation.

REFERENCES
• [1] Sterling, L., Lopez-Lorca, A. and Kissoon-Curumsing, M., 2018.
Adding Emotions to Models in a Viewpoint Modelling Framework From
Agent-Oriented Software Engineering: A Case Study With Emergency
Alarms. In Innovative Methods, User-Friendly Tools, Coding, and Design
Approaches in People-Oriented Programming (pp. 324-367). IGI Global.
• [2] Gomez-Sanz, J.J. and Fuentes-Fernández, R., 2015. Understanding
agent-oriented software engineering methodologies. The Knowledge
Engineering Review, 30(4), pp.375-393.
• [3] Shehory, O. and Sturm, A., 2016. AGENT-ORIENTED SOFTWARE
ENGINEERING. SPRINGER-VERLAG BERLIN AN.
• [4] Mouratidis, H., Argyropoulos, N. and Shei, S., 2016. Security
requirements engineering for cloud computing: The secure tropos
approach. In Domain-specific conceptual modeling (pp. 357-380).
Springer, Cham.