A Social Organization Perspective on Software Architecture - PowerPoint PPT Presentation

errin
a social organization perspective on software architecture n.
Skip this Video
Loading SlideShow in 5 Seconds..
A Social Organization Perspective on Software Architecture PowerPoint Presentation
Download Presentation
A Social Organization Perspective on Software Architecture

play fullscreen
1 / 12
Download Presentation
A Social Organization Perspective on Software Architecture
102 Views
Download Presentation

A Social Organization Perspective on Software Architecture

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. A Social Organization Perspective on Software Architecture Department of Computer Science University of Toronto Toronto M5S 3G4, Canada Centro de Informática Universidade Federal de Pernambuco Recife 50732-970, Brazil Manuel Kolp Jaelson Castro John Mylopoulos STRAW’01 - May 14 2001, Toronto, Canada

  2. Motivation • Narrowing the gap requirements >< architectures • Same concepts for requirements and architectures • Software architecture as social organization • Coordinated autonomous components with goals to fulfil and social inter-dependencies ( i*) • Concepts from organization theory • Evaluated WRT a set of software quality attributes • Part of TROPOS (http://www.cs.toronto.edu/km/tropos) Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  3. Organization Theory • Mintzberg, Scott, Galbraith, … • Studies alternatives and models for (business) organizations • Used to model the coordination of business stakeholders -- individuals, physical or social systems -- to achieve common (business) goals. • Structure in 5, Pyramid, Takeover, Joint Venture, Cooptation, Hierarchical Contracting, Vertical Integration, Bidding, Merger, Equity Agreement, Virtual Organization, … Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  4. Structure in 5 • Strategic and logistic components found in organizations. • Operational core:basic operations-- the input, processing, output associated with running the organization. • Strategicapex: executive,strategic decisions. • Support : Assiststhe operation core for non-operational services outside the basic flow of operational procedures. • Technostructure : standardizesthe behavior of other components, help the systemadaptto its environment. • Middle line : Actors whojointhe apex to the core. Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  5. Structure in 5 in i* and Telos TELL CLASS StructureIn5MetaClass IN Class WITH /*Class is a MetaMetaClass*/ attribute name: String part, exclusivePart, dependentPart ApexMetaClass: Class CoordinationMetaClass: Class MiddleAgencyMetaClass: Class SupportMetaClass: Class OperationalCoreMetaClass: Class END StructureIn5MetaClass In i* In Telos Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  6. Joint Venture in i* and Telos TELL CLASS JointVentureMetaClass IN Class WITH /*Class is a MetaMetaClass*/ attribute name: String part, exclusivePart, dependentPart JointManagementMetaClass: Class part, exclusivePart /*exclusive and independent part*/ PrincipalPartnerMetaClass: Class part /*shared and independent part*/ SecondaryPartnerMetaClass: Class END JointVentureMetaClass In Telos Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  7. Quality Attributes Predictability, Security, Adaptability, Cooperativity, Competitivity, Availability, Integrity, Modularity, Aggregability Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  8. Example A Classical mobile robot layered architecture Information exchange not always straight-forward Often need to establish direct communication Data and control hierarchies not separated Prevent the dynamic manipulation of components Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  9. Mobile Robot Architecture: Structure-in-5 More distributed architecture Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  10. Selecting Architecture for an E-com System From Security, Availability, Adaptability Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  11. A Joint-Venture E-commerce Architecture E-business classical styles: on web, protocols, technologies Not on business processes, NFRs No organization of the architecture, conceptual high-level perspective Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001

  12. Conclusion • Software architectures described with concepts from requirements modeling • -> Narrows the gap requirements / architecture • Architectures as social and intentional structures • Best suited to open, dynamic and distributed applications • In progress • Formalizing the style, Instantiation of a style ?? • Macro and micro levels • Social Patterns : broker, mediator, embassy, ... Manuel Kolp, Jaelson Castro, John Mylopoulos, 2001