The Tropos and MaSE Agent-Oriented Software Engineering Methodologies. Msury Mahunnah, Tallinn University of Technology
|
|
|
- Clara Fox
- 8 years ago
- Views:
Transcription
1 The Tropos and MaSE Agent-Oriented Software Engineering Methodologies Msury Mahunnah, Tallinn University of Technology
2 Mailing list for the course You can join at
3 The course webpages General information: Lectures and workshops:
4 Last time The Prometheus agent-oriented software engineering methodology
5 Prometheus AOSE methodology developed at RMIT under the leadership of Lin Padgham:
6 The conceptual space
7 The Prometheus process Detailed design Architectural design System specification Scenarios Interaction diagrams Protocols Process actors Capability overview Analysis agent acquaintance System Agent agent grouping Event descriptors System goals actions, percepts messages shared data Data descriptions Initial Role descriptors Agent descriptors Capability descriptors Plan descriptors Key final design artefact intermediate design artefact input Code
8 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
9 Percepts and Actions Agents are situated therefore need to define the interface(s) with the environment
10 Conference management system A collection of papers presented over several days Academics and students interested in presenting at the conference submit papers for consideration The papers must be submitted by a given deadline The papers are distributed by a program chair to members of the PC PC members may delegate to reviewers The reviews are completed by an internal deadline Papers are selected based on the reviews The authors are notified and provided with comments from the reviews Final copies are collected for publications
11 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
12 Analysis Diagram
13 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
14 Goal Diagram
15 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
16 System Roles Diagram
17 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
18 Scenario
19 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
20 Knowledge Coupling Key A W D role B X E knowledge C Y F role uses knowledge Z G role produces knowledge
21 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
22 Agent Acquaintance : derivation A W D A D E B C F B X E G C Y F Z G
23 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
24 Agent Descriptors Name Description Percepts responded to Actions executed Messages sent - to which agent, what content Messages received - from which agent, what content Internal events Knowledge used - external or shared internal Knowledge produced - external or shared internal Goals Roles included Creation/Destruction Cardinality (how many?)
25 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
26 System overview diagram
27 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
28 Interaction Diagram Example with Alternatives Agents Messages Time Multiple scenarios/ variations Decision point Agent X Agent Y Agent Z message A message D message B message C message E message G message E These should be variations in scenarios develop in message protocol F message G specification
29 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
30 Notation: AUML-2 Initiator Participant query-if x query-ref not-understood refuse failure x inform
31 Mapping Prometheus to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Analysis Diagram, System Roles Diagram Goal Diagram, Initial Role Descriptors, Scenarios Platformindependent computational design Platform-specific design and implementation Agent Acquaintance Diagram, Interaction, Protocol, System Diagram Event Descriptors Knowledge Coupling Data Descriptors Agent Descriptors Agent, Process Specifications, Capability
32 Agent overview diagram for Review_manager
33 Today The Tropos agent-oriented software engineering methodology The MaSE agent-oriented software engineering methodology
34 The Tropos process
35 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
36 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
37 Actor diagram
38 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
39 Goal diagrams
40 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
41 Expanded actor diagram
42 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
43 Goal diagram for CMS system
44 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
45 Refined goal diagram for CMS System
46 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
47 Further refined goal diagram for CMS System
48 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
49 Capability diagram
50 Mapping Tropos to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Actor Diagram Actor Diagram Goal Platformindependent computational design Refined Goal Platform-specific design and implementation Agent Interaction UML Class Capability, Plan
51 Agent interaction diagram
52 The MaSE process
53 Mapping MaSE to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Sequence, Role Model Goal Diagram, Use Cases, Role Model Platformindependent computational design Protocol, Agent Class Diagram Concurrent Tasks, Agent Class Diagram Platform-specific design and implementation Plan, Deployment
54 Mapping MaSE to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Sequence, Role Model Goal Diagram, Use Cases, Role Model Platformindependent computational design Protocol, Agent Class Diagram Concurrent Tasks, Agent Class Diagram Platform-specific design and implementation Plan, Deployment
55 Goal diagram
56 Elaborated goal diagram
57 Mapping MaSE to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Sequence, Role Model Goal Diagram, Use Cases, Role Model Platformindependent computational design Protocol, Agent Class Diagram Concurrent Tasks, Agent Class Diagram Platform-specific design and implementation Plan, Deployment
58 Role model
59 Mapping MaSE to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Sequence, Role Model Goal Diagram, Use Cases, Role Model Platformindependent computational design Protocol, Agent Class Diagram Concurrent Tasks, Agent Class Diagram Platform-specific design and implementation Plan, Deployment
60 Agent class diagram
61 Mapping MaSE to viewpoint framework Viewpoint models Viewpoint aspect Abstraction layer Interaction Information Behavior Conceptual domain modeling Sequence, Role Model Goal Diagram, Use Cases, Role Model Platformindependent computational design Protocol, Agent Class Diagram Concurrent Tasks, Agent Class Diagram Platform-specific design and implementation Plan, Deployment
62 Plan diagram for the Referee agent
An Investigation of Agent Oriented Software Engineering Methodologies to Provide an Extended Methodology
An Investigation of Agent Oriented Software Engineering Methodologies to Provide an Extended Methodology A.Fatemi 1, N.NematBakhsh 2,B. Tork Ladani 3 Department of Computer Science, Isfahan University,
Goal-Oriented Design of Agent Systems: A Refinement of Prometheus and its Evaluation. Jason Khallouf and Michael Winikoff*
Int. J. Agent-Oriented Software Engineering, Vol. x, No. x, xxxx 1 Goal-Oriented Design of Agent Systems: A Refinement of Prometheus and its Evaluation Jason Khallouf and Michael Winikoff* School of Computer
4. Multiagent Sys stems Design. Part 2: The PROMETHEUS methodology.
4. Multiagent Systems Design Part 2: Multiagent Syste ems (SMA-UPC) https://kemlg.upc.edu The PROMETHEUS methodology. Javier Vázquez-Salceda SMA-UPC Methodological Extensions to Object-Oriented Approaches
Evaluating the Coverage of Development Lifecycle in Agent Oriented Software Engineering Methodologies
Evaluating the Coverage of Development Lifecycle in Agent Oriented Software Engineering Methodologies N.Sivakumar Department of Computer Science and Engineering Pondicherry Engineering College Puducherry,
Agent-Oriented Software Engineering PORTO Methodology AIAD 2013/2014. António Castro and Eugénio Oliveira
Agent-Oriented Software Engineering PORTO Methodology AIAD 2013/2014 António Castro and Eugénio Oliveira NIAD&R Distributed Artificial Intelligence and Robotics Group 1 Contents What is AOSE? Main Existing
Prometheus: A Methodology for Developing Intelligent Agents
Prometheus: A Methodology for Developing Intelligent Agents Lin Padgham and Michael Winikoff RMIT University, GPO Box 2476V, Melbourne, AUSTRALIA Phone: +61 3 9925 2348 {linpa,winikoff}@cs.rmit.edu.au
Use Cases. Massimo Felici. Massimo Felici Use Cases c 2004 2011
Use Cases Massimo Felici Use Cases 1 Support requirements engineering activities and the requirement process Capture what a system is supposed to do, i.e., systems functional requirements Describe sequences
In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development Chapter 5C About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities
Model driven Security of Service Oriented Systems based on Security as a Service
Japan-Austria Joint Workshop on ICT October 18-19 2010, Tokyo, Japan SECTET Model driven Security of Oriented Systems based on Security as a Basel Katt, Ruth Breu, Mukhtiar Memon and Michael Hafner Research
Enterprise architecture Manufacturing operations management Information systems in industry ELEC-E8113
Enterprise architecture Manufacturing operations management Information systems in industry ELEC-E8113 Contents Enterprise architecture (EA) Manufacturing operations management (MOM) Rationale of the lecture:
Enhancement of Development Technologies for Agent- Based Software Engineering
Enhancement of Development Technologies for Agent- Based Software Engineering Andre Karpištšenko Tallinn Technical University, Ehitajate tee 5 19086 Tallinn, Estonia andre@lap.ee Abstract. Current trends
A Review of Agent-Oriented Development Methodologies and Programming Languages/Frameworks
A Review of Agent-Oriented Development Methodologies and Programming Languages/Frameworks Khalil Salah Advanced Informatics School Universiti Teknologi Malaysia Kuala Lumpur, 54100, Malaysia Ardavan Ashabi
Agent-Oriented Software Engineering
ID2209 Distributed Artificial Intelligence and Intelligent Agents Agent-Oriented Software Engineering Mihhail Matskin: www.ict.kth.se/courses/id2209 Autumn 2015 Lecture Outline 1. When is an agent-based
Chapter 4 Software Lifecycle and Performance Analysis
Chapter 4 Software Lifecycle and Performance Analysis This chapter is aimed at illustrating performance modeling and analysis issues within the software lifecycle. After having introduced software and
Masters of Science in Software & Information Systems
Masters of Science in Software & Information Systems To be developed and delivered in conjunction with Regis University, School for Professional Studies Object Oriented Design Table of Contents January
COSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring 2008. For the 1 st Quiz
COSC 3351 Software Design Recap for the first quiz Spring 2008 For the 1 st Quiz Three large topic areas: UML syntax and diagrams Software architectural styles Object oriented design principles A couple
A Methodology to Evaluate Agent Oriented Software Engineering Techniques
Submitted to: The International Journal of Multiagent and Grid Systems, Nov. 2005. A Methodology to Evaluate Agent Oriented Software Engineering Techniques Chia-En Lin, Krishna M. Kavi Department of Computer
Basic Unified Process: A Process for Small and Agile Projects
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
Object-Oriented Design Guidelines
Adaptive Software Engineering G22.3033-007 Session 8 Sub-Topic 3 Presentation Object-Oriented Design Guidelines Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute
When security meets software engineering: A case of modelling. secure information systems
When security meets software engineering: A case of modelling secure information systems Haralambos Mouratidis 1, Paolo Giorgini 2, Gordon Manson 1 1 Department of Computer Science, University of Sheffield,
Model-driven Software Development (MDSE) for the Cloud
Module 1-5(a) Model-driven Software Development (MDSE) for the Cloud Business Modelling Scoping How to scope your software development 1 Outline Roadmap Recommended workflow Tasks and corresponding Work
Object-Oriented Systems Analysis and Design
Object-Oriented Systems Analysis and Design Noushin Ashrafi Professor of Information System University of Massachusetts-Boston Hessam Ashrafi Software Architect Pearson Education International CONTENTS
Business Process (BPMN) Course
Business Process (BPMN) Course 2 day course held as Public or On Site Course We also offer bespoke foundation & advanced modules which can be developed/adapted to suit requirements Course Objectives Day
JOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 8, Novmeber - December 2008 Extension of Object-Oriented Software
Remigijus Gustas. Department of Information Systems, Karlstad University, Sweden
Department of Information Systems, Karlstad University, Sweden Underlying principles of conventional Conceptual Modeling Approaches EM methods distinguish disparate views/dimensions (Zachman, 1987). UML
OMG s Second Workshop on Web Services. Orchestrating Web Services from a UML Development Platform
Transform your software architecture into a reusable asset OMG s Second Workshop on Web Services Orchestrating Web Services from a UML Development Platform Michel Brassard Founder & CTO mbrassard@codagen.com
Engineering of a Clinical Decision Support Framework for the Point of Care Use
Engineering of a Clinical Decision Support Framework for the Point of Care Use Szymon Wilk, PhD 1, Wojtek Michalowski, PhD 1, Dympna O Sullivan, PhD 1, Ken Farion, MD 2, Stan Matwin, PhD 1 1 University
VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS
VARIABILITY MODELING FOR CUSTOMIZABLE SAAS APPLICATIONS Ashraf A. Shahin 1, 2 1 College of Computer and Information Sciences, Al Imam Mohammad Ibn Saud Islamic University (IMSIU) Riyadh, Kingdom of Saudi
SOFT 437. Software Performance Analysis. Ch 5:Web Applications and Other Distributed Systems
SOFT 437 Software Performance Analysis Ch 5:Web Applications and Other Distributed Systems Outline Overview of Web applications, distributed object technologies, and the important considerations for SPE
Decomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces
Software Engineering, Lecture 4 Decomposition into suitable parts Cross cutting concerns Design patterns I will also give an example scenario that you are supposed to analyse and make synthesis from The
Software Rapid Approach to Agency Design and Development
1 Introduction Over the past decades, agents have become a powerful software abstraction to support the development of complex and distributed systems (Jennings 2001). They are a natural metaphor to understand
PROCESS MODELS FOR AGENT-BASED DEVELOPMENT
PROCESS MODELS FOR AGENT-BASED DEVELOPMENT Luca Cernuzzi 1,2, Massimo Cossentino 3, Franco Zambonelli 1 1) DISMI Università di Modena e Reggio Emilia, Italy 2) Universidad Catolica de Asunciòn, Paraguay
Communicating Systems
Communicating Systems with UML 2 Modeling and Analysis ofnetwork Protocols David Garduno Barrera Michel Diaz LEEJTEE WILEY Table of Contents Preface xi Chapter 1. Why Use UML to Model Network Protocols?
A Goal-Driven Project Management Framework for Multi- Agent Software Development: The Case of I-Tropos
LOUVAIN School of Management A Goal-Driven Project Management Framework for Multi- Agent Software Development: The Case of I-Tropos Yves Wautelet A dissertation submitted in fulfillment of the requirements
Enterprise Application Deployment: Amodel driven approach
Enterprise Application Deployment: Amodel driven approach Peter Golibrzuch Lufthansa Technik AG peter.golibrzuch@lht.dlh.de Alexander Holbreich Lufthansa Systems AG alexander.holbreich@lhsystems.com Simon
An Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications
An Aspect-Oriented Product Line Framework to Support the Development of Software Product Lines of Web Applications Germán Harvey Alférez Salinas Department of Computer Information Systems, Mission College,
Visual Modelling for Information Management. Author: Alex Jouravlev, Consultant with Business Abstraction
Visual Modelling for Information Management Author: Alex Jouravlev, Consultant with Business Abstraction Contents Introduction...1 What is Visual Modelling?... 1 Dimensions of Visual Modelling...2 Visual
2. Analysis, Design and Implementation
2. Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Individual Programs to Complete Application Systems Software Development: Goals, Tasks, Actors,
Integrated Development of Distributed Real-Time Applications with Asynchronous Communication
Integrated Development of Distributed Real-Time Applications with Asynchronous Communication Marc Schanne International Workshop on Java Technologies for Real-time and Embedded Systems (JTRES) 26-28 September
How To Develop A Multi Agent System (Mma)
S-Tropos: An Iterative SPEM-Centric Software Project Management Process Yves Wautelet, Manuel Kolp, Youssef Achbany IAG Institut d Administration et de Gestion, ISYS Unité de Systèmes d Information, Université
Designing Real-Time and Embedded Systems with the COMET/UML method
By Hassan Gomaa, Department of Information and Software Engineering, George Mason University. Designing Real-Time and Embedded Systems with the COMET/UML method Most object-oriented analysis and design
Table of Contents. Preface. Chapter 1 Introduction 1.1 Background. 1.2 Problem description. 1.3 The role of standardization. 1.4 Scope and objectives
Table of Contents Table of Contents Preface Chapter 1 Introduction 1.1 Background 1.2 Problem description 1.3 The role of standardization 1.4 Scope and objectives 1.5 Approach 1.6 Related work 1.7 General
Software Requirements Specification of A University Class Scheduler
Software Requirements Specification of A University Class Scheduler Deanna M. Needell Jeff A. Stuart Tamara C. Thiel Sergiu M. Dascalu Frederick C. Harris, Jr. Department of Computer Science University
Linking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models?
Linking BPMN, ArchiMate, and BWW: Perfect Match for Complete and Lawful Business Process Models? Ludmila Penicina Institute of Applied Computer Systems, Riga Technical University, 1 Kalku, Riga, LV-1658,
Business-Driven Software Engineering Lecture 3 Foundations of Processes
Business-Driven Software Engineering Lecture 3 Foundations of Processes Jochen Küster jku@zurich.ibm.com Agenda Introduction and Background Process Modeling Foundations Activities and Process Models Summary
One and a half hours QUESTION PAPER MUST NOT BE REMOVED FROM THE EXAM ROOM AND MUST BE RETURNED UNIVERSITY OF MANCHESTER SCHOOL OF COMPUTER SCIENCE
One and a half hours QUESTION PAPER MUST NOT BE REMOVED FROM THE EXAM ROOM AND MUST BE RETURNED UNIVERSITY OF MANCHESTER SCHOOL OF COMPUTER SCIENCE Software Engineering Date: Monday 19th January 2015 Time:
Analyzing Requirements of Knowledge Management Systems with the Support of Agent Organizations
Analyzing Requirements of Knowledge Management Systems with the Support of Agent Organizations Renata S. S. Guizzardi 1, Anna Perini 2 1 Computer Science Department University of Twente (UT) P.O. Box 217
What is Enterprise Architect? Enterprise Architect is a visual platform for designing and constructing software systems, for business process
1 2 3 What is Enterprise Architect? Enterprise Architect is a visual platform for designing and constructing software systems, for business process modeling, and for more generalized modeling purposes.
Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk. COMP 201 web-page: http://www.csc.liv.ac.
Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~coopes/comp201 Lecture 18 Introductory Case Study Introduction to UML During
Use Cases. Reference: Craig Larman, Applying UML and Patterns, Ch. 6
Use Cases Reference: Craig Larman, Applying UML and Patterns, Ch. 6 Use Case What it is: Text story Widely used to discover and record (mostly functional) requirements What is it about: Some actor(s) using
RUP Design. Purpose of Analysis & Design. Analysis & Design Workflow. Define Candidate Architecture. Create Initial Architecture Sketch
RUP Design RUP Artifacts and Deliverables RUP Purpose of 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
Background: Business Value of Enterprise Architecture TOGAF Architectures and the Business Services Architecture
Business Business Services Services and Enterprise and Enterprise This Workshop Two parts Background: Business Value of Enterprise TOGAF s and the Business Services We will use the key steps, methods and
Dr. Pat Mirenda. Software Design Specification Document
CPSC 319 Team 2 Dr. Pat Mirenda Software Design Specification Document Version: 1.2 Date: (03/17/2006) 2Communicate SDS Revisions Version Primary Author(s) Description of Version Date Completed 1.0 Wei
A Software Development Platform for SOA
A Software Development Platform for SOA Peter Eeles Executive IT Architect Rational Brand Architect for UK, Ireland and South Africa peter.eeles@uk.ibm.com 2004 IBM Corporation Agenda IBM Software Group
Chap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
Software Architecture Action Guide. Why do we care about Software Architecture?
Software Action Guide Dana Bredemeyer Bredemeyer Consulting Tel: (812) 335-1653 Fax: (812) 335-1652 Email: dana@bredemeyer.com Web: Why do we care about Software? Because we want to be a dominant player
Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Service Pack 2 MOC 10233
Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Service Pack 2 MOC 10233 Course Outline Module 1: Introduction to Designing a Microsoft Exchange Server 2010 Deployment This
Comparing Agent-Oriented Methodologies
Comparing Agent-Oriented Methodologies Khanh Hoa Dam kdam@cs.rmit.edu.au Michael Winikoff winikoff@cs.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne, Australia
Development of Enterprise Architecture of PPDR Organisations W. Müller, F. Reinert
Int'l Conf. Software Eng. Research and Practice SERP'15 225 Development of Enterprise Architecture of PPDR Organisations W. Müller, F. Reinert Fraunhofer Institute of Optronics, System Technologies and
Mastem: A Mathematics Tutoring Multi-Agent System
Mastem: A Mathematics Tutoring Multi-Agent System Jéssyka Vilela 1, Ricardo Ramos 2, Jaelson Castro 1 1 Universidade Federal de Pernambuco Centro de Informática Av. Jornalista Anibal Fernandes, S/N, Cidade
Sofware Requirements Engineeing
Sofware Requirements Engineeing Three main tasks in RE: 1 Elicit find out what the customers really want. Identify stakeholders, their goals and viewpoints. 2 Document write it down (). Understandable
RETRATOS: Requirement Traceability Tool Support
RETRATOS: Requirement Traceability Tool Support Gilberto Cysneiros Filho 1, Maria Lencastre 2, Adriana Rodrigues 2, Carla Schuenemann 3 1 Universidade Federal Rural de Pernambuco, Recife, Brazil g.cysneiros@gmail.com
Questions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
Building Service-oriented User Agents using a Software Product Line Approach. Ingrid Oliveira de Nunes ionunes@inf.puc-rio.br
Building Service-oriented User Agents using a Software Product Line Approach Ingrid Oliveira de Nunes ionunes@inf.puc-rio.br 2 Summary Introduction Objectives Integration of SOA, MAS and SPL Related Work
Frameworks of Process Improvement for Mobile Applications
Frameworks of Process Improvement for Mobile Applications Haeng-Kon Kim Abstract Mobile application development belongs on the complicated, but quite regular software development environment that includes
Tool-supported Development with Tropos: The Conference Management System Case Study.
Tool-supported Development with Tropos: The Conference Management System Case Study. M. Morandini, D. C. Nguyen, A. Perini, A. Siena, and A. Susi Fondazione Bruno Kessler - IRST Via Sommarive, 18 38050
An agent-oriented approach to change propagation in software evolution
An agent-oriented approach to change propagation in software evolution Khanh Hoa Dam, Michael Winikoff, and Lin Padgham School of Computer Science and Information Technology RMIT University GPO Box 2476V,
Table of Contents. CHAPTER 1 Web-Based Systems 1. CHAPTER 2 Web Engineering 12. CHAPTER 3 A Web Engineering Process 24
Table of Contents CHAPTER 1 Web-Based Systems 1 The Web 1 Web Applications 2 Let s Introduce a Case Study 3 Are WebApps Really Computer Software? 4 Are the Attributes of WebApps Different from the Attributes
Software Engineering Reference Framework
Software Engineering Reference Framework Michel Chaudron, Jan Friso Groote, Kees van Hee, Kees Hemerik, Lou Somers, Tom Verhoeff. Department of Mathematics and Computer Science Eindhoven University of
Component Based Development Methods - comparison
Component Based Development Methods - comparison Dan Laurenţiu Jişa Abstract: This paper realizes a comparison among three of the best known component based development methods, emphazing on the earlier
AN OVERVIEW OF SYSTEMS ANALYSIS: SYSTEMS ANALYSIS AND THE ROLE OF THE SYSTEMS ANALYST. Lecture 1. 21.10.2014, Tuesday
AN OVERVIEW OF SYSTEMS ANALYSIS: SYSTEMS ANALYSIS AND THE ROLE OF THE SYSTEMS ANALYST Lecture 1 21.10.2014, Tuesday 2 A Series of Lectures 1.The Role of the Systems 2.Project Planning and Project Management
Announcements. HW due today, 2 to grade this week Welcome back from Spring Break!
Announcements HW due today, 2 to grade this week Welcome back from Spring Break! Analysis (Domain) Modeling: Introduction Reading: Arlow and Neustadt chaps. 8, 9 (& 7) Also see Larman Chapter 10 (2 nd
Current Issues in Multi-Agent Systems Development (Invited Paper)
Current Issues in Multi-Agent Systems Development (Invited Paper) Rafael H. Bordini 1, Mehdi Dastani 2, and Michael Winikoff 3 1 University of Durham, U.K. R.Bordini@durham.ac.uk 2 Utrecht University,
Socially Grounded Analysis of Knowledge Management Systems and Processes. Email: rguizzardi@inf.ufes.br. Email: perini@itc.it
Socially Grounded Analysis of Knowledge Management Systems and Processes Renata S. S. Guizzardi 1, Anna Perini 2, Virginia Dignum 3 1 Computer Science Department, Federal University of Espírito Santo,
UML Diagram Types. Use Cases do the Following. Use Case Diagram
UML Diagram Types Dynamic Models activity diagrams statechart diagrams interaction diagrams sequence diagrams collaboration diagrams use case diagrams Structural Models class diagrams object diagrams packages
- 5 days (30 PDUs)... 15. ITIL V3 Intermediate Capability - Planning, Protection and Optimization... 14
Course List Business Analysis... 5 Advanced Business Analysis - 2 days (16 PD Hrs/CDUs)... 5 Basics of Business Analysis - 1 day... 5 Business Process Analysis - 2 days... 5 Business Analysis Certification
A Comparison of SOA Methodologies Analysis & Design Phases
202 A Comparison of SOA Methodologies Analysis & Design Phases Sandra SVANIDZAITĖ Institute of Mathematics and Informatics, Vilnius University Abstract. Service oriented computing is a new software engineering
5054A: Designing a High Availability Messaging Solution Using Microsoft Exchange Server 2007
5054A: Designing a High Availability Messaging Solution Using Microsoft Exchange Server 2007 Course Number: 5054A Course Length: 2 Days Course Overview This 2-day course teaches messaging engineers to
Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions
Announcements SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 Send your group
Karunya University Dept. of Information Technology
PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main
The Agent Modeling Language (AMOLA)
The Agent Modeling Language (AMOLA) Nikolaos Spanoudakis 1,2 and Pavlos Moraitis 2 1 Technical University of Crete, Department of Sciences, University Campus, 73100, Kounoupidiana, Greece nikos@science.tuc.gr
Logical Data Models for Cloud Computing Architectures
Logical Data Models for Cloud Computing Architectures Augustine (Gus) Samba, Kent State University Describing generic logical data models for two existing cloud computing architectures, the author helps
UML TUTORIALS THE USE CASE MODEL
UML TUTORIALS THE USE CASE MODEL www.sparxsystems.com.au Sparx Systems 2004 Page 1/5 describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between
How To Develop A Multiagent System
Towards a Comprehensive Agent-Oriented Software Engineering Methodology Dissertation vorgelegt dem Fachbereich Wirtschaftswissenschaften, der Universität Duisburg-Essen (Campus Essen) von Tawfig M. Abdelaziz,
Case Study Solutions. This appendix contains the solutions to the Acme Mining Company Case Study.
Case Study Solutions This appendix contains the solutions to the Acme Mining Company Case Study. Sun Proprietary: Internal Use Only 1 The Acme Mining Company Rewritten Problem Statement Note The candidate
A SYSTEMATIC APPROACH FOR COMPONENT-BASED SOFTWARE DEVELOPMENT
A SYSTEMATIC APPROACH FOR COMPONENT-BASED SOFTWARE DEVELOPMENT Cléver Ricardo Guareis de Farias, Marten van Sinderen and Luís Ferreira Pires Centre for Telematics and Information Technology (CTIT) PO Box
10 Proxy Pattern [Gamma et al]
![10 Proxy Pattern [Gamma et al]](/thumbs/31/14940468.jpg "10 Proxy Pattern [Gamma et al]")
10 Pattern [Gamma et al] pattern is used in scenarios when it is required to use avoid heavy-weight objects. So lightweight objects that are actually replica of the original objects exposing the same interface
Tropos: An Agent-Oriented Software Development Methodology
Autonomous Agents and Multi-Agent Sytems, 8, 203 236, 2004 Ó 2004 Kluwer Academic Publishers. Manufactured in The Netherlands. Tropos: An Agent-Oriented Software Development Methodology PAOLO BRESCIANI
Towards an Agent Oriented approach to Software Engineering
Towards an Agent Oriented approach to Software Engineering Anna Perini and Paolo Bresciani ITC-IRST Via Sommarive 18, 38055 Povo, Trento, Italy perini,bresciani @irst.itc.it John Mylopoulos Department
Evaluating Agent-Oriented Software Engineering Methodologies
Evaluating Agent-Oriented Software Engineering Methodologies Abdulsalam Alarabeyyat Information Technology Department (IT) Faculty of Prince Abdullah Bin Ghazi of Science and Information Technology Al-Balqa
Software Architecture Document
Software Architecture Document Natural Language Processing Cell Version 1.0 Natural Language Processing Cell Software Architecture Document Version 1.0 1 1. Table of Contents 1. Table of Contents... 2
Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Service Pack 2
Microsoft Exchange About this Course This five-day, instructor-led course provides you with the knowledge and skills to design and deploy messaging solutions with Server 2010. This course describes how
International Journal of Software Engineering and Knowledge Engineering Vol. 11, No. 3 (2001) 231-258 World Scientific Publishing Company
International Journal of Software Engineering and Knowledge Engineering Vol. 11, No. 3 (2001) 231-258 World Scientific Publishing Company MULTIAGENT SYSTEMS ENGINEERING SCOTT A. DELOACH, MARK F. WOOD AND
Project Plan. Building the Project Plan The Software Production Process Project Management, Integration, & Change. Mike McKerns, Caltech
Project Plan Building the Project Plan The Software Production Process Project Management, Integration, & Change Mike McKerns, Caltech Goals & Objectives The goal of DANSE is to build a software system
Lab Manual. Advanced Pr I IT 314
Lab Manual Advanced Pr I IT 314 Lab Instructions Several practicals / programs? Whether an experiment contains one or several practicals /programs One practical / program Lab Teacher forms groups of the
2. Analysis, Design and Implementation
2. Analysis, Design and Implementation Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Programs to Application Systems Products Software Development:
JOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2008 Vol. 7, No. 8, November-December 2008 From The Business Motivation Model (BMM)
10233B: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010
Course: 10233B: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Description: About this Course This five-day, instructor-led course provides you with the knowledge and skills
Applying 4+1 View Architecture with UML 2. White Paper
Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was
3.1 Use Case Diagrams
3.1 Subject/Topic/Focus: Introduction to Use Cases Summary: System Boundary Actors Use Cases Generalization, Inclusion, Extension Literature: [Fowler99], UML Distilled, Second Edition [Booch98] Last change: