1 / 11

Research Approaches

Research Approaches. A menu. Appetizers. Review Structure of GBC Business Service Business Pattern + Policies ADM FW Themes: encapsulation and refinement. A mille feuille. There is a clear precession of encapsulation going on, why not model it directly?

gypsy
Download Presentation

Research Approaches

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. Research Approaches A menu

  2. Appetizers • Review Structure of • GBC • Business Service • Business Pattern + Policies • ADM • FW • Themes: encapsulation and refinement

  3. A mille feuille • There is a clear precession of encapsulation going on, why not model it directly? • GBCs and Business Services are more alike than different. Both: • Encapsulate contents under well defined interface(s?). • Emphasize consistency over flexibility • Units of assembly by domain specialists

  4. The meat of the matter • Model Business Services and GBCs with the same construct • A GBC is basically just an exported / deployed Business Service • Maybe main difference between the two is that a GBC is connected to a concrete model • Or do we want to have all Services thus connected • Contain little or no code “in the raw”. • Code comes in the form contained components

  5. Side Dishes • A Business Service will contain several smaller components • May be Services, but eventually we will need Object Oriented Code: Business Patterns • Business Services combine Patterns to make consistency preserving high-level interfaces

  6. Cheese • Business Patterns are units of re-use. • Provide low-level programmatic interfaces with complicated semantics. • May be configured at deployment time by Policies passed in from encapsulating Service. • Question: Who writes policies; against which class model

  7. (Re)fine(d) Wines • Problem with policies is that they can only add forseen variation. • In general, we want to be able to take existing component and refine it : subcomponent. • Refined versions can always be substituted for the original. • This means that the substitution context becomes refined as well

  8. Major Food Groups • In order to have a meaningful definition of refinement for Business Services, we need to define the relation for Business Patterns. • Assume that patterns will be implemented as Aspectual Components • Get refinement relation “for free” • Johan + Karl Lieberherr are developing this.

  9. Cognac soothes difficulties • OCL constraints are necessary for instantiation in Collaborations. • Existential Types are necessary for Aspectual Collaborations • Paper describing difficulties/solutions hopefully submitted to ECOOP ’01. • Deadline is Nov 28

  10. Losing weight • Minimal class models come for free

  11. Doing Dishes • There are two approaches to Proxy vs Insertive approach.

More Related