[138] in Tooltime
Scopus Status Report 6/14/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Jun 18 08:30:53 1996
Date: Tue, 18 Jun 1996 08:32:25 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation
Date: June 14,1996
Working On Milestone:
- Beta phase continues with multiple releases, testing, and assessment
of work required to complete this phase. Beta phase completion goal
is last week of June.
- Release 1.0b2 testing to begin week of June 17.
Accomplishments:
- Released 1.0b1 for testing within the tooltime team
- Conducted feedback and assessment of 1.0b1
- Conducted review of development tools for team members
- Began work on 1.0b2, slated for release June 17
- Preparation for 1.0b2 release (software deployment, account setup)
- Identified Filemaker migration issues and began strategy to import
Goals:
- Complete 1.0b2 release and conduct testing
- Asses 1.0b2 testing and prioritize changes for 1.0b3 release
- Complete requisition for production machine
- Complete other items in progress, Win 32 bit Scopus deployment,
Silverrun data model migration, Filemaker migration strategy
Issues:
- Response from Scopus on metadata version control: Appears to be
working as they expected, which is different from the consultant's
expectation. Metadata version control is requires an initiative on
the user to issue a function "generate new metadata". This presents
a scale issue for using metadata, where users would be expected to
know there is a new version of metadata and to take an action.
- Macintosh issue is still open to determine if the response time is
the expected behavior. Scopus issue number: 18100. Issue number
18938 for Macintosh and Metadata problem (does not work at all) and
new issue number 19275 for problem with Child windows not allowing
data entry.
Notes:
- This is the last week the Scopus consultant will be on-site. Please
bring up any issues needing his attention.
- With the consultant leaving, we need to confirm that our
documentation (Functional Spec, Design Spec, loading software, etc.)
is in order. Specifically, we need ensure for customer acceptance
that the Functional Specification meets the delivered product.
- As testing continues, we need to begin focus on training, deployment
and contingency planning.
