1. 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 June 2001Valencia

2. Valencia June 20012 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.

3. Valencia June 20013 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.

4. Valencia June 20014 OO-H proposal Design Process Pattern Catalog Navigation view Presentation view OO-H CASE tool

5. Valencia June 20015 Pattern Catalog OO-H: an overview

6. Valencia June 20016 OO-H Design Process refinements Class Diagram NAD’s Bill Customer Update Marketing Inventory Authorize Credit Order Entry Schedule DeliveryAPD’s html xml wml asp jsp pyth 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 Pattern Catalog Use Case Diagram 1..N

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

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

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

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

11. Valencia June 200111 Review System Class Diagram

12. Valencia June 200112 PCChair Use Case Diagram

13. Valencia June 200113 PCChair NAD (level 0) (View prototype)

14. Valencia June 200114 NAD (V): Final NAD (View APD) (View NC pt) (View CD pt) (View TS pt)

15. Valencia June 200115 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. APD (I): General Concepts

16. Valencia June 200116 XMLTEMPLATES XMLTEMPLATES TFORM TLINK TWIDGET TLAYOUT TLOCATION TSTYLE TSTRUCT TEXTERNAL APD (II): Page Taxonomy TFUNCTIONTLOGIC

17. Valencia June 200117 APD (III): Default APD (View NAD)

18. Valencia June 200118 Example of Template: TLink

19. Valencia June 200119 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.

20. Valencia June 200120 Interface Behavior Pattern Catalog

21. Valencia June 200121 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.

22. Valencia June 200122 Generated Prototype (I)

23. Valencia June 200123 Generated Prototype (II)

24. Valencia June 200124 Generated Prototype (III)

25. Valencia June 200125 Generated Prototype (IV)

26. Valencia June 200126 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

27. Valencia June 200127 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...

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