Outline Context Problematic Related Works Statement Intentional - PowerPoint PPT Presentation

Assia Ait -Ali- Slimane Assia . ait - ali -slimane@ malix . univ - paris1.fr CRI, Universit é Paris 1 Panth é on - Sorbonne 1

Outline Context Problematic Related Works Statement Intentional Process Conclusion 2

Context Services Provider Publish Bind Search Repository Customer The functionalities of Services Needs are published 3

Context Services Provider Publish Bind Search Repository Customer The functionalities of Services Needs are published 4

Context Services Provider Publish Bind Search Repository Customer The functionalities of Services Needs are published Requirements : < functionnal + quality > 5

Context Services Provider Publish Bind Search Repository Customer The functionalities of Services Needs are published Provider : S atisfy a wide number of customers Service meets the Functional Requirement variability of QoS policy 6

Problematic Services Provider Bind Publish Search Repository Customer The functionalities of Services Needs are published Adapt dynamically services to quality requirements The SoC using one -dimensional service involves that some concerns, namely QoS are cross - services functionality 7

Related works (Tomaz et al, 06) propose a weaving tool by 1. implementing aspects - QoS - as services, whose aspects can be woven and adapted dynamically to service functionality. (Courbis and Finkeltein,05) modify the 2. Business Process Execution Language (BPEL) by using aspect specification. 8

Statement There is a lack concerning dynamic adaptability of 1. the business-logic services to QoS at the intentional level. An intentional approach to deal with the business- 2. logic service exists. it omits the quality dimension of services. 9

Intentional process Identify system goals by using map formalism, 1. Identify services from the map, 2. Distinguish different kinds of service, 3. Identify potential aspect. 4. 10

Map formalism Intention Strategy Start S dk I k S ki S jk S ij1 I j I i S ja S ij2 Stop S ii Section 11

Case study The example is extracted from our industrial experience through a company that industrialize automatons that analyses blood plasma in order to detect some haemostasis anomaly. The automatons hardware is composed of electronic and mechanical parts such as arm, drawer, needle, etc. The software manages the hardware to analyse the blood plasma, and other functionalities such as user authentication, sending analyse results and etc. Features, such as authentication, logging, or transactional mechanisms, must be considered. 12

1. Identify system goals S2: by loading product S3: by loading tube S1: by information Start capture in a Treat confidential way analysis S4: by chronometric request methodology S5: by photometric methodology Carry S10: by denied S6: by out request unblocking analysis analysis in less 13s and in a S7: by providing result confidential way S8: by blocking analysis Stop S9: by anomaly Goal: « Analyse blood plasma » 13

2. Identify services from the map Code Service Description S1 Treat analysis request This service provides the form to capture the necessary data about the by information information for the treatment of the analysis request. These inc lude the capture in a name of user, the blood plasma tube, and the test to launch. The se confidential way must be done in a confidential way. S2 Carry out analysis by This service provides the form to capture the necessary data about the loading product product for the carrying out of the analysis. These include the product identity, the name, the volume, and the expiration date. S6 Carry out analysis by This service provides the form to capture the necessary data about the unblocking analysis to unblock it. These include the user that unblocks the analysis in less analysis, the unblocked analysis. These must be doing in a fast way 13s and in a (less than 13s) and in a confidential way. confidential way 14

3. Distinguish different types of service Intentional Service 1 - Code Goal satisfies - Description 1 1 Verb Target Parameters 0..* 1 Way Quality Mean Manner Example: ( Treat) verb (analysis request) target (by information capture) manner (in a confidential way) quality 15

3. Distinguish different types of service We propose to consider each quality parameter of the map section as quality of service . E ach section can have several qualities of service . Example: (Carry out) verb ( analysis) target (by unblocking analysis) manner ( in less 13s) quality and ( in a confidential way) quality 16

Decomposition process Input: service. 1. Build a business service from the verb, the target, 2. the direction and the way parameters of the service goal. Build a quality service, corresponding to the quality 3. parameters : By giving a nominal expression to the quality parameter of 1. the service goal. It becomes the target of the new service. By using satisfy verb to build the new service. 2. Output: business service, quality service 4. 17

Example Code Service Quality parameter S1 Treat analysis request by information capture in a confidential way - in a confidential way service S2 Carry out analysis by loading product service S6 Carry out analysis by unblocking analysis in less 13s and in a - in less 13s confidential way service - in a confidential way Code Service Service type S1 Treat analysis request by information Information capture service Business service capture in a confidential way service Satisfy confidentiality service Quality service S2 Carry out analysis by loading product Loading product service service S6 Carry out analysis by unblocking Unblocking analysis service Business service analysis in less 13s and in a confidential way service Satisfy performance service Quality service Satisfy confidentiality service Quality service 18

4. Identify potential aspect An aspect definition contains Behaviour which is called advice . Potential advice Potential pointcut Satisfy confidentiality service , Satisfy performance service are the potential advices; Satisfy confidentiality before - Information capture - the former will be weaved ' before' service before service Information capture service and Unblocking - Unblocking analysis analysis service , service - the latter will be weaved ' before' and ' after ' Unblocking analysis service . Specification that expresses the pointcut . Satisfy performance before, after - Unblocking analysis service service Information capture service and Unblocking analysis service are the potential pointcuts . They are concerned by the introduction of quality behaviours. Weaving. consists to compose quality service to business service. 19

Conclusion An intentional process to deal with QoS as potential aspects. A goal/strategy graph is used to represent the system services: 1. map section definition. The process proposes to distinguish quality service from the bus iness one 2. service goal definition. The quality services are designed as potential aspects. 3. The main characteristic of this approach is its goal emphasis, n amely: the capture of the enterprises wishes and goals in terms the st akeholders can understand and 1. reason about easily, the early identification of both business services and quality s ervices that satisfy these goals. 2. Our Futur Works: Reasoning about the quality services (work to be published in I NFORSIDE08), Introducing conflictual quality services, 20

THANK YOU 21

This document was created with Win2PDF available at http://www.daneprairie.com. The unregistered version of Win2PDF is for evaluation or non-commercial use only.