INF5120 Model-based System Development

Transcription

1 INF5120 Model-based System Development Lecture 13: UI Models, and IFML, Process models (WebRatio) and Cordys Cloud April 22 nd, 2013 Arne J. Berre, SINTEF ICT Telecom and Informatics

2 Content Lecture plan 2013 Oblig 2 and 3 NoMagic MagicDraw (Cameo EA edition) Java 6, JEE WebRatio IFML Cordys Cloud platform Telecom and Informatics 2

3 INF Lecture plan (14/1): Introduction overview Enterprise Architecture with UML and BPMN and DSLs 2 (21/1): Service Innovation and Design, AT ONE method/workshop myservicefellow (Marika Lüders) 3: (28/1): Value Networks/VDML BPMN, vs. UML Activity diagrams - Oryx 4 (4/2): User experience and Touchpoints/UI Design Balsamiq (Amela Karahasanovic) 5 (11/2): UML and Req.Modeling Agile User stories versus Use cases 6 (18/2): Business-SoaML, Requirements Modeling, Goal Modeling, BMM, and Non Functional requirements 7 (25/2): Model driven engineering Metamodels, DSL, UML Profiles etc. NAV on NFR 8 (4/3): UML Service Modeling SoaML, UML 2.0 Service composition, MagicDraw 9 (11/3): Method Engineering, SW Process frameworks, SPEM/EPF, ISO 24744, FACESEM/ESSENCE (Brian Elvesæter) 10(18/3): Model driven engineering, transformation technologies, 11(8/4): MDE and DSL in practice, with ThingML example Franck Fleurey 12(15/4): System Architecture and Information/Ontology modeling, UML, ISO (22/4): UI Models, and IFML, Process models (WebRatio, Cordys Cloud) 14(29/4): System Architecture and Service models, semantic models 15(6/5): Platform models for the Cloud, with CloudML, Alessandro Rossini 16(13/5): Conclusion and Summary for INF Preparation for Exam Exam: Monday June 3rd, 2013, (4 hours) Telecom and Informatics 3

4 INF5120 Oblig plan (14/1): Introduction 2 (21/1): myservicefellow/service Design 3: (28/1): Oryx 4 (4/2): Balsamiq 5 (11/2): Use cases (18/2): Oblig 1 Group work 7 (25/2): EMF and Eclipse Group (3) presentation Business Model, Business-SoaML 8 (4/3): Oryx Group (3) presentation - User stories/use cases, UI, NFR 9 (11/3): Group presentation(s) on Oblig 1: User stories/use cases, UI/Balsamiq 10(18/3): Group presentation on Oblig 1 NFR 1 Parallell Start on Oblig 2 (individual) and Oblig 3 (group) - 22/3 : Delivery of Oblig 1 EASTER 11(8/4): Walk through of Oblig 1 Questions on Oblig 2 and 3 12(15/4): Question on Oblig 2 Value Network editor in Eclipse, description of Oblig 3 including references to MagicDraw Cameo Enterprise Architecture 13(22/4): Group work, Oblig 2/3 Group presentation/discussion 14(29/4): Group work, Oblig 2/3 Group presentation /discussion delivery Oblig 2 15(6/5): Delivery of Oblig 3 Concierge SA Model 11/5: Delivery of Oblig 3 16(13/5): Walk trough of Oblig 3 - Preparation for Exam Exam: Monday June 3rd, 2013, (4 hours) Telecom and Informatics 4

5 Oblig 3 Concierge Model-based System Architecture System Architecture for Concierge Basis for Cloud realisation MagicDraw Cameo Enterprise Architecture Use of Java, JEE 6.x. or use CORDYS Cloud platform. or use WebRation model platform with -IFML Information Model UML Class model Service Model SoaML model Process/Behaviour Model BPMN/Seq.diagrams, UI Model (ref. also Balsamiq) Telecom and Informatics 5

6 3-tier System Reference architecture UIC Legacy Application Layer: Business Layer: User Service Service Entity Service Infrastructure Data Layer: DataService Telecom and Informatics 6

7 MagicDraw Cameo Enterprise Architecture Telecom and Informatics 7

