[Esip-preserve] Upcoming meeting planning
Bruce Barkstrom
brbarkstrom at gmail.com
Tue Apr 5 17:03:53 EDT 2011
Tried to find the six use case suggestions. No luck.
As far as the generic categories below, I don't know what the "Key
Systems Involved"
means.
Personally, I think we're going to have to get a lot more detailed
than we've been
in the past. Indeed, I think we need to get all the way down to a
fairly complete
UML model that could lead to a simulation of the scenario.
Bruce B.
On Tue, Apr 5, 2011 at 2:18 PM, Hua, Hook (388C) <hook.hua at jpl.nasa.gov> wrote:
>
> ________________________________________
>> From: esip-preserve-bounces at lists.esipfed.org [esip-preserve-bounces at lists.esipfed.org] On Behalf Of Curt Tilmes [Curt.Tilmes at nasa.gov]
>> Sent: Tuesday, April 05, 2011 9:29 AM
>> To: ESIP Preservation cluster
>> Subject: [Esip-preserve] Upcoming meeting planning
>
>> I'm thinking between now and the meeting, we try to flesh out some
>> of Hook's Use Cases here:
>>
>> http://wiki.esipfed.org/index.php/Preservation_Ontology#Use_Cases
>>
>> Anyone interested in Preservation Ontology Use Cases, select "watch"
>> on that page so you'll get notified of changes. It would be great if
>> each such person could contribute 1 Use Case to build on -- doesn't
>> have to be complete/perfect at this point, just brainstorming. We can
>> refine/combine/etc. to get a good set to work from later. Also keep
>> in mind Frank Lindsey's advice from the Winter Meeting -- it's more
>> valuable to take one use case through to fruition than to spend a lot
>> of time trying to get a set of use cases perfect up front.
>
>
> As a starting point, I just updated the wiki page with 6 use case ideas. Some are fairly high-level and could be broken up into more specifics. We would still need for each use case something like: (borrowing from the Decadal Survey Mission Use Cases)
> - Goal
> - Summary of the Scenario
> - Users
> - Key Systems Involved
> - Notes
> - Technology Challenges
> Do we want to get that detailed?
>
> Should we also separate out the provenance use cases and context use cases?
> If it gets bigger, we should probably move the section out to it's own page(s).
>
> I also think working out an end-to-end use case thread is a good idea. Maybe after we lay down some high-level representative set, we can choose a use case with high priority to work out end-to-end first.
>
>
>> From the meeting feedback, we have two requests -- 1) Fewer powerpoint
>> talks and more informal discussion and 2) Less informal discussion and
>> more structured talks.
>
> Sounds like something a doodle poll can quickly answer.
>
>
> --Hook
> _______________________________________________
> Esip-preserve mailing list
> Esip-preserve at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-preserve
>
More information about the Esip-preserve
mailing list