[98] in Tooltime
Scopus Status Report 5/10/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri May 10 14:04:52 1996
Date: Fri, 10 May 1996 14:05:46 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Cc: pakulat@MIT.EDU, endriga@MIT.EDU, jwl@MIT.EDU, tarnett@MIT.EDU
Scopus Implementation
Date: May 10,1996
Working On Milestone:
- Requirements phase scheduled for nine days, and scheduled to be complete by
Tuesday, May 10th. This includes Prototype and Functional Specification.
- Project has slipped three days as compared to original project plan.
Project plan had been revised and functional specification sign-off
is now scheduled for May 16.
Accomplishments:
- Completed and achieved sign-off for data entry and lookup screens
- Completed load of demo data
- Completed meeting with database group to review outstanding issues
- Corrected SQL*Net problem on database machine (last week status issue)
- Completed initial assessment of data risks (last week status issue)
- Began functional specification
- Began initial conversation with data warehouse on issues
- Began investigation into Windows client deployment
Goals:
- Review rough first draft of functional specification, define process
to give feedback, produce final version on May 16.
- Complete first draft of design specification on May 17.
- Install metadata tables to facilitate client startup
- Complete Windows client deployment installation
- Setup accounts for tooltime
- Review first draft storybook, scope statement for new business document
Issues:
- Scopus QA people working on Macintosh issues with SQL*Net 2.1
certification, missing VMNU object, slow performance (escalated issue
on May 9th).
Concerns:
- Total consulting days charged is 9 days. Long hours were put in this
week resulting in 6 days of effort. If this continues, we will exceed
our consulting contract earlier than expected.
- Progress on obtaining specifications for new production machine is moving
forward, but behind schedule. June 1 appears to be critical date to
obtain machine for prepping and testing.
- Learned that data privacy principles address archival of data, which
applies to log information. We need to evaluate impact.
Learning's:
- It's difficult to move away from an existing process and technology
solution, especially when effort has been applied to make the system work.
- Reaching consensus on the process and definition of core business
requirements for the first release may have been enhanced with a preliminary
requirements document. This document would have a set of design principles,
generate clarity on process, and separate features into "must-have" and
"nice-to-have". It would generate multiple thresholds for must-have
performance and assess trade-offs related to time and cost.