8 Download MagicDraw Enterprise Architecture Download MagicDraw from NoMagic full EA version Cameo Enterprise Architecture FR Enterprise Edition (Full license file until September 1, 2013 will be provided to each student) See many MagicDraw demonstrations/tutorials here: Including demo of UI modeling and code generation! Telecom and Informatics 8

9 JEE: Java Enterprise Edition Java for 3 tiers architectures Includes Java Libraries (Mail, Protocols, etc.) Tools, compilers, code generators, Application Server JEE 6.x Telecom and Informatics 9

10 References SiSaS Methodology Wiki JEE 6.0 First cup of JEE 6 Official JEE 6 tutorial Telecom and Informatics 10

11 models and concepts - WebRatio model based development - Provided by Marco Brambilla Politecnico di Milano and Web Models Srl

12 WebRatio and material 4 - slides on : (you can get the PPT file by clicking on SAVE) slides on large-scale experiences with webml: (you can get the PPT file by clicking on SAVE) exercises and other teaching materials: (slides are older than the above) our book on webml: Kaufmann-Management/dp/ /ref=sr_1_1?ie=UTF8&qid= &sr=8-1&keywords=designing+data+intensive+web+applications audio-video lessons on webml (oldish but still reasonable)

13 WebRatio and material 4 - download of webratio: (you need the personal edition trial version) Alternatively, you can ask an academic license for you and your students: wiki with issues organized by topic: forum for questions: new open source ifml editor:

14 The models 4 : a conceptual language for high-level design of dataintensive web sites 4 Models: Content: data organization Derivation: redundant data definition Composition: definition of site pages as set of subpages and elementary publishing units Navigation: definition of links between pages and between units Presentation: positioning of the units in the page and definition of graphical appearance 14

15 Preview of concepts 4 Site = Content + Composition + Navigation + Presentation entities, relationships units, pages, links site views styles content navigation + composition user models presentation 15

16 Structure Model (1) 4 Q: what are the objects published in the site and how they are related? 4 A: Entity: an object type in the application domain Attribute: scalar property of an entity Relationship: A connection between entities IS-A hierarchy: classification and grouping 4 Compatible with Entity-Relationship and UML class diagrams 16

17 Structure Model (2) 4 Simplified Entity-Relationship model Binary relationships between entities IS-A hierarchies Simple typed attributes in entities Derivation model can be applied for redundant data Author Book Genre BestSeller 17

18 Relationship cardinality 4 Relationship Book_Review book2review mincard: 0 maxcard: N review2book mincard: 1 maxcard: 1 Book 0..N Review 1..1 q It reads: a book may have zero or more reviews, a review deals with one and only one book 18

19 Derivation Objectives 4 Derivation is a modelling phase that makes it possible: To augment the content of an entity by adding attributes, either imported or calculated from related objects. To define the population of entities or of relationships, based on some property of the involved objects. 19

20 OCL 4 Derivation consist of writing expressions called derivation queries 4 Queries can be expressed using OCL 4 Derivable concepts: Entities, relationships, attributes 4 Derivation queries can be automatically transformed into SQl views installed in the database 20

21 Derived entities 4 Sub-Entities population in ISA hierarchies can be specified by means of OQL queries 4 A free slot is a slot having 0 reservations 4 OQL: SuperEntity where count(reservation)=0 ISA slot freeslot 21

22 Derived attributes 4 Attributes of an entity can be derived by associating to them a query. 4 Four types of derived attributes: Constant attribute: affiliation: Politecnico di Milano Imported attributes: maritalname: Self.husband.lastname Aggregate attributes: reservation#: count(self.reservation) Calculated attributes: lastprice: Self.price*discount 4 The Self keyword identifies the current entity in which the attribute is defined 22

23 Basic Content Units Content: instances of an entity DATAUNIT INDEXUNIT MULTIDATAUNIT Selector: set of conditions entity [Selector] entity [Selector] entity [Selector] ENTRYUNIT SCROLLERUNIT MULTICHOICE HIERARCHICAL entity [Selector] 23 entity [Selector] entity [Selector]

