You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Time

Session 1

Session 2

Notes

 WEDNESDAY

             ITANA                                

N/A

 

THURSDAY

Advanced CAMP


 

7:30-8:30

Breakfast

 

 

8:30-9:00

Introductions and Goals of the Workshop

 

Provide set of issues to report on
per Chas examples below

9:00-10:00

Bamboo/SEASR: New Examples

 

Expose privacy and policy issues that loosely coupled environments create.

10:00-10:15

Break

 

 

10:15-11:30

Open Discussion: Projects and user experiences.
How closely do they match your experience?

 

 

11:30-1:00

Lunch

 

 

1:00-2:15

Kuali/OGSA/Fedora Projects and Users
Compare and contrast three projects and user stories

 

 

2:15-2:30

Break

 

 

2:30-3:45

Discussion Groups: Services, Data Models, Governance
Groups will consider each of these in turn given the examples so far and develop a set of requirements for each.

 

Orchestration/Information discovery: How do you go about finding information of interest and cross linking your results? Introduce Tool from caBIG??? But where does infrastructure stop and governance begin? Or is it a design pattern instead of an infrastructure component?

3:45-4:00

Break

 

 

4:00-5:00

Panel: Are there lessons learned from ESB
that can be applied to loosely coupled
environments? To project centric environments?

 

How can campus architects learn about this? How do we get project and campus folks to talk?
How can we diagnose this complexity?

5:30-7:00

Reception

(Available until 6pm)

 

 

 

 

 

 FRIDAY

 

N/A

 

7:30-8:30

Breakfast

N/A

 

8:30-9:30

Privacy and Policy Panel: Expose privacy and policy issues that loosely coupled environments create.

Blakely, EGEE, Lori Crantor (CMU),

N/A

 

9:30-10:30

 

N/A

 

10:30-11:00

Break

N/A

 

11:00-Noon

 

N/A

 

Issues to Compare and Contrast

- vision of project
- motivation (business and technical)
- brief narrative
- initial timeline
- how they began to define requirements
        - business/operational
        - technical
- defining governance model
- describe their technology
        - architecture
        - why they made specific decisions
- status thus far
        - progress to date (real timeline)
        - problems
        - risks
                - core competencies of staff?
                        - development/operational
                - continued funding?
                - technology?
                        - development
                        - operations
                - governance?
                - etc?

  • No labels