1 / 9

Plug & Play Adapters

Plug & Play Adapters. Adapter = “adapter” AdapterName “{“ <ground> CollabName <super> CollabName List(MemberDefinition) List(AdaptClause) ”}”. AdaptClause = <ground> ClassName “as” <super> ClassName AdaptationBody. AdaptationBody = List(MethodDefinition). Plug & Play Adapters.

ulmer
Télécharger la présentation

Plug & Play Adapters

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. Plug & Play Adapters Adapter = “adapter” AdapterName “{“ <ground> CollabName <super> CollabName List(MemberDefinition) List(AdaptClause) ”}”. AdaptClause = <ground> ClassName “as” <super> ClassName AdaptationBody. AdaptationBody = List(MethodDefinition).

  2. Plug & Play Adapters provides super collaboration Y requires Adapter provides ground collaboration X requires

  3. Plug & Play Adapters: they are partitioned provides super collaboration Y1 Y requires XY Adapter provides ground collaboration X1 X requires

  4. Why partitioning? • When we implement the required interface of Y, we might want to use the provided interface of X1 and Y1. Why is this not needed? • Mira writes: in XY part of connector all public provided X and Y definitions are visible. Why cannot we use the provided X1 definitions? Why are they not needed?

  5. Why partitioning? • I argue that implementing the required interface of Y may require services of multiple participants of the ground collaboration. Example (in DJ): • class Y {Z required() { return TraversalGraph.compute(cd, new Strategy(“from Y to Z”)).fetch();} may traverse through several participants.

  6. Personalities • By partitioning the adapters we say that X + XY is a personality that requires exactly what Y provides. Therefore Y personifies X + XY.

  7. Subclasses X as Y XY is equivalent to class X extends Y { Xbody;XYbody} • X gets the provided interface of Y • The methods that Y requires are provided in subclass X.

  8. Proposal • In XY part of connector all public provided Y methods and all provided methods of ground collaboration are visible.

  9. Collaboration Refinement provides super collaboration Y requires provides more May have more participants, including hidden participants. sub collaboration X requires less

More Related