Using and extending the SPEM specifications to represent agent oriented methodologies Valeria Seidita Valeria Seidita - 3 Dicembre 2007.

Slides:



Advertisements
Similar presentations
Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
Advertisements

Software Process Modeling with UML and SPEM
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel.
1 Chapter 4 - Part 1 Software Processes. 2 Software Processes is: Coherent (logically connected) sets of activities for specifying, designing, implementing,
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Unified Modeling Language
Prof. Ing. M. Dassisti Enterprise modelling for networked enterprise: interaction aspects for a training organisation 16th IFAC World Congress, Prague.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Object Oriented Analysis and Design Using the UML
Chapter 7: The Object-Oriented Approach to Requirements
Model-Driven User Requirements Specification using SysML Authors: Michel dos Santos Soares, Jos Vrancken Source: Journal of Software(JSW), Vol. 3, No.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
TC Methodology Massimo Cossentino (Italian National Research Council) Radovan Cervenka (Whitestein Technologies)
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s.
Experiences from a standardization attempt in AO methodologies Massimo Cossentino (Italian National Research Council)
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
 The need for a formal methodology description  SPEM for describing an agent oriented methodology  PASSI: an example  The needed extension  Discussion.
MFI-5: Metamodel for process model registration WANG Chong, HE Keqing, HE Yangfan, WANG Jian State Key Lab of Software Engineering (SKLSE) Wuhan University,
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Lab 5 CPIT 250 System Analysis and Design.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Towards filling the gap between AOSE methodologies and infrastructures: requirements and meta-model Fabiano Dalpiaz¹, Ambra Molesini², Mariachiara Puviani³,
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
Elaboration popo.
Introduction to UML.
Welcome to M301 P2 Software Systems & their Development
UML Diagrams By Daniel Damaris Novarianto S..
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
Architecture Concept Documents
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Unified Modeling Language
UML Diagrams Jung Woo.
Object Oriented Analysis and Design
Bussines process modeling using BPMN
University of Houston-Clear Lake
Introduction to UML.
Chapter 20 Object-Oriented Analysis and Design
SYS466 Domain Classes – Part 1.
Software Design Lecture : 15.
Software Design Methodologies and Testing
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
PASSI (Process for Agent Societies Specification and Implementation)
Uml diagrams In ooad.
Generic Statistical Information Model (GSIM)
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
MFI-5: Metamodel for process model registration
Presentation transcript:

Using and extending the SPEM specifications to represent agent oriented methodologies Valeria Seidita Valeria Seidita - 3 Dicembre 2007

Outline The need for a formal methodology description SPEM for describing an agent oriented methodology PASSI: an example The needed extension Discussion and conclusion Valeria Seidita

Introduction Adopting Situational Method Engineering for composing agent oriented design processes Process Requirements Analysis Method Fragments Selection Method Fragments Assembly It is fundamental the creation and the use of a method fragments repository To be constructed following a specific process Elements for constructing the repository A well known set of existing methodology The definition of method fragment to be used A notation to describe a development process Valeria Seidita

The Method Fragment Definition Valeria Seidita

The Process Description Three are the main elements of a design process Activity Process Role Work Product MMM Element The SPEM (Software Process Engineering Metamodel) is based on the idea that “a software development process is a collaboration between abstract entity called process role that perform operation called activities on tangible entities called work product”. Valeria Seidita

The Process Description Each fragment refers to one (or more) MMM element The MMM element is the constituent part of a Work Product The MMM is not part of SPEM metamodel It is the main element leading in modifying and extending SPEM diagram When we construct a new design process we start from the creation of its meta model Each part (one or more elements) of this meta model can be designed in one fragment (or more) Valeria Seidita

The Process Description The need for establishing which is the real action a process role performs on a MMM element when he is carrying out a specific activity The set of actions: Define – it is performed when a MMM element is introduced for the first time and its features are defined in a portion of process (hence in a fragment) Relate – when a relationship is created (defined) among two or more MMM elements previously defined in another portion of process Quote – a MMM element or a relationship is quoted in a specific work product Valeria Seidita – Hammamet 12 december 2007

Modelling a methodology with SPEM SPEM version 1.0 A top-down approach to describe who performs what and how SPEM main process component element we use: Process Component – a portion of process description that is internally consistent Discipline – is a specialization of process component that partitions activities under common theme Valeria Seidita – Hammamet 12 december 2007