24 Meaning of Content Units DATAUNIT INDEXUNIT MULTIDATAUNIT Author first name:xxx last name:yyy photo: Index of Authors S. Ceri P. Fraternali O.Versand All Authors ENTRYUNIT SCROLLERUNIT MULTICHOICE HIERARCHICAL Insert Your Data Browse Authors Choose Authors Books&Authors Fname Lname 5/12: go to 1/ : Ceri Fraternali Versand 1. Web Applicat. Ceri Fraternali 2. Systems Tannenbaum 24

25 Pages 4 A page is a container of one or more pieces of information shown to the user at the same time 4 Nesting of pages is allowed: a page can have sub-pages 4 The user navigates a site made of pages Book Index Login Catalog 25

26 Non contextual links 4 A non contextual link is a link between pages 4 No context (information) is transported HomePage Book Index 4 The user can browse from a page to another one via an anchor (e.g., >>Books) 26

27 Home Page 4 The Home Page is the main page of a site 4 It is the first page of the site that the user should see 4 Each siteview must contain a page marked as Home HomePage H Book Index 27

28 Landmark pages 4 Landmark pages: globally visible pages. The user can jump to them from everywhere in the site view 4 It is equivalent to a non contextual link implicitly defined from every other page in the site view to the landmark page Books Store Page Books Store Page L Book Details Authors Book Details Authors 28

29 Areas 4 An area is a set of logically homogeneous pages 4 Examples of areas: Sections of a portal: Sport, Music, Technology, Elements of a data-management system: Products management, News management, 4 Areas can be nested, so that sub-areas can be defined inside areas 4 Each area should have a DEFAULT PAGE or a DEFAULT SUB- AREA, to give a meaning to landmark areas and noncontextual links pointing to areas Area 29

30 Site Views 4 A siteview is a set of pages and/or areas forming a coherent view of the site 4 Multiple site views can be defined on the same data model 4 Different site views can be published for different types of users and for different types of output devices 4 Site views can be Public: everyone can enter Private: access control with password protection is enforced 30

31 Acme site view modeling 4 Two site views on the same data model Customer: public, for customers Admin: private, for the administrators and content managers 31

32 Acme customer site view 4 Purpose: define the customer experience of the site 4 Structure: Two main areas: products and combinations Other landmark pages: home, stores Customer Product area Combination area L L Home Page H,L Store Page L 32

33 ACME page modeling 4 Q: what main pages do I need in the site? Home, Products, Combinations, Stores AcmeHome H L Product area Products L Combination area Combinations L Stores L Q: what other pages do I need? Product detail, Combination detail, ByPrice, BigImages,.. By price BigImages Product Page Combination Detail 33

34 ACME: HomePage 34

35 ACME product page 35

36 ACME combination page 36

37 Navigation Model: Links AuthorID is transported entity: author Book [ author2book ] Semantics of a link: 1. Moving from one place to another 2. Transporting information from one place to another (navigation context) 3. Activating a computation (side effect) 37

38 Composition: Pages A Page is a structured container of units and links Possibly structured in and/or sub-pages Abstraction of screen, frame, card, deck... Permits one to cluster related information for more efficient communication E.g.: Author Author The index of authors and the selected author are shown together in the same page 38

39 Types of links 4 Contextual links Between units Context transported 4 Non-contextual links Between pages No context transported Voyages Books 39

40 Operation Unit 4 Models a generic external operation, or a built-in content manipulation operation 4 Input from one or more incoming links (at least one is declared as normal link, the others as transport links) 4 Two kinds of output links OK link if the operation completes correctly KO link if the operation fails 4 The predefined units can be enriched by adding custom external operations (e.g. SendMail, ) 40

41 Built-in Operations 4 predefines a set of frequently used built-in operations to manage a site s content 4 They are the traditional database operations: create, delete, modify, create relationship, delete relationship 4 Users do not need to define the behaviour and the implementation; they are provided off-the-shelf in the model 41

42 Built-in Operations CREATE DELETE MODIFY Create Unit Delete Unit Modify Unit Entity Entity Entity CONNECT DISCONNECT Connect Unit Disconnect Unit relationship 42 relationship

