1 / 27

The OO-H method

Valencia. June 2001. The OO-H method. C. Cachero, J. Gómez, A. Párraga, O. Pastor DLSI. Universidad de Alicante DSIC. Universidad Politécnica de Valencia SPAIN. OO-H Objetives.

asher
Télécharger la présentation

The OO-H method

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. Valencia June 2001 The OO-H method C. Cachero, J. Gómez, A. Párraga, O. Pastor DLSI. Universidad de Alicante DSIC. Universidad Politécnica de Valencia SPAIN

  2. OO-H Objetives • Definition of new views that provide existing software engineering approaches (UML-compliant models) with interface modelling capabilities. • Inclusion of reuse mechanisms in the model refinement process. Valencia June 2001

  3. OO-H is not... • An Application Modelling Tool BUT an Interface Modelling Tool. • A methodology for developing web sites BUT a method to model and integrate high quality interfaces with preexisting business logic modules. Valencia June 2001

  4. Pattern Catalog OO-H: an overview Valencia June 2001

  5. Class Diagram APD’s NAD’s Update Marketing Authorize Credit Order Entry Bill Customer Schedule Delivery Inventory OO-H Design Process Use Case Diagram 1..N 1..N 1..N DESIGN PROCESS 1. Start from Class Diagram and Use Case Diagram 2. Create a NAD instance 3. Generate a Default APD 4. Apply refinements to APD 5. Generate deliverables refinements Pattern Catalog asp jsp pyth html xml wml Valencia June 2001

  6. Modelling Constructs: MANAGE CONFERENCE • Navigation Classes • Navigation Links Decorators: • Visibility (V|R|H) • Perspectives (P) • Meta attributes • Patterns (Pt) • Filters (F) NAD (I): Constructs • Navigation Targets • Collections Valencia June 2001

  7. NAD (II): Navigation Links • Six types: I-Links, T-Links, R-Links, X-Links, S-Links, Sr-Links • Activation Links • Metamodel attributes: • Visualization • User Interaction • Application Scope Valencia June 2001

  8. NAD (III): Patterns & Filters • PATTERNS • Indexing • Navigation • FILTERS • In origin (Fo) • In destination (Fd) • User-defined • Domain-dependent • $, $$ Valencia June 2001

  9. Associated Expression NAD (IV): Parameter Interaction • Defined inside the Service Links • They have an associated Response Link • 5 Introduction Modes • Hidden • Constant • Immediate • Selection • Navigation Valencia June 2001

  10. Review System Class Diagram Valencia June 2001

  11. PCChair Use Case Diagram Valencia June 2001

  12. PCChair NAD (level 0) (View prototype) Valencia June 2001

  13. (View NC pt) (View CD pt) NAD (V): Final NAD (View APD) (View TS pt) Valencia June 2001

  14. APD (I): General Concepts • Abstract pages = XML documents. • A different template definition (DTD) for each dimension of the interface: tStruct, tForm, tFunction, tLink, tWidget, tLayout, tLocation, tStyle, TExternal(*), TLogic(*). Facilitates Reuse • Automatic derivation of a default APD out of the NAD. • Refined by means of patterns and its corresponding transformation rules. Valencia June 2001

  15. TLOGIC TFUNCTION APD (II): Page Taxonomy XMLTEMPLATES TSTRUCT TFORM TLINK TWIDGET TLAYOUT TLOCATION TSTYLE TEXTERNAL Valencia June 2001

  16. APD (III): Default APD (View NAD) Valencia June 2001

  17. Example of Template: TLink Valencia June 2001

  18. APD Refinements (I) • Two types: • Pattern-driven refinements • Designer-dependent refinements • OO-H Patterns: Transformation Rules • Python scripts easily integrated in the tool. • They can affect every construct of the APD. • The effects don’t necessarily appear on the diagram. Valencia June 2001

  19. Interface Behavior Pattern Catalog Valencia June 2001

  20. Final step: the CLD • It affects the XML content of tExternal, tLayout, tWidget, tLocation and tStyle (pure visualization). • ‘Multiview pattern’ is supported by means of different layouts. • The appearance specification is adapted (not lost) when the APD structure changes: design reuse. Valencia June 2001

  21. Generated Prototype (I) Valencia June 2001

  22. Generated Prototype (II) Valencia June 2001

  23. Generated Prototype (III) Valencia June 2001

  24. Generated Prototype (IV) Valencia June 2001

  25. Main Contributions • Modelling constructs for the definition of user-service interaction • Taxonomy of XML templates tackling the different perspectives involved in interface definition • Notion of Transformation Rule for Pattern implementation • Case Tool to support the OO-H design process, with shortcuts for the construction of the different diagrams Valencia June 2001

  26. Future Work • Detection of new Patterns and inclusion of correspoding TR in the CASE tool • Inclusion of Frameworks, with the same TR philosophy • Inclusion of Advanced Personalization Features • Event Modelling • Client Logic Modelling • ... Valencia June 2001

  27. For further comments... ccachero@dlsi.ua.es jgomez@dlsi.ua.es aparraga@dlsi.ua.es opastor@dsic.upv.es THANKS FOR YOUR ATTENTION!!! Valencia June 2001

More Related