Social Structures in Tropos Manuel KolpPaolo GiorginiJohn Mylopoulos U Louvain U Trento U Toronto U Louvain U Trento U Toronto First Tropos Workshop, Trento,

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 2 4. Achieving Qualities.
Advertisements

1 Hot DAML: Electronic Commerce Gateway David E. Anyiwo Bowie State University July 18, 2001.
Agent Based Software Development
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Design Concepts and Principles
Systems Analysis and Design, 7e Kendall & Kendall
Effective Coordination of Multiple Intelligent Agents for Command and Control The Robotics Institute Carnegie Mellon University PI: Katia Sycara
An Architecture-Based Approach to Self-Adaptive Software Presenters Douglas Yu-cheng Su Ajit G. Sonawane.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Lecture 13 Revision IMS Systems Analysis and Design.
Formal Service-Oriented Development of Fault Tolerant Communicating Systems Linas Laibinis, Elena Troubitsyna, Johan Lilius, Qaisar Malik (Åbo Akademi)
Course Instructor: Aisha Azeem
Chapter 10: Architectural Design
Community Manager A Dynamic Collaboration Solution on Heterogeneous Environment Hyeonsook Kim  2006 CUS. All rights reserved.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Implementing Strategy Through Organizational Design
What is it? A mobile robotics system controls a manned or partially manned vehicle-car, submarine, space vehicle | Website for Students.
A Goal-Based Organizational Perspective on Multi-Agent Architectures Manuel Kolp Department of.
A Requirement-Driven Development Methodology Jaelson Castro † Manuel Kolp ‡ John Mylopoulos ‡ ‡ Department of Computer Science University of Toronto University.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 10 Architectural Design
Software Development Process
A Research Agenda for Accelerating Adoption of Emerging Technologies in Complex Edge-to-Enterprise Systems Jay Ramanathan Rajiv Ramnath Co-Directors,
ARTIFICIAL INTELLIGENCE [INTELLIGENT AGENTS PARADIGM]
Systems Analysis and Design in a Changing World, Fifth Edition
What is Architecture  Architecture is a subjective thing, a shared understanding of a system’s design by the expert developers on a project  In the.
Performance analysis and prediction of physically mobile systems Point view: Computational devices including Mobile phones are expanding. Different infrastructure.
A Goal-Based Organizational Perspective on Multi-Agent Architectures Manuel Kolp † Paolo Giorgini ‡ John Mylopoulos † † Department of Computer Science.
 Applied Architectures and Styles Chapter 11, Part 2 Service-Oriented Architectures and Web Services Architectures from Specific Domains Robotics Wireless.
L 9 : Collaborations Why? Terminology Coherence Coordination Reference s :
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Dart: A Meta-Level Object-Oriented Framework for Task-Specific Behavior Modeling by Domain Experts R. Razavi et al..OOPSLA Workshop DSML‘ Dart:
Chapter 10 Information Systems Analysis and Design
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
SOFTWARE DESIGN.
TROPOS Derived from the Greek tropé, which means easily changeable, also easily adaptable. Presented By: Varun Rao Bhamidimarri.
Software Architectural Styles Andrew Midwinter, Mark Mullen, Kevin Wong, Matt Jones 1.
1 Introduction to Software Engineering Lecture 1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Designing software architectures to achieve quality attribute requirements F. Bachmann, L. Bass, M. Klein and C. Shelton IEE Proceedings Software Tzu-Chin.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Design Concepts By Deepika Chaudhary.
A Social Organization Perspective on Software Architecture Manuel KolpJaelson CastroJohn Mylopoulos Department of Computer Science University of Toronto.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Separating Crosscutting Concerns in Agent Oriented Detailed Design: The Social Patterns Case Carla Silva Jaelson Castro Advisor: Jaelson Castro João Araújo.
Chapter 3 Strategic Information Systems Planning.
 2001 John Mylopoulos STRAW’ Software Architectures as Social Structures John Mylopoulos University of Toronto First ICSE Workshop titled “From.
Management: Arab World Edition Robbins, Coulter, Sidani, Jamali Chapter 9: Organizational Structure and Design Lecturer: [Dr. Naser Al Khdour]
Chapter 13 설계 개념 Architectural Design 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book “Software Engineering: A Practitioner’s.
An Architecture-Centric Approach for Software Engineering with Situated Multiagent Systems PhD Defense Danny Weyns Katholieke Universiteit Leuven October.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
Chapter 9 Architectural Design. Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software.
1 8.1 Requirements Analysis Rules of Thumb Rules of Thumb Models should focus on requirements that are visible within the problem or business domain. The.
Patterns -- Manuel Kolp Dept of Information Engineering and Computer Science 11b. Reference Models and Organizational Patterns Reference Models.
Lecture 9- Design Concepts and Principles
Chapter 1: Object-Oriented Thinking
Princess Nourah bint Abdulrahman University
Object-Oriented Design
Chapter 9 Architectural Design
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Lecture 9- Design Concepts and Principles
The Tropos visual modeling language A meta-model.
Chapter 9 Architectural Design.
Chapter 1: Introduction to Systems Analysis and Design
Market-based Dynamic Task Allocation in Mobile Surveillance Systems
Chapter 5 Architectural Design.
Agent-oriented Software Engineering Methodologies
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Social Structures in Tropos Manuel KolpPaolo GiorginiJohn Mylopoulos U Louvain U Trento U Toronto U Louvain U Trento U Toronto First Tropos Workshop, Trento, November

