[354] in Athena_Backup_System
Notes 7 Nov 96
daemon@ATHENA.MIT.EDU (Bill Cattey On the Road)
Thu Nov 7 18:36:39 1996
Date: Thu, 07 Nov 96 18:32:41 EST
From: wdc@MIT.EDU (Bill Cattey On the Road)
To: athena-backup@MIT.EDU
Next meeting: No meeting next week because both Bill and Miki are out.
Next meeting is in two weeks, when Miki will be back.
Status Report:
Restore Server partition from multiple tapes testing is in progress.
Large Cell test dump of entire dev cell has completed successfully.
Diane has fixed most of the problems reported.
Mark has drafted the check list of things to test.
He will put it online and circulate it soon.
Miki circulated a new example page of her document.
She has 70 pages written.
----
What viewpoint should we take when we review Miki's Functional Spec?
That it matches the design?
That it matches the code?
That it is a well written document?
We should match up Requirements, Design, AND Functional Spec.
The we go back and confirm that the Functional Spec Matches the code,
and confirm that the code follows coding standards.
----
We should make sure that the User Interface really is meeting Ted's
requirements.
There is the question of whether or not there will be things in the
database that ABS users will want to change inside Oracle directly
rather than through an ABS application.
The consistency and robustness of the database really requires that
people who are going to modify the database directly should be trained
in Oracle, and understanding of the database schema to a DBA level of
understanding.
It is important to create the proper ABS User Interface applications to
take control of the relevant parts of the database so that the ABS users
can get the job done without requiring intervention of a DBA.
It was decided to make appropriate mention of these issues in our
various written docments, with special emphasis on being careful to say
the right thing in the ABS Administration Guide.
