FrameWeb. Vítor E. Silva Souza ~ vitorsouza

Transcription

1 FrameWeb Vítor E. Silva Souza ~ vitorsouza Department of Informatics Federal University of Espírito Santo (Ufes), Vitória, ES Brazil

2 License for use and distribution This material is licensed under the Creative Commons license Attribution-ShareAlike 4.0 International; You are free to (for any purpose, even commercially): Share: copy and redistribute the material in any medium or format; Adapt: remix, transform, and build upon the material; Under the following terms: Attribution: you must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use; ShareAlike: if you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. More information can be found at: Jun 2017 FrameWeb 2

3 FrameWeb Framework-based Design Method for Web Engineering: Architectural design; Web-based Information Systems (WISs); Framework or container-based. Masters dissertation (2007 Souza, Falbo & Guizzardi); Evolutions since 2015, work in progress. Jun 2017 FrameWeb 3

4 Motivation Use of frameworks: Promote robust architectures; Increase productivity (if WIS is not trivial); State-of-practice (especially for the Web); Drive the definition of standards; Bring frameworks to architectural models: Lack of proposals; More power (and responsibility) to software architects; Code generation (MDD). Jun 2017 FrameWeb 4

5 Frameworks History Jun 2017 [Martins, 2015] FrameWeb 5

6 FrameWeb in a nutshell Definition of a basic architecture; Separation of concerns in layers; Use of frameworks; A UML profile for construction of architectural models: Entity model; Persistence model; Application model Navigation model. Jun 2017 FrameWeb 6

7 Categories of frameworks Front Controller Dependency Injection Object/Relationa l Mapping Decorator Aspect-oriented Programming Authentication & Authorization etc Jun 2017 FrameWeb 7

8 Front Controller framework! Jun 2017 FrameWeb 8

9 Object/Relational Mapping framework Jun 2017 FrameWeb 9

10 Dependency Injection framework! Jun 2017 FrameWeb 10

11 Decorator framework Source: Jun 2017 FrameWeb 11

12 Aspect-Oriented Programming framework Jun 2017 FrameWeb 12

13 Current focus of FrameWeb Front Controller Dependency Injection Object/Relationa l Mapping Doesn t really affect models Decorator Jun 2017 FrameWeb 13

14 Proposed architecture Decorator Front Controller Dependency Injection O/R Mapping Jun 2017 FrameWeb 14

15 Original frameworks (2007) Jun 2017 FrameWeb 15

16 Running example LabES Portal!! Jun 2017 FrameWeb 16

17 Running example LabES Portal! Jun 2017 FrameWeb 17

18 Entity Model UML class diagram; O/R mappings added to classes via UML extensions; Use of sensible defaults; Guides the implementation of: Classes of the Domain package; O/R mapping for these classes. Jun 2017 FrameWeb 18

19 Entity Model UML Extensions O/R Mapping Extension Possible Values If the class is persistent, transient or mapped (not persistent itself, but its properties are persistent if another class inherits them) Name of the table in which objects of a class will be persisted If an attribute is persistent or transient If an attribute can be null when the object is persisted Date/time precision: store only the date, only the time or both (timestamp) If the attribute is the primary-key of the table Class stereotype Class constraint Attribute stereotype Attribute constraint Attribute constraint Attribute stereotype <<persistent>> <<transient>> <<mapped>> table=name (class name) <<persistent>> <<transient>> null not null precision = (date time timestamp ) <<id>> Jun 2017 FrameWeb 19

20 Entity Model UML Extensions O/R Mapping Extension Possible Values How the ID attribute should be generated: automatically, obtained in a table, use of IDENTITY column, use of SEQUENCE column or none If the attribute represents the versioning column. If an attribute should be stored in a large object field (e.g.: CLOB, BLOB) Name of the column in which an attribute will be persisted Size of the column in which an attribute will be persisted If the association should be embedded (instead of having its own table, the associated child class' attributes are placed in the parent's table) Attribute constraint Attribute stereotype Attribute stereotype Attribute constraint Attribute constraint Attribute stereotype generation = ( auto table identity sequence none ) <<version>> <<lob>> column=name (attribute name) size=value <<embedded>> Jun 2017 FrameWeb 20

