27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 6. Steps S1, S2, S3, S4 and S5 of our approach considering the event “CAG2 - Declarant submits declaration”<br />

Both monitorable and operationalizations tasks should be<br />

linked with system services. Operational services have the<br />

objective of return the system to an optimal state in an<br />

autonomic manner. For example, the “Receive CAGED File”<br />

activity is linked to “Service5”<br />

D. Step S4 – Define Contextualization<br />

Both contextualization and NFR are i mportant factors<br />

to be cons idered as they can guide the execution of<br />

operational tasks that must provide autonomic adaptations<br />

in the system in order to return the equilibrium in face of<br />

incoming perturbations [16]. Hence in this step we define:<br />

(i) Variation Point; (ii) V ariants; (iii) Context; and (iv)<br />

NFR attributes values. The 3 contexts (C1, C2 and C3)<br />

present in Figure 6 (box S4 are defined in TABLE<br />

II.<br />

In this activity we state metrics to be monitored, i.e. we<br />

delimit the environment context that influences the choice of<br />

the system adaptation. In this sense, given that in our running<br />

CAGED there is a deadline for declaration submission, it is<br />

important to measure the daily reception. As observed in<br />

Figure 7, the reception rate peaks during the first seven days<br />

of the month. This trend has to be considered in case of a<br />

correct adaptation.<br />

TABLE II.<br />

Task<br />

Receive<br />

CAGED<br />

File<br />

CONTEXTUALIZATION OF AUTONOMIC BUSINESS PROCESS<br />

Variation<br />

Point<br />

Response<br />

Time<br />

Deviation<br />

Contextualization<br />

Variants Context NFR<br />

Increase<br />

Reception<br />

Rate<br />

Decrease<br />

Reception<br />

Rate<br />

Deviation<br />

Reception<br />

Rate<br />

C1: ReceptionTrendIsOK=<br />

true and<br />

LastThreeCycleIncreasing=<br />

true<br />

C2:ReceptionTrendIsOK=<br />

true and<br />

LastThreeCycleDecreasing=<br />

true<br />

C3:ReceptionTrendIsOK=<br />

false and<br />

LastThreeCycleIncreasing=<br />

true<br />

Response<br />

Time >=<br />

220ms<br />

Response<br />

Time =<br />

220ms<br />

E. Step S5 – Define Service QoS<br />

All defined and linked services, represented as ServiceID<br />

in Figure 6, box S5, must be instrumented according to SLO.<br />

The definition of QoS is based on NFR attributes and<br />

represents the characteristics that must be guaranteed by each<br />

monitorable business activity. Considering the four send<br />

activities and one reception activity of our running example,<br />

the system must provide a Response Time less than 220ms to<br />

each one.<br />

535

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!