• Aucun résultat trouvé

From Aspect-oriented Requirements Models to Aspect-oriented Business Process Design Models

N/A
N/A
Protected

Academic year: 2021

Partager "From Aspect-oriented Requirements Models to Aspect-oriented Business Process Design Models"

Copied!
13
0
0

Texte intégral

Loading

Figure

Figure 1: AoUCM: Root Map – Get Pictures
Figure 4: Concern Interaction Graph
Figure 5: Adore : picasaService Fragment & Associated Composition Directive
Figure 7: Adore : truncate Business Process
+4

Références

Documents relatifs

In this paper the author will provide insight in socialization aspect which can support requirement management process and improve knowledge availability,

The main methods implement the code for finding an implementation of Singleton within a class, to identify constructor and the static method, and to search and remove the invocation

L’archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des

In [1], it is shown how the application of subject-oriented programming con- cepts to the complete software development cycle can help to maintain consis- tency of requirements,

One way to constrain the behavior of a model element, a Class for example is to define Invariant condition on the class, and pre and post conditions on its operations.. These three

Figure 2 KerTheme models for LogIn and Persistence concerns The LogIn KerTheme is testable because the logic encapsulated in the executable classes models and the resulting

Abstract. Software systems should often propose continuous services and can- not easily be stopped. However, in order to meet new requirements from the user or the marketing,

We have presented a process for detecting concern interactions in AO designs ex- pressed in UML (for modeling concern data and behaviour) and WRL (a domain