21 Entity Model UML Extensions O/R Mapping Extension Possible Values Inheritance mapping strategy: one table for each class using UNION, one table for each class using JOIN or single table for the entire hierarchy Type of collection which implements the association: bag, list, set or map Order of an association's collection: natural ordering (implemented in code) or order by columns (ascending or descending) Cascading of operations through the association: nothing, persists, merges, deletions, refreshs or all Association fetching strategy: lazy or eager. Inheritance stereotype Association constraint Association constraint Association constraint Association constraint <<union>> <<join>> <<single-table>> collection = ( bag list set map ) order = ( natural column names [asc desc] ) cascade = ( none persist merge remove refresh all ) fetch = ( lazy eager ) Jun 2017 FrameWeb 21

22 Entity Model LabES Portal! Jun 2017 FrameWeb 22

23 Persistence Model UML class diagram; Based on the DAO pattern; Use of base DAO (e.g., nemo-utils) recommended; DAOs show domain-specific operations (usually queries); No UML extensions needed; Guides the implementation of: Classes and interfaces of the Persistence package. Jun 2017 FrameWeb 23

24 Persistence Model Base DAOs Jun 2017 FrameWeb 24

25 Persistence Model LabES Portal! Jun 2017 FrameWeb 25

26 Navigation Model UML class diagram; Component types and controller configuration added to classes via UML extensions; Use of sensible defaults; Guides the implementation of: Classes of the Control package; Web pages of the View package; Front Controller framework configuration. Jun 2017 FrameWeb 26

27 Navigation Model UML Extensions The type of each component is specified using UML stereotypes: Stereotype (none) <<page>> <<template>> Component type An action class, to which the Front Controller framework delegates the execution of the action. A static or dynamic Web page. A template that is processed by a template engine and is transformed into a Web page. <<form>> <<binary>> An HTML form. Any binary file that can be retrieved and displayed by the browser (e.g.: images, reports, documents, etc.). Jun 2017 FrameWeb 27

28 Navigation Model UML Extensions The meaning of dependency associations depend on their source and destination: From To Meaning Page / template Form Action class Action class Action class Action class Action class Page / template Binary file Action class A link in the page/template that triggers the execution of the action. Form data are sent to the action class when the form is submitted. The page/template is shown as one of the results of the action class. A binary file is shown as one of the results of the action class. An action class is executed as result of another. This process is known as action chaining. Jun 2017 FrameWeb 28

29 Navigation Model UML Extensions Finally, UML constraints on dependencies configure the Front Controller framework: Which method to call: method=name; Which result to display: result=name; Which result type to use: resulttype=(binary chain dispatch redirect template). Jun 2017 FrameWeb 29

30 Navigation Model LabES Portal Jun 2017 FrameWeb 30!

31 Application Model UML class diagram; No UML extensions needed; Guides the implementation of: Classes and interfaces of the Application package; Configuration of Dependency Injection framework. Jun 2017 FrameWeb 31

32 Application Model LabESPortal Jun 2017 FrameWeb 32

33 FrameWeb 2.0: 2015 and forward Some of the main limitations of the approach: The models may not be suited to other framework instances. What if I use JSF, CDI and JPA? The UML extensions do not prevent designers from including elements that do not belong in the model; There are no tools to help developers build models, verify models, generate code, etc. Jun 2017 FrameWeb 33

34 FrameWeb 2.0: 2015 and forward Proposals: Adopt MDD concepts in the method; A base (common) meta-model for FrameWeb using the MDD concepts; An extensible set of packages suited to specific framework instances (e.g., Struts 2, JSF, VRaptor, etc); FrameWeb Editor (CASE tool). Publications: 2015 paper and 2016 MSc dissertation of Beatriz Franco Martins. Jun 2017 FrameWeb 34

35 What is Model-Driven Development Key characteristics of Model Driven Development (MDD): The model is the design; The model will grow, evolve and extend; There is a flow from abstraction to abstraction; Implementation is directed derived from the model. Jun 2017 [Martins, 2015] FrameWeb 35

