 The need for a formal methodology description  SPEM for describing an agent oriented methodology  PASSI: an example  The needed extension  Discussion.

Slides:



Advertisements
Similar presentations
Software Process Modeling with UML and SPEM
Advertisements

UML an overview.
1 Chapter 4 - Part 1 Software Processes. 2 Software Processes is: Coherent (logically connected) sets of activities for specifying, designing, implementing,
SYSE 802 John D. McGregor Module 2 Session 2 Method Tailoring.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Unified Modeling Language
UML – Class Diagrams.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Systems Analysis and Design in a Changing World, 6th Edition
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Object Oriented Analysis and Design Using the UML
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
TC Methodology Massimo Cossentino (Italian National Research Council) Radovan Cervenka (Whitestein Technologies)
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
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: 
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
A language to describe software texture in abstract design models and implementation.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Design Concepts and Principles Instructor: Dr. Jerry Gao.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Copyright © 2013 Curt Hill UML Unified Modeling Language.
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.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
© 2005 Prentice Hall1-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
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.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
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.
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.
Welcome to M301 P2 Software Systems & their Development
UML Diagrams By Daniel Damaris Novarianto S..
Chapter 6 The Traditional Approach to Requirements.
Object-Oriented Analysis and Design
Object-Oriented Software Engineering Using UML, Patterns, and Java,
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Unified Modeling Language
UML Diagrams Jung Woo.
Object Oriented Analysis and Design
Rational Worldwide Software Symposium
Object Oriented Analysis and Design
Using and extending the SPEM specifications to represent agent oriented methodologies Valeria Seidita Valeria Seidita - 3 Dicembre 2007.
University of Houston-Clear Lake
Introduction to UML.
Rational Worldwide Software Symposium
SYS466 Domain Classes – Part 1.
Software Design Lecture : 15.
Requirement Analysis using
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
Rational Worldwide Software Symposium
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:

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

 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 Seidita3

4

 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 Seidita5

 Each fragment refers to one (or more) MMM element(s)  The MMM element is the constituent part of a Work Product  The MMM is not part of SPEM metamodel ◦ It is the element which leads us in modifying and extending SPEM diagram  We introduced MMM elements in the process description because when we construct a new design process we start from the definition of its metamodel ◦ Each part (one or more elements) of this metamodel can be instantiated in one (or more) fragment(s) Valeria Seidita6

 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 20077

 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 20078

 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 WorkDefinition 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 Valeria Seidita – Hammamet 12 december 20079

10 is a kind of contains is composed of is performed by

 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

 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

Valeria Seidita – Hammamet 12 december

 PASSI includes six disciplines  Direct correspondence between the disciplines and the PASSI phases Valeria Seidita – Hammamet 12 december

 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 Valeria Seidita – Hammamet 12 december

Valeria Seidita16

 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 Valeria Seidita – Hammamet 12 december

Valeria Seidita – Hammamet 12 december

 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 Valeria Seidita19

Valeria Seidita20