Double Talk

1

• Double Talk
• Object Oriented vs. Agent Oriented
• Methodologies for Analysis and Design
• Anna Perini (ITC-IRST)
• Adolfo Villafiorita (ITC-IRST)

OO AO
1
2
In This Talk

• OO vs. AO is really
• OO Methodologies vs.
• AO Methodologies
• OO Methodologies is really
• AO Methodologies is really

UML
Tropos
OO AO
2
3
Outline of the Talk

• UML
• Overview
• UML in the Process
• (Example)
• Tropos
• Overview
• Tropos in the Process
• (Example)
• Discussion

OO AO
3
4
Why UML

• Visual (Simple and Intuitive)
• Notations for the whole development cycle
• Supported by several tools (Rose, , Tau)
• Widely used ( and trendy)
• Mature (Close to become a ISO standard (?))
• Scalable and Flexible ( often a necessity)

5
History of UML

• Tres Amigos Booch, Rumbaugh, Jacobson
• OMG not for profit consortium, 800 members, that
  produces and maintains standards (e.g. Corba)

6
UML Diagrams

• Static
• Use case diagram
• Class diagram
• Component diagram
• Deployment diagram
• Dynamic
• Interaction diagrams
• Sequence diagram
• Collaboration diagram
• State diagram
• Activity diagram

7
Process Phases

• Business Modeling
• Requirements
• Analysis Design
• Implementation
• Testing
• Deployment

• Business Modelling
• To understand the structure and the dynamics of
  the organization in which a system is to be
  deployed (the target organization).
• To understand current problems in the target
  organization and identify improvement potentials.
• To ensure that customers, end users, and
  developers have a common understanding of the
  target organization.
• To derive the system requirements needed to
  support the target organization.

• Requirements
• To establish and maintain agreement with the
  customers and other stakeholders on what the
  system should do.
• To provide system developers with a better
  understanding of the system requirements.
• To define the boundaries of the system.
• To provide a basis for planning the technical
  contents of iterations.
• To provide a basis for estimating cost and time
  to develop the system.
• To define a user-interface for the system,
  focusing on the needs and goals of the users.

• Analysis Design
• To transform the requirements into a design of
  the system to-be.
• To evolve a robust architecture for the system.
• To adapt the design to match the implementation
  environment, designing it for performance.

• IMPLEMENTATION
• To define the organization of the code, in terms
  of implementation subsystems organized in layers,
• To implement classes and objects in terms of
  components (source files, binaries, executables,
  and others),
• To test the developed components as units, and
• To integrate the results produced by individual
  implementers (or teams), into an executable
  system.

8
Use Case Diagram Example
ltltextendgtgt
Buy Tickets via Web
9
Activity Diagram Example
10
Class Diagram Example

• Constraints
• Derived Attributes
• Association Classes

11
Statechart Example
12
UML Diagrams in the Process
Business Modelling
Requirements
Analysis Design

• Implementation

Use Cases
Activity Diagrams
Class Diagrams
Statecharts
13
Business Modeling BUC Model
14
Business Model BUC Model
15
Business Model BO Model
16
Business Modeling BO Model
17
Business Modeling BO Model
18
Discussion

• Business Model vs. Early Requirements
• From Requirements to System Specification
  UML/Tropos
• UML and Tropos Mutually Exclusive Choices?

OO AO
18