36 FrameWeb Language Definition Jun 2017 FrameWeb 36

37 Navigation Meta-model Jun 2017 FrameWeb 37

38 Framework Meta-model Jun 2017 FrameWeb [Martins, 2015] 38

39 FrameWeb Framework Definition JSF definition: Jun 2017 FrameWeb [Martins, 2015] 39

40 Navigation Model SCAP on JSF: [Martins, 2015] Jun 2017 FrameWeb 40

41 Navigation Model SCAP on VRaptor: [Martins, 2015] Jun 2017 FrameWeb 41

42 Navigation Model SCAP on Struts 2 : Jun 2017 FrameWeb 42

43 FrameWeb Editor Jun 2017 FrameWeb 43

44 Semantic FrameWeb / FrameWeb for Linked Data S-FRAMEWEB / FRAMEWEB-LD Jun 2017 FrameWeb 44

45 S-FrameWeb FrameWeb extension to help integrate the resulting WIS into the Semantic Web; Proposed process: Jun 2017 FrameWeb 45

46 Jun 2017 FrameWeb 46! S-FrameWeb LabES Portal Use of base ontology for educational portals:

47 S-FrameWeb LabES Portal Use of ODM (Ontology Definition Metamodel, by OMG) for the S-FrameWeb Domain Model:! XSD Datatypes Jun 2017 FrameWeb 47

48 S-FrameWeb LabES Portal Simplification of ODM: Jun 2017 FrameWeb 48

49 S-FrameWeb: back to FrameWeb Entity Model based on S-FrameWeb Domain Model: Specification of association navigabilities for the implementation of the classes; Addition of the O/R mappings for the configuration of the ORM framework; Use of the data types of the implementation platform instead of those defined by XSD; Persistence, Application and Navigation models as usual. Jun 2017 FrameWeb 49

50 S-FrameWeb LabES Portal Jun 2017 FrameWeb 50

51 S-FrameWeb runtime components Developed for the Struts 2 framework; Identifies requests coming from software agents and returns result in RDF/XML format:! Jun 2017 FrameWeb 51

52 FrameWeb-LD: 2016 and forward Some of the main limitations of the approach: Outdated Ontology Engineering process and modeling language; Does not take into account many principles and best practices of Linked Data; New technology (LD frameworks, triple stores, etc.) has been developed in the mean time; Jun 2017 FrameWeb 52

53 FrameWeb-LD: 2016 and forward Proposals: Use the SABiO approach for Ontology Engineering: Use the OntoUML language and its extensions: Build a Semantic/LD layer on top of FrameWeb 2.0. Publication: 2016 paper from Danillo Ricardo Celino. Jun 2017 FrameWeb 53

54 FrameWeb-LD: process Jun 2017 FrameWeb 54

55 FrameWeb-LD: domain ontology Jun 2017 FrameWeb 55

56 FrameWeb-LD: Vocabulary Meta-model Jun 2017 FrameWeb 56

57 FrameWeb-LD: entity model with vocab Jun 2017 FrameWeb 57

58 FrameWeb-LD: D2RQ c2d: < # Table Researcher map:researcher a d2rq:classmap; d2rq:datastorage map:database; d2rq:class c2d:researcher; d2rq:classdefinitionlabel "Researcher"; rdfs:subclassof foaf:person; owl:equivalentclass dblp:person;. map:researcher_name a d2rq:propertybridge; d2rq:belongstoclassmap map:researcher; d2rq:property vocab:researcher_name; d2rq:propertydefinitionlabel "Researcher name"; owl:equivalentproperty dblp:primaryfullpersonname; d2rq:column "Researcher.name";. Jun 2017 FrameWeb 58

59 FrameWeb-LD: Semantic Web Services Jun 2017 FrameWeb 59

60 FrameWeb-LD: 2016 and forward Work on challenges of the Semantic Web: Vocabulary mapping; ID resolution; Provenance tracking; Data quality assessment; Performance and scalability issues; Semantic Web Services; Tools, tools, tools! Etc. Jun 2017 FrameWeb 60

61 Jun 2017 FrameWeb 61