[ Index ]
[ Individual Project ]
[ Placement Presentation ]
[ Timetable ]
[ Index ]
[ Research ]
[ Schedule ]
New Challenges for Configuration Management
Last Updated: 1st December 2001
This paper is concerned with the problems of dependencies between shared components. The solution they propose is a configuration management (CM) that can track the versions of various components/libraries that some component uses and produce some sort of alert when something in the DAG is altered.
The usefulness of this paper is limited since I am assuming the software using the library will be known, and the JMX agent keeps track of them already.
Ground covered in previous papers has been repeated here, things such as compatibility:
- Input/Output - The program can read the same data and produce the same data.
- Interface compatibility - What has been previously called binary compatibility.
- Behaviour compatibility - Internal characteristics (performance, resource requirements, etc.) remain the same.
The only type of compatibility I'm concerned with at the moment is binary compatibility. The last type of compatibility they mention is important in real-time systems, but this type of checking is quite different to binary compatibility checking having little in common. I am interested in providing some sort of logic compatibility in the tool, but the more relevant paper is Jonathan Cook's.
Miles Barr <miles@milesbarr.com>
