Configuration Management Goals Investigate problems of using multiple

Configuration Management – Goals • Investigate problems of using multiple complex platforms with many possible configurations • Investigate established approaches to the above problems • Establish methods of increasing the efficiency of the use of the project platforms – Cut down on system downtime ? (metric? ) – Better knowledge about the platforms – Increased ability to develop components in parallel

Configuration Management – Status • Several methods for ensuring platform stability – Unit tests for components to pass before being tested on a platform – Maintain a baseline configuration that changes only after components pass basic performance tests on the platform • Some Methods for tracking configuration – Distributed but redundant knowledge of system components – Track component versions/states when used, track deviations from baseline – Automate setups for operations and always start from base? • Things to get from other teams – Simulation environment that can import or fake data, noise, faults – Version oriented development?

Test Management – Goals • Investigate how to deal with testing a complex and fast changing system • Investigate how to deal with test failures/faults • Establish methods of increasing the efficiency of testing • Metrics?

Test Management - Status • Have come up with a lot of situations to be solved – – What to do if the baseline shows problems in testing? What to do when code fails a test? What’s the best way to deal with/track bugs? How do we develop a test-bed that makes testing efficient? – How close does a simulator/test-bed need to be to the real world? – How do we run tests to decrease sitting-around time? – How do we document/enforce test procedures? • We need from other teams - ?