Software MEIC. (Lesson 20)

Transcription

1 Software MEIC (Lesson 20)!

2 Last class C&C styles Publish-subscribe style Shared-data style Communicating processes style Tiers style

3 Today Finish the C&C styles Begin with the Allocation viewtype

4 Dynamic Reconfiguration

5 When are components and connectors created or destroyed?

6 In client-server?

7 In peer-to-peer?

8 In pipes-and-filters?

9

10 May define Configuration Managers

11 Are Configuration Managers part of connectors?

12 For all applications of C&C styles it is necessary to consider this style At least to say that C&C are configured at initialisation time

13 Service-Oriented Architecture (SOA) style

14 Interaction pattern: distributed components provide and/or consume services

15 Consumer Provider Call-return connector

16 What s the difference for Client-Server?

17 Consumer/ Provider Consumer/ Provider Provider

18 What s the difference for Peer-to-peer?

19 Components are standalone services (deployed independently, belonging to systems/organizations)

20 Typically use implementation languages/platforms

21 Adventure Builder Web browser Consumer Web site jdbc Adventure Catalog DB Key Client-side application Java EE application External Web service provider User s client OpcPurchase OrderService OPC OpcOrder TrackingService jdbc Adventure OPC DB Web services endpoint Data repository TBD CreditCard Service Web Service Broker service registry HTTP/HTTPS Bank ActivityPO Service SOAP call AirlinePO Service Airline Provider Lodging Provider LodgingPO Service Activity Provider Data access SMTP Scope of the application (not a component)

22 Keyword: interoperability

23 Typical SOAs use specialized components

24 Specialized SOA components Enterprise Service Bus (ESB) Service Registry Orchestration server

25 ESB: hub-and-spoke vs point-to-point topology

26 Consumer/ Provider Consumer/ Provider Provider

27 Consumer/ Provider Consumer/ Provider Enterprise Service Bus (ESB) Provider

28

29 ESB Routes messages Converts messages (e.g. HTTP to JMS) Transforms data Security checks Manages transactions

30 Improves interoperability, security, modifiability

31 Service registry improves transparency of location of service providers

32 Service Registry Consumer Provider

33 Increases modifiability

34 Orchestration server orchestrates interaction among consumers/providers

35 Consumer/ Provider Consumer/ Provider Enterprise Service Bus (ESB) Consumer Provider Orchestration Server

36 Orchestration server executes scripts upon the occurrence of an event (Typically defined in BPEL)

37 Improves interoperability, modifiability, reliability

38 SOA connectors Call-return - SOAP (XML messages over HTTP) - REST (HTTP commands on resources) Asynchronous messaging - Point-to-point - Publish-Subscribe

39 Adventure Builder Web browser Consumer Web site jdbc Adventure Catalog DB Key Client-side application Java EE application External Web service provider User s client OpcPurchase OrderService OPC OpcOrder TrackingService jdbc Adventure OPC DB Web services endpoint Data repository TBD CreditCard Service Web Service Broker service registry HTTP/HTTPS Bank ActivityPO Service SOAP call AirlinePO Service Airline Provider Lodging Provider LodgingPO Service Activity Provider Data access SMTP Scope of the application (not a component)

40 SOA often used to integrate legacy and external systems

41 End User Application Portal Internal System External Consumer Service Consumers SOA Infrastructure Internet Security Discovery Data Transformation Infrastructure Service A Service B Service C Service D Service Interfaces Internal Users Enterprise Information System Legacy or New Service Code External System Service Implementation

42 Finished the C&C styles

43 Generic C&C style Data-flow style See Section 4.2 Call-return style See Section 4.3 Event-based style See Section 4.4 Repository style See Section Batch sequential Pipe-andfilter See Client- Peer-to- Publish- Point-to- Shared- server See peer See subscribe See point messaging data See Pipeline UNIX pipeand-filter... Multi-tier client-server See SOA See Key Class of styles Blackboard Generalization

44 Architectural viewtypes Module Component-and-connector Allocation

45 Allocation viewtype

46 What is allocation?

47 How is the system related to CPUs, file systems, development teams, networks,...?

48 Maps software elements to environment elements

49 Software Element allocated-to Environment Element

50 What are the software elements? (Modules, components, connectors)

51 What are the environment elements? (Physical resources, people/teams, files)

52 4 styles Work-assignment Implementation Deployment Install

53 Software Module Element Work allocated-to Environment Person/team Element assignment

54 Module allocated-to Files Implementation

55 Component / Connector allocated-to Hardware Deployment

56 Component / Connector allocated-to Install Files

57 How to do the allocation?

58 Software Element allocated-to Environment Element Required properties match Provided properties

59 Deployment style

60 Component Process / Connector allocated-to Hardware

61

62

63 Where do processes come from?

64 From the various C&C views

65 Browser Web server DB

66 Where do processes execute?

67 Hardware Elements Processors Memories Disks Networks

68 How to do the allocation?

69 Process allocated-to Hardware Required properties match Provided properties

70 Which properties? (Processing power, memory, fault tolerance, )

71 What is this style for?

72 Analyses of various quality attributes: Performance Reliability Security Cost estimates

73 Example

74 Browser Web server Which hardware? DB

75 Browser Web server DB

76 Web server Browser DB

77 Browser Web server DB Internet? LAN?

78 Web server Browser Web server DB Web server

79 Browser Web Web Web server Web server Web server Web server Web server Web server Web server Web server Web server Web server Web server Web server Web server server server DB DB DB DB DB DB DB DB

80 Browser Web server DB Same C&C, Different deployments

81 Example using UML

82

83 Install style

84 Components & Connectors allocated-to Files

85 Files in the production environment (libraries, executable files )

86 libraries executable files data files log files configuration and version control files license files help files deployment descriptors scripts static content

87 One component or connector, many files

88 Supports the build of different versions of the systems

89 Software configuration and packaging to produce multiple versions of a system

90 Support internationalization Offer different pricing (for example, a free version and a commercial version) Accommodate customizations for different clients Support clients in a distributed system that still send old-version message requests

91 Remember the software configuration management patterns you learned in SE course

92 What is this style for?

93 To create build-and-deploy procedures To package a specific version of a software product line To update and configure files of multiple installed versions of the same system To navigate in the files and folders of the installed system

94 Example

95