Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Generative programming: methods, tools, and applications
Generative programming: methods, tools, and applications
Communications of the ACM
Component-based product line engineering with UML
Component-based product line engineering with UML
A UML-based aspect-oriented design notation for AspectJ
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
Towards a standard design language for AOSD
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
Understanding and Using Context
Personal and Ubiquitous Computing
Data & Knowledge Engineering
Proceedings of the 25th International Conference on Software Engineering
UMLAUT: A Framework for Weaving UML-Based Aspect-Oriented Designs
TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 33)
A Conceptual Model for Context-Aware Dynamic Architectures
ICDCSW '03 Proceedings of the 23rd International Conference on Distributed Computing Systems
ICECCS '99 Proceedings of the 5th International Conference on Engineering of Complex Computer Systems
Introducing Microsoft .NET, Third Edition
Introducing Microsoft .NET, Third Edition
Enhancing pervasive Web accessibility with rule-based adaptation strategy
Expert Systems with Applications: An International Journal
Context-driven requirements analysis
ICCSA'07 Proceedings of the 2007 international conference on Computational science and its applications - Volume Part III
Hi-index | 0.00 |
Portable and embedded devices form an increasinglylarge group of computers, often referred to as Ambient Intelligence(AmI). This new variety in computing platformswill cause a corresponding diversity in software/hardwareplatforms and other context factors. Component-based middlewareplatforms offer a uniform environment for software,but they do not take away specific context differences,such as hardware resources, user identity/role andlogical/physical location. Specialised component versionsand/or configurations have to be made for each computingcontext if that computing context is to be used to its full extent.This is because the fine differences between componentversions cannot be separated into finer components withthe current component models. Aspect-oriented programmingand generative programming technologies can be usedto provide the fine-grained modularity that is necessary. Inaddition, the diversity of component-based platforms themselvesform an extra reason for different component versions.We propose using a context-driven framework for thedevelopment of AmI components, which is based upon agradual refinement mechanism. This refinement mechanismcan cope with the course-grained differences between componentmodels as well as the fine-grained differences betweencomputing configurations.