[92] in Tooltime
Scopus Implementation Meeting Notes 5/8/96
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Wed May 8 15:58:45 1996
Date: Wed, 8 May 1996 15:59:31 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Cc: pakulat@MIT.EDU, jwl@MIT.EDU, endriga@MIT.EDU, tarnett@MIT.EDU
Another day, more notes !!! Please read next steps for upcoming activities.
Scopus Implementation Meeting May 8, 1996
Attending: Sousa, , Larrabee, Pakulat, Lee, Wade, Arnett, Fermann, Endriga
Agenda
1. Administrative, status updates
2. Walkthrough of screens
3. Next steps and action items
1. Administrative, status updates
- Talked to integration team members. Issues with access to warehouse
data appear to be resolved. No additional action will be taken, it
should be understood that data is for Institute purposes only. Misuse
by staff (including students) can result is some action.
2. Walkthrough of screens
Specific attention was paid to the process of receiving a call, and either
entering a new log or annotating an existing log.
( Yikes, do you really want to know the result of the walkthrough? Well,
your going to have to wait until I sift through all those notes ).
3. Next steps and action items:
- Next Meeting - Thursday 9:00 am 11-124A
(short meeting expected)
Agenda - Sign-off on the screens reviewed this week. Terry to
have revised screens from today's meeting.
Sign-off implies a solid understanding of how the screens
will be evaluated for the Functional Specification. The
Screens represent at least the core business needed for
a first release.
It is understood that modifications (field names, searching
changes, new fields) may occur after the initial release as
the product is refined.
- Peter to have first rough draft of a storybook (refers to the process
of how consultants (via multiple roles) communicate to a customer,
questions asked, process to locate a log, enhance log history,
create a new record, review existing queue's, etc. This type of
information is more process oriented and should compliment the
functional specification.
- Peter to deliver extended data definition by Thursday ( May 9 )
afternoon. This includes field attribute definition, use as a
core business, and if the field is read-only, mandatory or visible.
- Next week:
- Need to prioritize the functions in the specification as we plan
the implementation functions. Either a binary rating, decide
release 1.0 or not. Or rate on high (must have for release),
medium (need for release after 1.0), low (would like to have
someday).
- Terry to deliver draft functional specification by Tuesday 5/14.
*** Meeting is at 1:00 pm ****
- Meet on Wednesday 5/15 to give comments.
- Meet on Thursday 5/16 to sign-off on functionality
- Wade/Terry and others? to meet on Thursday and Friday to plan
schedule for implementation.
