An UML profile to design Aspects in AspeCiS approach · 2012. 11. 14. · An UML profile to design...
14
An UML profile to design Aspects in AspeCiS approach Mohamed Amroune 1,2,3 [email protected] Nacer eddine Zarour 1 [email protected] Pierre-Jean Charrel 3 [email protected] Jean Michel Inglebert 3 [email protected] 1 Tebessa University, Algeria & 2 LIRE Laboratory, Constantine, Algeria 3 IRIT Laboratory, Toulouse, France IWAISE’12 10-11 November 2012 Constantine (Algeria) 10/11/2012 1 IWAISE'12
Transcript of An UML profile to design Aspects in AspeCiS approach · 2012. 11. 14. · An UML profile to design...
An UML profile to design Aspects in AspeCiS approach
Mohamed Amroune1,2,3 [email protected] Nacer eddine Zarour1 [email protected] Pierre-Jean Charrel3 [email protected] Jean Michel Inglebert3 [email protected] 1Tebessa University, Algeria & 2LIRE Laboratory, Constantine, Algeria
3IRIT Laboratory, Toulouse, France
IWAISE’12
10-11 November 2012
Constantine (Algeria)
10/11/2012 1 IWAISE'12
Outline l Introduction l An overview of AspeCiS
l The phases of AspeCis § Phase I: Elicitation and analysis of CRs § Phase II: CRs models § Phase III: from models to code
l An UML profile for AspeCiS l Aspects l Pointcuts l Advices
l A motived example l Conclusion
10/11/2012 IWAISE'12
2
Introduction The increased competition
10/11/2012
The changes in customer demands
The communications performance
The Important business conditions
inter-organizational relationships
etc…
obligate Enterprises to migrate to
IWAISE'12 3
Introduction
10/11/2012
Building effective enterprise cooperation is not an easy task
It requires a CIS to support this inter-entreprise cooperation
CIS
our research aims at developing a new approach called AspeCiS, that ensures the effectiveness and efficiency of business cooperation
AspeCiS develops a CIS from existing ISs by using their artifacts such as requirements, and design based on the ASPECT concept
IWAISE'12 4
10/11/2012
An Overview of AspeCiS:
Synopsis of AspeCiS approach IWAISE'12 5
10/11/2012
The main feature of AspeCis is to analyze the new requirements of the system being developed as (early) aspects which are then woven on existing systems (specifically on their visible and accessible parts)
An Overview of AspeCiS In AspeCiS : When a new requirement cannot be achieved directly by the existing systems, there should be a possibility to combine and compose the requirements of set of existing systems in order to fulfill the requirement.
The main objectives of AspeCiS are: (i) to separate (not mixed) in the resulting system, the pre-existing functionalities from the new ones;
(ii) to provide a high degree of functional reuse, which could help to weave (build) again these same functionalities on other pre-existing systems
IWAISE'12 6
Phase I: The Elicitation and Analysis of Cooperative Requirements
Ø Refinement of Cooperative Requirements: decompose CRs into a set of basic requirements. Ø Expression of CRs in terms of ERs/ARs: determine the ERs and ARs involved in the definition of every CR
Ø Selection of the OperatorRequirements:A modification of an ER = the weaving of a new behavior on this ER. This change is provided by the UnaryOperatorRequirement
The Phases of AspeCiS
10/11/2012 IWAISE'12 7
10/11/2012
The second phase of AspeCiS basically entails the modelling of base (ERs or ARs models,aspectual entities (OperatorRequirement models) and the definition of a process for weaving them in order to define CRs models.
The general operational context of the model weaving is depicted in
Phase II: Weaving Models
An UML Profile of Aspects in AspeCiS
The Phases of AspeCiS
IWAISE'12 8
10/11/2012
An UML Profile of Aspects in AspeCiS
An AspectOperatorRequirement as a modular way to implement crosscutting Requirements. in AspeCiS, It is very similar to a class.
The Advices define the AspectOperatorRequirements behavior, (the modifications performed by the aspect). An Advice can be either Advice-AddElt to add an element, Advice-Update to modify an element, or an Advice- DeleteElt to remove an element.
These elements can be attributes, classes or associations.
Constraints allow the system designer to specify both when an Advice is applicable (precondition), and the effect of an Advice execution (postcondition).
IWAISE'12 9
10/11/2012
A motivated example This example illustrates a part of the University Students Management System for the High Graduate School
CIS (H.G.School)
IWAISE'12 10
10/11/2012
At the requirements level of the existing ISs, the student subscription requirement is defined as:
ER1= Every student may have a second subscription in the same university.
CR1= Every student can have a second subscription in the same university
provided that the number of hours of the second specialty does not exceed 50% of the number of hours of the first one.
A motivated example
IWAISE'12 11
10/11/2012
A motivated example At the model level of the existing ISs, the student subscription requirement is defined as:
IWAISE'12
IWAISE'12 12
q Conclusion l We have proposed an approach named AspeCiS to develop a
CIS from existing ISs by using their artifacts such as requirements, and design.
l We presented in this paper a profile for AspeCiS. It allowed
the designer to give response to the following question ”How to design Aspects in AspeCiS”?.
10/11/2012
Conclusion
IWAISE'12 13
An UML profile to design Aspects in AspeCiS approach
Mohamed Amroune [email protected] Nacer eddine Zarour [email protected] Pierre-Jean Charrel [email protected] Jean Michel Inglebert [email protected]
IWAISE’12
10/11/2012
Thank you !
14 IWAISE'12