43 In/out flows value1 attribute1 Create Unit KO OK Nothing OID of the new object value2 attribute2 value1 attribute2 Value2 attribute1 Entity Modify Unit KO OK Identifier(s) of the object(s) to modify Identifier(s) of the modified object(s) OIDs of objects to modify Entity 43

44 In/out flow: delete OIDs of the object(s) to delete Delete Unit KO OK OIDs of the object(s) to delete Nothing Example: Albums AlbumIndex Entity DeleteAlbum DeletionError NotDeleted KO OK Album Album Album OK Albums DELETE ALBUMS DeletionError NOT DELETED Albums DELETE ALBUMS All the way Anthology Born in the USA Bridges to Babylon Imagine Let's talk... Del Sing-a-long KO All the way 1999 Sing-a-long 1998 Let's talk Anthology Bridges to Babylon Imagine Del 44

45 In/out flow: connect 4 Note: if the any of the input parameters is a set of OIDs, the operation is applied to each element of the set 4 The disconnect operation is similar OIDs of source object(s) to connect OIDs of destination object(s) to connect Connect Unit relationship role KO OK Identifiers of the objects to connect Identifiers of the connected objects 45

46 Example ReviewPage Result NewReview KO Rev : Rev iew.oid ArtistDetai ls Rev iew AllArtists Rev : OID Art:OID AssignReview OK Art: Artist.OID Rev : Rev iew.oid Artist [OID = Art] ReviewDetails ArtistToRev iew [Artist.OID = Art ] [Rev iew.oid = Rev ] Artist Rev iew [OID=Rev ] KO Rev iewpage Result NEW REVIEW ARTISTS ARTIST REVIEW One of the most romantic and expressive artists of the nineties. Select an artist to assign the review: Review : Beatles * Dion Prince 46 OK First name: Celine Last name: Dion One of the most romantic and expressive artists of the nineties.

47 Example/2 Artist&AlbumsPage ArtistDetails KO OK Album Disconnect Artist PublishedAlbums AlbumDetails AlbumToArtist Album [ArtistToAlbum] Album KO Artist&Albums Celine Dion ALBUMS Artist&Albums Celine Dion ALBUMS DETAILS Artist&Albums Celine Dion ALBUMS All the way Let's talk... All the way Let's talk... Sing-a-long 1999 OK All the way Let's talk... Sing-a-long * Sing-a-long These are... These are... These are... Press OK to remove 47 OK

48 Siteviews 4 A Siteview is a set of pages that the user can experience as a whole Web site 4 Different site views can be defined for different devices and different groups of users 4 Thus, access control and multi-devices delivery is achieved 48

49 Using global information 4 It is often necessary to: Set a parameter value (e.g. the country or language preferred by a user) Use this value globally in all the pages the site view, without carrying it explicitly along links 4 Solution Use global parameters stored in the session Provide means for setting/getting their value 49

50 Context Parameters 4 Context Parameters allow to achieve this goal in a simple way 4 Designer defines one or more Context parameters. 4 A context parameter is defined by: Name ID Duration (User session or Application) Value type: can be either: A Printable value (integer, string, ) An Entity (thus, the parameter can assume an OID value of that entity) Starting value [optional] 50

51 Set unit 4 Unit that allows to SET the value of a parameter Value/OID 4 It is always placed outside a Page 4 It has only an incoming link (carrying the value to be assigned to the parameter) 4 It has not outgoing links ParamName 51

52 Get unit 4 Unit that allows to RETRIEVE the value of a parameter Value/OID ParamName 4 It is always placed inside a Page 4 It has only an outgoing link (carrying the value retrieved from the parameter) 4 It has not incoming links 4 The retrieved value can be used in any compatible unit 52

53 Example SetCountry GetCountry NewsPage[L] CountryData CurrCountry CurrCountry CountrySelectionPage [L] ProductPage [L] CountryIndex CountryData CountryData Country LocalNews Country Country Country LocalProducts News [Country2News] Product [Country2Product] 53

