Améliorer la conception des applications interactives par l'utilisation conjointe du modèle PAC et des patrons de conception

Authors:
Thierry Duval;Jean-Claude Tarby
Affiliations:
IRISA (Siames) UMR, Campus Universitaire de Beaulieu, Rennes Cedex, France;Laboratoire Trigone, Institut CUEEP, Université Lille, Villeneuve d'Ascq Cedex, France
Venue:
IHM '06 Proceedings of the 18th International Conferenceof the Association Francophone d'Interaction Homme-Machine
Year:
2006

Citing 6
Cited 0

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Patterns in Java: A Catalog of Reusable Design Patterns Illustrated with UML

Patterns in Java: A Catalog of Reusable Design Patterns Illustrated with UML
A Unifying Reference Framework for the Development of Plastic User Interfaces

EHCI '01 Proceedings of the 8th IFIP International Conference on Engineering for Human-Computer Interaction
Model Driven Engineering

IFM '02 Proceedings of the Third International Conference on Integrated Formal Methods
Using the PAC-Amodeus Model and Design Patterns to Make Interactive an Existing Object-Oriented Kernel

TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 33)
Utilisation du modèle PAC-Amodeus pour une réutilisation optimale de code dans le développement de plusieurs versions d'un logiciel commercial

IHM 2004 Proceedings of the 16th conference on Association Francophone d'Interaction Homme-Machine

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software architectural models like MVC and PAC are now well known, and can be implemented in many different ways. This is a problem for students when they have to implement these models, because they do not know how to select an appropriate solution. For now several years we have proposed a methodology to facilitate the implementation of the PAC model. This methodology is mainly based on Design Patterns such as « Proxy », « Abstract Factory », and « Singleton ». Thanks to this methodology, the structure of the source code is imposed and ensures an efficient separation between the application kernel and the GUI. Then, students learn to implement this separation efficiently, and they discover also with this separation that the software can evolve more easily: it is easy to change the GUI or the kernel without affecting the other part, and to add interaction possibilities to a non-interactive kernel.