High-level Models of Software-management Interactions and Tasks for Gradual Transition Towards Autonomic Computing (original) (raw)
Related papers
High-Level Modeling of Software-Management Interactions and Tasks for Autonomic Computing
For making software systems autonomic, it is important to understand,and model software-management tasks. Each such task contains typically many,interactions between,the administrator,and the software system. We propose,to model,software-management interactions and tasks in the form of a discourse between,the adminis- trator and the software system. Such discourse models,are based on insights from theories of human,communication. This should make,them “natural” for humans,to define and understand.,While it may,be obvious,that such discourse models cover software-management interactions, we found that they may,also represent major parts of the related tasks. Our well-defined models,of interactions and,tasks as well as their operationalization should facilitate their execution and automation.
2007
While management of today's software systems is usually performed by humans using some user interface (UI), autonomic systems would be self-managed. They would typically consist of a managed element, which provides actual system functionality, and an autonomic manager performing system management. However, truly self-managed systems are hard to achieve and not (yet) in wide-spread use. During the transition towards autonomic software systems it is more realistic to manage a large and complex software system partly by humans and partly by an autonomic manager. For facilitating this approach, the communication between the managed element and human administrators on the one hand and the communication between the managed element and the autonomic manager on the other, should be unified and specified on the same semantic level. However, there is no scientific basis for such a unified communication approach.
An architecture for gradual transition towards self-managed software systems
ACM SIGSOFT Software Engineering Notes, 2006
While management of today's software systems is usually performed by humans using some user interface (UI), autonomic systems would be self-managed.Our research addresses the research problem of gradual transition towards self-managed software systems and proposes and investigates a particular architecture for its solution. In particular, we propose unified communication between a system to be managed and its (human or autonomic) manager. Such communication is specified using our high-level discourse metamodel based on insights from theories of human communication. This should make such communication easier to design and understand by humans.
Autonomic Software Systems: Developing for Self-Managing Legacy Systems
2014
Modern software systems have grown in complexity and expense, even while the cost for supporting hardware has decreased over time. Humans have a lot to do with why software is expensive, and they contribute to its cost in at least three significant areas: the maintenance and evolution of existing software, the run-time monitoring and configuration of executing software, and errors made during data entry and system configuration tasks. Software engineers seek to mitigate these costs by minimizing or removing expensive human participation in these areas where possible by adopting software and hardware approaches aimed at doing so. In this paper, we describe a commercial software engineering project where code reuse, service-oriented architecture, and self-* autonomic approaches were employed to extend the legacy enterprise system of a multi-channel vendor of musical equipment. In adopting these approaches, the developers were able to produce a highlyautomated extension to an existing system that increased the number of orders places by customers, extending the business value of that system.
Autonomies in a Software Process Landscape
2002
Until now autonomy properties have been mainly discussed in the research area of database management systems, agents and robotic systems. We address these properties to software process models, and distinguish between data autonomy, operation autonomy and communication autonomy. In this paper we develop a classification framework of different granularity levels and different degrees for each of the autonomy types. We analyze the autonomy of an example software process landscape modelled with a Petri based net notation. The example process landscape represents software process models for the development of multimedia applications. Detailed analyses of the example check the classification framework, and consider the impact of autonomy properties on software processes and on software process management. " are elements of this set which are completely autonomous. This fact approves the accepted opinion that though these activities have to deal with concrete data, the way they work is highly creative and does not follow rules defined by others and the sequence of their definition resp. analysis steps cannot be predicted in advance.
Toward a new landscape of systems management in an autonomic computing environment
2003
Abstract In this paper we present IBM Tivoli Monitoring, a systems management application that displays autonomic behavior at run time, and we focus on extending it in order to encompass the design and the deployment phases of the product life cycle. We review the resource model concept, illustrate it with an example, and discuss its role throughout the product life cycle.