54 Personalization and access control 4 In reserved Web sites commitment wants: One or more public pages readable from anyone A set of private page accessed only after login, which contains personal content and personal services Personalization in terms of delivered pages (which pages user can access) and delivered content (which content user needs/can see) 54

55 Development process 55

56 Web services architecture BPEL4WS WCSI BPML WSFL XLANG UDDI IBM, Microsoft & BEA Sun BPMI.org IBM Microsoft UDDI.org Service Integration Service Discovery UDDI UDDI.org Service Publication WSDL W3C Service Description SOAP XML HTTP W3C W3C W3C XML -based Messaging Transport 56

57 Service integration layer 4 Choreography or collaboration layer 4 Describes the interaction of services within a process 4 Business processes are essential to build complex applications over the message-based paradigm. 4 Example: BPEL4WS 4 An implementation language: it allows to define new Web services as composition of existing ones 4 The composed service is described by means of WSDL, just as any other Web service 4 The process specification describes how the composed service plugs into the global process 57

58 Application scenario 4 Ski Portal stores touristic info on resorts and slopes plus name/address of hotels Reservations are done through the HMS web services Payment is done through the PS web services The HMS also delivers auxiliary services usable by the Ski Portal (e.g., hotel news, event notifications, user comment management) HTTP HTTP Ski portal Web appl. Resorts Ski slopes Hotels Clients Reservations Web service operations Hotel management system (HMS) Payment system (PS) 58

59 Types of interactions (as from WSDL) 4 Central component of a web service: operation = 1 or 2 msg Request-response Solicit-response Notification One-way Ski portal Web application One-way subscription to hotel news Hotel news notification HMS Get room offers request Room offer response Concert tickets solicit Concert tickets response 59

60 Synchronous vs. asynchronous 4 Two-message operations may be used Synchronously: no action is taken between 1 st and 2 nd messg and the sender waits Asynchronously: action is performed between the messages, the sender does not wait Ski portal HMS Get room offer request Make comment request Room offer response Comment response Solicit number of users connected Number of users. response Concert tickets solicit Concert tickets response 60

61 Conversations 4 A Web service conversation is a set of correlated messages involving one or more Web services (and Web applications) 4 Conversations entail additional semantics Messages belonging to the same conversation must be recognized and traced Timeouts or error conditions can be specified for the messages of a conversation Exceptions should be handled 61

62 support for web services 4 Goal: modeling the interaction between the Web application, the human users, and the remote systems 4 New modeling primitives are required: Data model: specific entities modeling the interaction history with Web services Hypertext model: primitives for handling the various classes of service operations 4 Run-time support for Web services Ability of exchanging messages Integration of application data and Web services XML messages Support for conversations 62

63 63 Meta-data model for Web services Out In Conversation Instance TimeStamp Status 1:N PartOf 1:1 Operation Instance TimeStamp 1:1 1:1 0:1 1:1 MessageType Name Out In OperationType OpName PortName Binding ServiceName NetworkAddress Timeout 1:1 1:1 0:1 0:1 1:1 1:1 0:N 0:N ConvType 1:N PartOf 1:1 0:N 0:1 Name Timeout Format Message Instance Content

64 for supporting Web services 4 One operation for each class of Web service operations ReqRsp SolRsp AsReqRsp AsSolRsp OneW Notif ConvName ConvName ConvName ConvName ConvName ConvName Marks for operations that start, resp. end conversations ReqRsp ReqRsp ConvName 64 ConvName

65 service operations are macros 1. Create a new Conversation Instance getoffer 2. Create a new Operation Instance Name= getoffer", 3. Connect the Operation Instance to the Conversation Instance 4. Compose parameters of the incoming links into an XML message 5. Send XML message; block waiting for answer 6. Decompose XML answer may involve populating the entities of the underlying data schema 7. Export selected element from the answer as parameters of the outgoing links ReservConv 65

66 Hypertext with service calls Room search RoomCrit From To getoffer ReservConv Reservation User data Confirmation Confirmed Reservation Offers RoomOffer Book ReservConv User [OID=CurrentUser] New Reservation CreditInfo CCNo Exp. Confirm ReservConv Pay 66 ReservConv