Social Structures in Tropos 2 Motivation Narrowing the gap between requirements modeling and system design Narrowing the gap between requirements modeling and system design Same concepts for both phases: Social and intentional structures Same concepts for both phases: Social and intentional structures Coordinated & autonomous with goals & social dependencies Coordinated & autonomous with goals & social dependencies Concepts from organization theory, … and early requirements modeling Concepts from organization theory, … and early requirements modeling Ontology: 3 levels (Macro, micro, atomic) Ontology: 3 levels (Macro, micro, atomic)

Social Structures in Tropos 3 Social Ontology 3 Levels 3 Levels 1 Macrolevel : Organizational Styles (Organization Theory) 1 Macrolevel : Organizational Styles (Organization Theory) –Vertical Integration, Pyramid, Joint Venture, Structure in 5, Bidding, Hierarchical Contracting, Co-optation, Takeover 2 Micro level : Social Patterns (Agent, COOPIS Community) 2 Micro level : Social Patterns (Agent, COOPIS Community) –Broker, Matchmaker, Contract-Net, Mediator, Monitor, Embassy, Wrapper, Master-Slave,... 3 Atomic : Social and intentional concepts – i* 3 Atomic : Social and intentional concepts – i* –goals, actors, social dependencies, …

Social Structures in Tropos 4 Organization Theory Mintzberg, Scott, Galbraith, … Mintzberg, Scott, Galbraith, … Studies alternatives and models for (business) organizations Studies alternatives and models for (business) organizations Model the coordination of business stakeholders -- individuals, physical or social systems -- to achieve common (business) goals. Model the coordination of business stakeholders -- individuals, physical or social systems -- to achieve common (business) goals.

Social Structures in Tropos 5 Structure in 5 Operational core : basic operations -- the input, processing, output associated with running the organization. Operational core : basic operations -- the input, processing, output associated with running the organization. Strategic apex : executive, strategic decisions. Strategic apex : executive, strategic decisions. Support : Assists the operation core for non-operational services outside the basic flow of operational procedures. Support : Assists the operation core for non-operational services outside the basic flow of operational procedures. Technostructure : standardizes the behavior of other components, help the system adapt to its environment. Technostructure : standardizes the behavior of other components, help the system adapt to its environment. Middle line : Actors who join the apex to the core. Middle line : Actors who join the apex to the core.

Social Structures in Tropos 6 Structure in 5 and Joint Venture

Social Structures in Tropos 7 Bidding and Vertical Integration

Social Structures in Tropos 8 Structure in 5 in detail (from Mintzberg)

Social Structures in Tropos 9 Formal Analysis Dependency StrategicManagement Type SoftGoal Mode achieve Depender MiddleAgncy Dependee Apex Attribute constant objective : MiddleAgencyObjective Creation condition  objective.strategy condition  objective.strategy trigger Pursue(objective) Fulfillment condition for depender  ma-strategy: MiddleAgencyStrategy  ma-strategy: MiddleAgencyStrategy (  org -strategy: OrgStrategy (objective.strategy=strategy ^ consistent(ma-strategy,org-strategy)) consistent(ma-strategy,org-strategy)) [the StrategicManagement dependency is created when there is no strategy for a given middle agency objective, and it is fulfilled when there exists a middle agency strategy consistent with all the strategies of the organization]

Social Structures in Tropos 10 The Mobile Robot Case Study Mobile robot activities: Mobile robot activities: - Acquiring the input from sensors, - Controlling the motion of moveable parts, - Planning its future path. External Factors: External Factors: - Obstacles may block the path, - Sensor inputs may be imperfect, - The robot may run out of power, - Mechanical limitations may restrict accuracy - The robot may manipulate hazardous materials, - Unpredictable events may leave little time for responding.

Social Structures in Tropos 11 Conventional Architectures Task Trees : Hierarchies of tasks. Parent tasks initiate child tasks. Temporal dependencies between tasks permit selective concurrency. Layers Control Loop

Social Structures in Tropos 12 Organizational Architectures: Structure-in-5

Social Structures in Tropos 13 Quality Attributes for Mobile Robots Coordinativity. A mobile robot has to coordinate the actions it undertakes to achieve its objective with the reactions forced on it by the environment. Coordinativity. A mobile robot has to coordinate the actions it undertakes to achieve its objective with the reactions forced on it by the environment. Predictability. For a mobile robot, never will all the circumstances of the operation be fully predictable. The architecture must provide the framework in which the robot can act even when faced with incomplete information. Predictability. For a mobile robot, never will all the circumstances of the operation be fully predictable. The architecture must provide the framework in which the robot can act even when faced with incomplete information. Failability-Tolerance. Must prevent the failure of the robot’s operation and its environment. Local problems like reduced power supply, unexpectedly opening doors should not necessarily imply the failure of the mission. Failability-Tolerance. Must prevent the failure of the robot’s operation and its environment. Local problems like reduced power supply, unexpectedly opening doors should not necessarily imply the failure of the mission. Adaptability. Application for mobile robots frequently requires experimentation and reconfiguration. Changes in assignments require regular modification. Adaptability. Application for mobile robots frequently requires experimentation and reconfiguration. Changes in assignments require regular modification.

