![](bg4.png)
AGL
Allows to seize a UML
diagram
Patterns Engineer
XMI
Tool
created
integrate
merge
AGL
Allows to modify a UML diagram
Applications Engineer
search
XMI
credits
duplicated
XMI
credits
duplicated
imitate
YES
Information
System
Class
Diagram
Class
Diagram
XMI
XMI
AGAP
generate
Pattern
Pattern
Class
Diagram
Class
Diagram
Xmi
Xmi
AGAP
generate
XMI
XMI
Tool
created
AGAP Catalog
Validated
pattern
Figure 7: AGAP imitation and integration processes
Application : The shows the imitation screen of
«Adapter pattern ».
Figure 8 : Imitation screen of «Adapter Pattern»
3 CONCLUSION
This article presented AGAP, a development
environment suited to two types of actors,
applications engineers and patterns engineers.
AGAP addresses therefore two types of processes:
- a process by reuse allowing the AE to define
information systems by selecting, applying and
integrating patterns applications,
- a process for reuse allowing the PE to define and to
organize patterns systems.
AGAP evolved from a prototype model to a
functional product and was used wright now to
specify two formalisms: P-Sigma (Conte, 2001) and
Gamma as well as Gamma patterns system (Gamma,
1995) and two patterns systems written in P-Sigma.
These patterns systems result from applied
researches on two projects in collaboration with
industrial companies. The first one focuses on the
engineering of Product Information Systems (PIS) of
industrial enterprises (Gzara, 2000) and was
developed in collaboration with Schneider Electric
company (project CNRS PROSPER-POSEIDON).
The second patterns system concerns the
specification of Symphony, a development process
based on business components proposed by the
UMANIS company.
From these first validated results, other research
works were initiated to facilitate reuse in
information systems engineering field and to
guaranty a traceability between design choices and
software products resulting from the design.
REFERENCES
Ambler, S.W., 1998. Process Patterns building Large
Scale Systems using Object technology, SIGS Books,
Cambridge University Press.
Borne, I., Revault, N., 1999. Comparaison d’outils de mise
en oeuvre de design patterns, Object-oriented
Patterns, Vol5, num2.
d
f
c
e
Conte. A, Giraudin J .P., Hassine I., Rieu D. 2001, Un
environnement et un formalisme pour la définition, la
gestion et l’application de patrons, Revue ISI vol 6
n°2.
Fowler, M., 1997. Analysis Patterns – Reusable Object
Models, Addison-Wesley.
Gamma, E., Helm, R., Johnson, R.E., Vlissides, J., 1995.
Design patterns: Elements of Reusable Object-
Oriented Software, Addison-Wesley,
Gzara L., Rieu D. 2000. Tollenaere M., Pattern Approach
To Product Information Systems Engineering,
Requirements Engineering Journal, Editors: Peri
Loucopoulos & Colin Potts, Springer- Verlag,
London.
Hassine I., Rieu D., Bounaas F., Seghrnouchni O. ,
« Symphony : Un modèle conceptuel de composants
métier» Revue ISI, volume 7, numéro 4, Hermès,
2002.
Johnson, R.E., 1992. Documenting Frameworks using
Patterns, OOPSLA'92.
Maiden, N., Sutcliffe, A., Taylor, C., Till, D., 1994. A set
of formal problem abstractions for reuse during
requirements engineering, ISI, Hermes, vol. 2, n° 6.
Meijers M., 1996. Tools Support for Object-Oriented
Design Patterns, Master's Thesis, Utrecht University.
Meijler, S. Demeyer, R. Engel, 1997. Making design
patterns explicit in Face, ESEC/FSE 97.
Rieu, D., Giraudin, J.P., Conte A., 2002. Pattern-Based
Environments for Information Systems Development,
The Sciences of Design, Lyon, France.
AN INFORMATION SYSTEM DEVELOPMENT TOOL BASED ON PATTERN REUSE
551