Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Quantifying the energy consumption of a pocket computer and a Java virtual machine
Proceedings of the 2000 ACM SIGMETRICS international conference on Measurement and modeling of computer systems
The Case for Higher-Level Power Management
HOTOS '99 Proceedings of the The Seventh Workshop on Hot Topics in Operating Systems
Modeling Resources in a UML-Based Simulative Environment
AICCSA '01 Proceedings of the ACS/IEEE International Conference on Computer Systems and Applications
Software Engineering for Self-Adaptive Systems
Software Engineering for Self-Adaptive Systems
REMES: A Resource Model for Embedded Systems
ICECCS '09 Proceedings of the 2009 14th IEEE International Conference on Engineering of Complex Computer Systems
A multi-model framework to implement self-managing control systems for QoS management
Proceedings of the 6th International Symposium on Software Engineering for Adaptive and Self-Managing Systems
TOP: Tail Optimization Protocol For Cellular Radio Resource Allocation
ICNP '10 Proceedings of the The 18th IEEE International Conference on Network Protocols
Deriving minimal models for resource utilization
Proceedings of the 2013 workshop on Green in/by software engineering
A design method for modular energy-aware software
Proceedings of the 28th Annual ACM Symposium on Applied Computing
Hi-index | 0.00 |
Resource optimization is an increasingly important requirement in the design and implementation of software systems. It is applied to improve both environmental sustainability and usability of resource-constrained devices. This paper claims that to achieve more modular resource-aware applications, the resource utilization of components must explicitly be modeled. Due to shortcomings of existing modeling languages, we propose a notation for the resource consumption of components and we illustrate the suitability of this notation by means of two real-world examples. We observe that explicitly modeling resource consumption has as result that resource consumption information is scattered across and tangled with the functional services of components.