Identifying Services in KAOS Models Authors: Eric Souza and Ana - - PowerPoint PPT Presentation

identifying services in kaos models
SMART_READER_LITE
LIVE PREVIEW

Identifying Services in KAOS Models Authors: Eric Souza and Ana - - PowerPoint PPT Presentation

SAC2018 Identifying Services in KAOS Models Authors: Eric Souza and Ana Moreira er.souza@campus.fct.unl.pt; amm@fct.unl.pt Presenter: Joo Arajo joao.araujo@fct.unl.pt April, 2018 SAC2018 Context Deploying Service-Oriented


slide-1
SLIDE 1

SAC2018

Authors: Eric Souza and Ana Moreira

er.souza@campus.fct.unl.pt; amm@fct.unl.pt

Presenter: João Araújo

joao.araujo@fct.unl.pt

April, 2018

Identifying Services in KAOS Models

slide-2
SLIDE 2

SAC2018

Context

  • Deploying Service-Oriented Architecture (SOA) in

an organization requires that the services are aligned with the business concerns [1, 2]

2

[1] Azevedo L. et al.. A method for bridging the gap between business process models and services. iSys-Revista Brasileira de Sistemas de Informação 6(1), 62–8, (2014) [2] Hans Weigand et al.. Value-based service modeling and design: Toward a unified view of services. In International Conference on Advanced Information Systems Engineering. Sprin- ger, Berlin, Heidelberg.

slide-3
SLIDE 3

SAC2018

Context

  • Lack of consensus on how service development life

cycle should be conducted [1]

  • Existing service-oriented works do not offer detailed

and systematic methods for business analysis and services identification [2]

3

[1] Q. Gu and P. Lago. A stakeholder-driven service life cycle model for SOA. In 2nd international workshop on Service oriented software engineering @ 6th ESEC/FSE joint

  • meeting. ACM, 1–7 (2007)

[2] T. Kohlborn et al.. Identification and analysis of business and software services at a consolidated approach. IEEE Transactions on Services Computing 2 (1), 50–64 (2009)

slide-4
SLIDE 4

SAC2018

Problem

  • Previously, we demonstrate how to generate goal-

models aligned with business models [1, 2]

  • Existing service-oriented works propose principles
  • r guidelines that are very difficult to follow in

practice due to lack of a systematic process [3]

4

Business Modeling Requirements Modeling SOA Modeling

[1] Souza et al., Aligning Business Models with Requirements Models. In Information Systems. 14th EMCIS 2017, LNBIP Vol. 299. Springer, 545–558. (2017) [2] Souza, E. et al., An approach to align business and IT perspectives during the SOA services identification. In Computational Science and Its Applications 2017, 3-6 (2017) [3] Azevedo L. et al., A method for bridging the gap between business process models and services. iSys-Revista Brasileira de Sistemas de Informac̨āo 6 (1), 62–98 (2014)

slide-5
SLIDE 5

SAC2018

Research Question

5

How to take a systematic approach to model SOA applications using goal models?

slide-6
SLIDE 6

SAC2018

  • SOA is an evolution of component-based

development where services are the main building component [1, 2]

  • Services are

typically specified using SOAML

6

Background

[1] T. Erl. Service-oriented architecture: concepts, technology, and design. Pearson Education, Inc, Indiana, USA. (2005) [2] Valipour et al., A brief survey of software architecture concepts and service oriented architecture. 2nd IEEE International Conference

  • n Computer Science and Information Technology, 34-38 (2009)
slide-7
SLIDE 7

SAC2018

  • Goal-oriented requirements engineering uses

goals to elicit, elaborate, structure, specify, analyze, negotiate, document, and modify requirements [1]

  • KAOS has been one of the most cited methods in

the literature [2]

7

Background

[1] A. van Lamsweerde. Goal-oriented requirements engineering: a guided tour. Requirements Engineering conference (RE), 2001 [2] F. Wanderley and J. Araûjo. Generating goal-oriented models from creative requirements using model driven engineering. MoDRE’13 (2013)

slide-8
SLIDE 8

SAC2018

KAOS4Services

8

slide-9
SLIDE 9

SAC2018

9

Create KAOS model

slide-10
SLIDE 10

SAC2018

10

  • System requirements are decomposed into human-intensive
  • perations (executed by people), and system-intensive
  • perations (requiring a number of computational transactions

with minimal or no human intervention)

  • Candidate services are identified from system-intensive
  • perations, and are ordered according to the designers’ order

given to operations

slide-11
SLIDE 11

SAC2018

11

Decompose requirements

slide-12
SLIDE 12

SAC2018

12

Generate business process

slide-13
SLIDE 13

SAC2018

13

Generate business process

slide-14
SLIDE 14

SAC2018

14

Generate business process

slide-15
SLIDE 15

SAC2018

15

Generate business process

slide-16
SLIDE 16

SAC2018

16

Generate business process

slide-17
SLIDE 17

SAC2018

17

  • The execution of this non-mandatory activity depends on the level
  • f detail the service designer wants
  • The more detailed the business process is, the more detailed the

service specification will be

slide-18
SLIDE 18

SAC2018

18

Identify candidate services

slide-19
SLIDE 19

SAC2018

19

Identify candidate services

slide-20
SLIDE 20

SAC2018

20

Identify candidate services

slide-21
SLIDE 21

SAC2018

21

Identify candidate services

slide-22
SLIDE 22

SAC2018

22

Identify candidate services

slide-23
SLIDE 23

SAC2018

23

  • H11: The sum of goals the candidate service needs to achieve

indicates its likelihood of being reused

  • H12: The higher the number of dependencies to a candidate

service, the higher the probability of being implemented

  • H13: Candidate services with a single operation (orphan
  • peration) can be aggregated into another candidate service
slide-24
SLIDE 24

SAC2018

24

Generate service specification

H14: A candidate service is mapped into a SOAML service contract. H14

slide-25
SLIDE 25

SAC2018

25

Generate service specification

H15: KAOS agents are mapped into SOAML participants. H15

slide-26
SLIDE 26

SAC2018

  • Industrial online auction system, from a Brazilian

gas station chain fidelity program

26

Evaluation

slide-27
SLIDE 27

SAC2018

  • 11 candidate services identified
  • After analysis, 8 services to be designed
  • Heuristics to consolidate candidate services have

been valuable, but further research is needed to decrease the subjectivity of the analysis

  • A SOAML specification was generated based on the

8 identified services

27

Results

slide-28
SLIDE 28

SAC2018

Conclusion

28

  • KAOS4Services is a systematic approach to modeling SOA

applications using goal-models

  • KAOS4Services offers a set of heuristics to identify

candidate services from KAOS

  • KAOS4Services applied to a case study based on a real-

project of an on-line auction system, guiding the identification of a set of SOA services

  • Current and future work includes tool support using DSL

techniques and exploring the satisfaction of NFRs at the architectural level

slide-29
SLIDE 29

SAC2018

Authors: Eric Souza and Ana Moreira

er.souza@campus.fct.unl.pt amm@fct.unl.pt

Presenter: João Araújo

joao.araujo@fct.unl.pt

Abril, 2018

Identifying Services in KAOS Models