Social Structures in Tropos 14 Strengths and Weaknesses of Robot Architectures LoopLayers Task Tree S-in-5Joint-Vent. Coordinativity Predictability Failability-Tol Adaptability

Social Structures in Tropos 15 Coordinativity Control loop: Simplicity is a drawback when dealing with complex tasks, no leverage for decomposing the software into more precise components. Control loop: Simplicity is a drawback when dealing with complex tasks, no leverage for decomposing the software into more precise components. Layers: services and requests between adjacent layers. Transactions not always straight-forward. Need to skip layers to coordinate behavior. Layers: services and requests between adjacent layers. Transactions not always straight-forward. Need to skip layers to coordinate behavior. Task trees: clear separation of action and reaction. Allows incorporation of concurrent agents. Components have little interaction with each other. Task trees: clear separation of action and reaction. Allows incorporation of concurrent agents. Components have little interaction with each other. Structure-in-5: separates data (sensor control, interpreted results, world model) from control (motor, navigation, scheduling, planning and user- level) hierarchies Structure-in-5: separates data (sensor control, interpreted results, world model) from control (motor, navigation, scheduling, planning and user- level) hierarchies Joint venture: Components interact via the joint manager for strategic decisions. They indicate their interest, the joint manager returns them such information or mediates the request to other partner component. Joint venture: Components interact via the joint manager for strategic decisions. They indicate their interest, the joint manager returns them such information or mediates the request to other partner component.

Social Structures in Tropos 16 NFR Analysis: Selecting Architectures

Social Structures in Tropos 17 Mobile Robot Organizational Environment With the Bidding Style 0. task auctionned Issuer Auctioneer Bidder

Social Structures in Tropos 18 Using These Social Structures at All Steps Early requirements (organization modeling): stakeholders (people, organizations, systems), goals and dependencies. Early requirements (organization modeling): stakeholders (people, organizations, systems), goals and dependencies. Late requirements, the system-to-be as one or a few social actors (blackbox) participating in the organization model. Late requirements, the system-to-be as one or a few social actors (blackbox) participating in the organization model. Architectural design, the system as an organization of actors Architectural design, the system as an organization of actors Detailed design, system actors transformed into agents by means of social patterns Detailed design, system actors transformed into agents by means of social patterns Implementation: Multi-agent system as societies of individuals to achieve particular, possible common goals. Implementation: Multi-agent system as societies of individuals to achieve particular, possible common goals.

Social Structures in Tropos 19 Media Industry: Early Requirements Organization Modeling with the Joint Venture Style

Social Structures in Tropos 20 Media Industry: Late Requirements With the Vertical Integration Style With the Bidding Style

Social Structures in Tropos 21 Media Industry: Architectural Design E-business styles: on web, protocols, technologies Not on business processes, NFRs No organization of the architecture, conceptual high- level perspective

Social Structures in Tropos 22 Social Patterns Embassy Mediator Contract-Net

Social Structures in Tropos 23 Detailed Design with Social Patterns

Social Structures in Tropos 24 Conclusion System described with concepts from requirements and organization modeling System described with concepts from requirements and organization modeling  Narrows the gap requirements / design  Narrows the gap requirements / design Multi-Agent Architectures as social and intentional structures Multi-Agent Architectures as social and intentional structures Best suited to open, dynamic and distributed applications Best suited to open, dynamic and distributed applications Ontology on 3 levels: Ontology on 3 levels: –Macro: Organization Styles –Micro: Social Patterns –Atomic: i* - goals, actors, social dependencies, …

Social Structures in Tropos 25 Discussion: Problems, Suggestions ??? Organization Theory why not Sociology, Group Dynamics, … Organization Theory why not Sociology, Group Dynamics, … Formalization at the metalevel: Makes sense, not too abstract?? Formalization at the metalevel: Makes sense, not too abstract?? Formal result: ex.: sound and complete, instantiation ethics Formal result: ex.: sound and complete, instantiation ethics Convincing real-world size case study: Organization Modeling, Early (Business) Requirements Convincing real-world size case study: Organization Modeling, Early (Business) Requirements Styles vs Patterns Macro level Microlevel Styles vs Patterns Macro level Microlevel Convincing for organization theorists, sociologists, ontologists?? Convincing for organization theorists, sociologists, ontologists?? NFR evaluation: intuitive vs formal for Requirements/Architectures NFR evaluation: intuitive vs formal for Requirements/Architectures WRT Conventional Architectures: pros & cons, reevaluation WRT Conventional Architectures: pros & cons, reevaluation Methodology: Social Structures at all steps makes sense? Methodology: Social Structures at all steps makes sense?