Tomorrow's meeting

["Timothy Grapes" <tgrapes@evotecinc.com>]

Gentlemen,

 

I have to be in a meeting in DC at 9:00 AM tomorrow, but should make it back
to the office in time for our meeting.  I will dial in via cell if necessary
for starters.  Just a heads-up in case...

 

I believe our plan was to pull up the first report requirement and begin
this process:

 

                                                  1.1.1       Review
reporting requirements (ICS etc.) to determine sequence of these reports,
what decisions they support, and what info is required to support those
decisions.  Approach is to define the constraint schemas first, and boil
them up / vet the overall reference model.

                                                  1.1.2       Process:  Go
through each ICS report with it's purpose, overview and definitions, and
determine:

 1.1.2.1              Materials Needed:  ICS reports pdf, SitRep ERM for
reference, possibly the SitRep Requirements Data Dictionary.

 1.1.2.2              Develop for each report:

 1.1.2.2.1         Where it fits in the sequence

 1.1.2.2.2         What decisions are supported

 1.1.2.2.3         What report info supports each decision

 1.1.2.2.4         What questions we have for practitioners (cannot have
them join the call due to IPR issues.  Will vet against our contacts.  .

SUBSEQUENT STEPS:

 1.2             Next, step back to the Requirements and ERM - start
stepping through the ERM IN DETAIL, referring to the element definitions
(data dictionary) to validate our detailed understanding, fit in the ERM,
structure and associations at the constraint schema level and then the
common overall reference schema.

 1.3             Review issues list

 1.4             Specification Writing

 

 

Thanks,

Tim Grapes

Evotec

<<attachment: winmail.dat>>