Requirements
Specifying Requirements
for 2001 milestone
Functional / Support / Other
Requirements so far largely “functional”
(and also vague / rather poorly specified)
e.g. see status report to the LCRB - March 96
comply to ODMG bindings
support schema evolution
individual databases (files) of 1TB by 2000 Valid?
support “logical databases” of 232 DBs
Whilst these must be revisited, missing
completely are “support” issues...
Support
A release of the product for a new
“platform” must be provided within a delay
of 3(?) months
This would have been more than adequate for
RH 6 - when is a shorter delay really needed?
Acknowledgement of bug reports &
automatic notification of change of state
Problem escalation and on-site support
and so on...
Proposal
Establish two (possibly overlapping)
working groups
To work together with experiments in
(re-)defining functional requirements
To work together with experiments and
representatives from likely RCs to define
support requirements
Work should be finished ~October 2000
to allow a response from candidates (?)
Financial Model
Current model is that all licenses are
acquired centrally - maintenance too
Is this a viable model when large RCs are
involved?
Need local expertise, local support, training, ...
Why should e.g. Objy be handled
differently from e.g. HPSS?
Or vice-versa
How do we interact with Hoffmann review?