Modelling a methodology with SPEM SPEM main structural elements a process description is composed of: WorkDefinition – the kind of operation describing the work performed in the process Phase – it is a specialization of WorkDefiniton and contains some milestones Activities – it describes a piece of work performed by one process role Step – the atomic part of an activity Process Role – defines the responsibility over a specific work product Work Product – the artifact, produced, consumed or modified by a process Far notare che the artefact, produced, consumed or modified by a process è in qualche modo legato a define relate e quote Valeria Seidita – Hammamet 12 december 2007 Valeria Seidita - 3 Dicembre 2007

Valeria Seidita – Hammamet 12 december 2007 Process Component Discipline is a kind of contains Phases is composed of Activities Per la descrizione di una porzione di processo o di un processo intero partiamo dalle discipline del process component Steps Process Role is performed by is composed of Valeria Seidita – Hammamet 12 december 2007 Valeria Seidita - 3 Dicembre 2007

Valeria Seidita – Hammamet 12 december 2007 SPEM Diagram The most important one for our purposes are: Activity Diagram – it allows describing the sequencing of activities with the input and output work products and separating the responsibility of each process role through swimlanes. Work Product Dependency Diagram – it allows to represent the dependencies among all the work product of design process. Valeria Seidita – Hammamet 12 december 2007

Valeria Seidita – Hammamet 12 december 2007 SPEM Diagram Other diagrams we use: Package diagram – allowing the representation of process component and discipline and its related process roles and workproducts Use Case diagram – for representing the relationships (for each discipline) among process roles and activities. Three different levels of details for activity diagrams: Process Component  Phase and Workproducts Phase  WorkDefinitions and UML Diagrams\Documents WorkDefioniton  ProcessRoles, Activity and UMLDiagr./Doc. Valeria Seidita – Hammamet 12 december 2007

Valeria Seidita – Hammamet 12 december 2007 An Example: PASSI Valeria Seidita – Hammamet 12 december 2007

Valeria Seidita – Hammamet 12 december 2007 An Example: PASSI PASSI includes six disciplines Direct correspondence between the disciplines and the PASSI phases Valeria Seidita – Hammamet 12 december 2007

Valeria Seidita – Hammamet 12 december 2007 An Example: PASSI Each phase produces a WorkProduct Each phase is composed of one or more sub-phases that we represented as WorkDefinitions A sub-phase is responsible for designing or refining one or more artefacts that are part of the corresponding model Each phase produces a document that is usually composed aggregating the UML models and work products produced during the related activities. Each phase is composed of one or more sub-phases each one responsible for designing or refining one or more artefacts that are part of the corresponding model (for instance the System Requirements model includes an agent identification diagram that is a kind of UML use case diagrams but also some text documents like a glossary and the system use scenarios). The details of each phase and its related sub-phases wil Valeria Seidita – Hammamet 12 december 2007 Valeria Seidita - 3 Dicembre 2007

An Example: PASSI Valeria Seidita

Valeria Seidita – Hammamet 12 december 2007 An Example: PASSI Input and output WorkProducts Responsibilities of each Process Roles Each Activity produces as results a WorkProduct where one (or more) MMM element is defined/quoted/relat ed Parte costituente di un work product è l’elemento del MMM, dell’intero processo, che in esso viene definito o rifinito. Ogni frammento fa riferimento ad un particolare elemento del MMM del processo; in altre parole qualunque processo di progettazione agent oriented presente in letteratura è sotteso da un ben preciso meta modello, ogni parte dell’intero processo, ogni componente o attività, è devoted alla progettazione di uno o più elementi di questo meta modello. Il risultato di una attività di un processo è un work product nel quale quindi uno o più elementi del meta modello vengono progettati. Valeria Seidita – Hammamet 12 december 2007 Valeria Seidita - 3 Dicembre 2007

Valeria Seidita – Hammamet 12 december 2007 The need for extension Valeria Seidita – Hammamet 12 december 2007

Conclusion SPEM is well suited for the description of an agent oriented methodology It provides a set of elements allowing a top- down decomposition of a methodology The proposed decomposition allows an easy identification/extraction of method fragments However we found some difficulties in the application and discrimination of the concepts of WorkDefinition, Phase and Activity; some simplifications was required SPEM si adatta bene alla descrizione di una metodologia ad agenti, esso fornisce una serie di elementi che permettono in maniera semplice di procedere ad una descrizione e scomposizione di una metodologia seguendo un approccio top-down; tuttavia abbiamo trovato difficoltà nella applicazione dei concetti di workdefinition phase e activity, per cui abbiamo dovuto in certo senso semplificare il meta modello in questo modo: Valeria Seidita Valeria Seidita - 3 Dicembre 2007

Thanks for your attention seidita@csai.unipa.it Valeria Seidita