Software LEIC/LETI. Lecture 18

Transcription

1 Software LEIC/LETI Lecture 18

2 Last Lecture Web presentation patterns Model View Controller Template View Page Controller Front Controller Transform View Two Step View

3 Presentation logic Services Domain logic Remote access Data access

4 Presentation logic Services Domain logic Remote access Data access

5 Web Presentation Patterns

6 Model View Controller Template View Front Controller Page Controller Transform View Two Step View

7 Today Service-oriented Software Engineering Testing the complete system JMeter

8 Service-oriented Software Engineering

9 Servers should be accessible from other servers, not only from browser web services - loosely coupled reusable software components

10 Benefits of a serviceoriented approach

11 Inter-organizational services

12 Inter-organizational services The information about the service is public

13 Inter-organizational services The information about the service is public Binding to services can be delayed until needed

14 Inter-organizational services The information about the service is public Binding to services can be delayed until needed New services by service composition

15 Inter-organizational services The information about the service is public Binding to services can be delayed until needed New services by service composition Pay by service

16 Inter-organizational services The information about the service is public Binding to services can be delayed until needed New services by service composition Pay by service Smaller applications

17 (Sommerville, fig 18.1)

18 Service-oriented Architecture

19 (Sommerville, fige 18.2 and 18.3)

20 Service Composition compose and configure services to create new, composite services

21 (Sommerville, fig 18.13)

22 It is necessary to deal with several issues

23 service failure - transactional behaviour compensating transactions idempotent services service adaptability - flexibility need to undo services - because the complete composition cannot succeed compensating transactions

24 (Sommerville, fig 18.14)

25 use a formal language, e.g. BPMN

26 (Sommerville, fig 18.15)

27 (Sommerville, fig 18.16)

28 In the project

29

30 Testing the Service Compositions

31 External services are under the control of service providers Due to dynamic binding different services may be used Load of services may depend on their use by other applications Paid services can make testing expensive It is difficult to test unexpected behaviour

32 The use of mocking helps! What about load testing?

33 Testing the complete system

34 Can we test the system as a whole?

35 What can we test?

36 What can we test? functionality

37 What can we test? functionality non-functionality

38 How can it be described?

39 How can it be described? scenarios of usage

40 How can it be described? scenarios of usage profiles of usage

41 Weather information system SatComms WeatherStation Commslink WeatherData request (report) acknowledge reportweather () acknowledge get (summary) summarise () send (report) reply (report) acknowledge acknowledge (Sommerville, fig 8.8) use case-based testing (needs to include exceptions several test cases)

42 Who does the testing?

43 Who does the testing? developers

44 Who does the testing? developers quality assurance team

45 Who does the testing? developers quality assurance team users

46 System Testing developers test the complete system

47 find bugs System Testing developers test the complete system

48 functional find bugs and non-functional System Testing developers test the complete system

49 Release Testing quality team tests the complete system

50 business value Release Testing quality team tests the complete system

51 business value functional and non-functional Release Testing quality team tests the complete system

52 Scenarios of Use typical scenarios of use

53 Operational Profile 90% of the transactions are of type A, 5% of type B,

54 Stress Testing create operational profiles outside the limits of the system

55 User Testing user tests the complete system

56 validation User Testing user tests the complete system

57 functional validation and non-functional User Testing user tests the complete system

58 functional validation and non-functional alpha User Testing user tests the complete system

59 functional validation and non-functional alpha User Testing beta user tests the complete system

60 functional validation and non-functional alpha User Testing beta acceptance user tests the complete system

61 (Sommerville, fig 8.11)

62 JMeter

63

64

65 $ mvn -Pjmeter verify

66 Create a test

67 create a broker, 300 adventures, invoke process 1000 times and delete all brokers

68 define variables to ease modifiability

69 needs to be changed for each user define variables to ease modifiability

70 data to be used

71 data to be used file location

72 data to be used file location column names

73

74

75

76

77

78

79 1 thread executes once

80

81

82

83

84

85

86

87

88

89

90 there are 19 tuples in the file

91

92

93

94 there are 300 tuples in the file

95 there are 300 tuples in the file each adventure is processed 3 or 4 times

96

97 delete all brokers

98 delete all brokers

99 delete all brokers

100

101