1 / 5

Seamless Visual Object-Orientated Behavior Modeling for Distributed Software Systems

This presentation covers a domain-specific visual notation for designing distributed systems through Object Coordination Nets (OCoN). It employs UML for static structural notions while addressing dynamic aspects like coordination, concurrency, and object-oriented analysis/design (OOA/OOD). Key points include the flow and remote procedure calls (RPC) metaphors, and the use of Petri nets to represent system behaviors. The presentation emphasizes cognitive dimensions, visibility, and the importance of reducing secondary notation for improved understandability in complex software environments.

cynara
Télécharger la présentation

Seamless Visual Object-Orientated Behavior Modeling for Distributed Software Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Seamless Visual Object-Orientated Behavior Modeling for Distributed Software Systems Holger Giese, Jorg Graf and Guido Wirtz Institut fur Informatik,Westfalische Wilhelms-Universitat Presenters: Jack & Christian

  2. Background • Domain specific visual notation for distributed system design • Object Coordination Nets (OCoN) • Uses UML for structural notions static • Handles coordination, concurrency, and OOA/OOD dynamic • Flow and RPC metaphor • Petri net (Place/Transition net) • Three views - abstractions

  3. Views

  4. Cognitive Dimensions • Medium abstraction and closeness of mapping • High progressive evaluation • Possible to consider state of elements • Viscosity depends on editor • Should be low • No secondary notation • Placement does not matter • Visibility/Juxtaposability is good • Contract + Scenario using contract • Terseness: • Lower: Terse, Higher: Diffuse

  5. Comments • Dynamic aspects of distributed systems • Object Coordination Nets (OCoN) • UML and flow of data + Petri nets • Well-known visual notation, added elements • Working metaphor • Remote procedure calls, resources, contracts

More Related