Abbrevation
ICAC
City
Chicago
Country
United States
Deadline Paper
Start Date
End Date
Abstract

To deal with the increasing complexity of large&#8211;scale computer systems, computers must learn to manage themselves, in accordance with high&#8211;level guidance from humans and a vision that has been referred to as autonomic computing&#046; Meeting the grand challenges of autonomic computing requires scientific and technological advances in a wide variety of fields, as well as new software and system architectures that support the effective integration of the constituent technologies&#046; <SPAN class=Text>The purpose of the 5th International Conference on Autonomic Computing (ICAC&#8211;08) is to bring together researchers and practitioners to address all aspects of self&#8211;management in computing systems&#046; In doing so, we will continue to develop and nurture a growing community that can work together to realize the vision of scalable self&#8211;managing systems&#046; The conference builds on previous highly influential meetings in New York, Seattle, Dublin and Jacksonville&#046;</SPAN><B>Keywords:</B> <LI><SPAN class=Text><STRONG>Autonomic computing systems</STRONG> that exhibit autonomic characteristics, such as self&#8211;configuration, self&#8211;optimization, self&#8211;healing, self&#8211;protection, and self&#8211;governance&#046; </SPAN> <LI><SPAN class=Text><STRONG>Fundamental scientific aspects of self&#8211;managing systems:</STRONG> understanding, controlling, and/or exploiting emergent behavior; methods to automate manual operations; implementation of new device, network and system functionality; behavior orchestration&#046; </SPAN> <LI><SPAN class=Text><STRONG>Software architectures</STRONG> for self&#8211;managing systems, based on appropriate supporting technologies such as Grid Services, agent&#8211;based systems, Web Services, model&#8211;based systems or novel paradigms such as biological, economic or social computing&#046; </SPAN> <LI><SPAN class=Text><STRONG>System&#8211;level technologies, middleware or services</STRONG> that entail interactions among two or more elements of self&#8211;managing components, devices and systems&#046; </SPAN> <LI><SPAN class=Text><STRONG>Toolkits, environments, models, languages, runtime and compiler technologies</STRONG> for building self&#8211;managing components, systems and applications&#046; </SPAN> <LI><SPAN class=Text><STRONG>Self&#8211;managing components</STRONG>, such as server, storage, network, mobile device, data center or specific application elements&#046; Emphasis should be placed on techniques or lessons that may generalized to other components&#046; </SPAN> <LI><SPAN class=Text><STRONG>Interfaces to autonomic systems</STRONG>, including user interfaces, mechanisms for controlling behavior, and techniques for defining, distributing, and understanding policies&#046; </SPAN> <LI><SPAN class=Text><STRONG>Applications of autonomic systems</STRONG> with respect to future Internet and other next generation architectures&#046; </SPAN> <LI><SPAN class=Text><STRONG>Experiences with autonomic systems or component prototypes</STRONG>: measurements, evaluations, or analyses of system behavior, user studies, or experiences with large&#8211;scale deployments of self&#8211; managing systems or applications&#046; </SPAN> <LI><SPAN class=Text><STRONG>General management topics</STRONG>, such as minimization of power/energy consumption, modeling of communications entities (e&#046;g&#046;, SLAs), negotiation/conversation support, behavior enforcement, tie in with IT governance, and legacy system support&#046; </SPAN></LI>