67 Hypertext with async messaging Added new entity Comment(OID,subject, text, answer) + Relationship Comment_User Connect Answers to my comments User data Send comment Create Comment2User User data Comment Subj Text Comment Comment User [OID=currentUser] MyComm User [OID=currentUser] CommConv A: text C:Comment.OID 67 Update Comment <answer:=a> Comment [Comment2User] [answer!=null] Answered Comment

68 data transformation 4 Web services communicate through XML messages (SOAP) 4 Marshalling and transformation between messages and from/into structured data is required 4 XML-in & XML-out: marshalling XML documents ßà ER instance 4 Adapter unit: XML transformations from XML document to another XML document (through user-defined XSL stylesheet) Adapter XML 68

69 Examples Book New Book Adapt Store XML New ReservConv Reservation ReservConv Reservation Pay Confirm Pay Adapt Confirm ReservConv ReservConv ReservConv ReservConv 69

70 BPMN* à transformation (1) (2) (3) (4) (5) One Orchestration control site view siteview serviceview per view: lane: a per controller user business per pool: navigation pool: Human component logics WS Choreography interaction of activities invokes and the gateways activities 4 Transformation rules finer-grained Application Model, needing few refinements by the designer typed activities enables reusable application models data dependencies are specified at a higher level less errors in Application Model design Faster development 70 70

71 Data Model Process Metadata Actors Run-Time Log 71

72 The NEXT unit The Next unit encapsulates the process control logic It exploits the information stored in the Process Metadata It calculates the current process status and the enabled state transitions It needs the following input parameters: caseid (the currently executed process instance ID) activityinstanceid (the current activity instance ID) conditionparameters (the values to evaluate the conditions) NEXT 72 72

73 The NEXT unit (cont.d) 4 execution modes: Process start. Instantiates and starts a case for the given ProcessID. Process end. Given the activityinstanceid of the last activity, sets the Case to Ended. Calculate and execute. Given the actinstid of the last concluded activity, enables the execution of the subsequent activities. Execute. Given an actinstid, sets its status to Active and launches its execution. NEXT 73 73

74 Next Unit Orchestration Modules 74

75 Next Unit 75

76 Design process 76

77 WebRatio 7 BPM 4 WebRatio 7 BPM permits you to: Model and Document your processes Execute and Validate your processes by instantly prototyping Developing, Improving and Refining your processes and create a complete Web application 77

78 WebRatio functionalities 4 Content model design 4 Business proces model design 4 Data derivation (Derivation Wizard) 4 Hypertext model design (siteviews) 4 Consistency checks (warnings) 4 Mapping onto a datasource 4 Units positioning in the pages 4 Automatic web site generation 4 Integration of advanced features (BPM, Web services, AJAX) 78

79 Model transformations 79

80 Interaction Flow Modeling Language - New Standard from OMG Marco Brambilla

81 IFML Submitters Submitters WebRatio Fujitsu Model Driven Solutions Thales (France) Softeam (France) Document numbers OMG Document Number: ad/ IFML Metamodel XMI, ad/ IFML UML Profile XMI, ad/ IFML Diagram Interchange XMI, ad/

82 Coverage of requirements All mandatory requirements All optional requirements: Modularization Input validation Missing discussions: Mapping to PSM Examples on integrated usage with UML 82 82

83 Proof of concepts 4 Consolidated evaluation of WebRatio toolsuite 10 years of experience Will be updated to the new IFML notation Implementation of new, open-source IFML modeling tool Eclipse based EMF / GMF Integration with UML / fuml / Alf 83 83

84 Proof of concepts 84 84

85 The metamodel 1: Core - Content 85 85

86 The metamodel 2 IFML Model 86 86

87 The metamodel 3 View Elements 87 87

88 The metamodel 4 Interaction Flow 88 88

89 Concrete notation - DD 89 89

90 IFML concrete syntax by example SelectedArtist à AnArtist 90 90

91 IFML concrete syntax by example 91 91

92 IFML concrete syntax by example 92 92

93 IFML concrete syntax extensions

94 IFML concrete syntax extensions

95 References IFML wiki IFML status and agenda Agenda Revised Submission Deadline: February 18,