OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: Tomorrow's meeting

Works for me, Tim,

Hi Everyone,

If you point your browsers to http:dimdim.com, then click on "Join 
Meeting" and type in "rexbroo" (not the quotes), you'll have a view of 
my desktop to which we can refer as we go through the steps since I plan 
to add the specific elements from the ERM to class diagrams of each 
report as we go through them. I'll change the name of the Enterprise 
Architect file to EDXL-SR-Reports-01.eap and continue uploading the 
latest version to the documents page after each session.


Timothy Grapes wrote:
> 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:
> Materials Needed: ICS reports pdf, SitRep ERM for reference, 
> possibly the SitRep Requirements Data Dictionary.
> Develop for each report:
> Where it fits in the sequence
> What decisions are supported
> What report info supports each decision
> What questions we have for practitioners (cannot have them 
> join the call due to IPR issues. Will vet against our contacts. .
> 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/*

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]