|
Size: 837
Comment:
|
Size: 3742
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Developer Evaluation == | = Developer Evaluation = |
| Line 3: | Line 3: |
| In February 2006 we asked the developers from the BRIDGES and DyVOSE projects to answer a few brief questions. Contact details confirmed at http://www.nesc.ac.uk/nesc/team.html with biographies. | In February 2006 we asked the developers from the BRIDGES and DyVOSE projects to answer a few brief questions. Contact details confirmed at http://www.nesc.ac.uk/nesc/team.html with biographies. We asked the developers to considering specifically the Shibbolizing of the Bridges web portal and DyVOSE work, and all the myriad of steps which had to be completed to make this work (PERMIS, whatever), and asked them to please identify for us: 1. what did you find difficult? 1. what makes Shibboleth a good solution for accessing a service like Bridges or the DyVOSE data? 1. what issues can you see in a real-world production of this with 100s of users, maybe a commercial data provider, issues for the future etc.? 1. what scalability issues can you identify? 1. how could the access control you've implemented be subverted by e.g. a bad person, or by an expert trying to get round the system for their own convenience, or by a careless user? |
| Line 5: | Line 11: |
| We used the "naively"-formed scenario: | To spark some real-world flavour we used the "naively"-formed scenario: |
| Line 14: | Line 21: |
| === Responses Received === | = Responses Received = |
| Line 25: | Line 32: |
| === | = Results = ||'''Question''' || '''Developer''' || '''Answer''' || ||<-2 :> '''1. what did you find difficult?''' || || || || ||First draft evaluation of objectives || || ||Fri 7 April || || First draft user etc. evaluation || || ||''Mark on hols 6-17 April inclusive'' || ''Take a little time for Humbul'' || ||Tue 18 April ||Policy Evaluation feedback from other projects || || ||Fri 21 April ||Feedback to A on user etc. evaluation || || ||Fri 21 April || ||Feedback to M on Policy Management (and anything else) || || || ||'''All work drafted and ready'''|| ||WB 24 April ||''Full time on ESP-GRID'' ||''Full time on ESP-GRID'' || ||Tue 25 April || || First good draft of 'final' documents || || || || Plan for web site est. and move-over from wiki || ||Mon 1 May ||<-2 :> '''Final doc.s to JISC''' || ||Fri 5 May || Establish web site || || ||Fri 12 May || Finish move-over of text and documents to permanent ESP-GRID web site. || || = Possible extended work plan = ||'''Date''' || '''Mark''' || '''Alun''' || ||Fri 19 May || Dep.t user eval. for e-Science (1st draft) || Dep.t user eval. for e-Science (1st draft) || ||Fri 26 May || Dep.t user eval. for e-Science finished forms and plans || Dep.t user eval. for e-Science finished forms and plans|| ||Mon 29 May || User requirements exercise begins || User requirements exercise begins || ||Fri 9 June || User requirements exercise ends || User requirements exercise ends || ||Mon 19 June || Analysis and write-up begins || Analysis and write-up ends || ||Mon 19 June || Analysis and write-up begins || Analysis and write-up ends || ||Fri 30 June ||<-2 :> '''Final report of requirements doc. to JISC'''|| |
Developer Evaluation
In February 2006 we asked the developers from the BRIDGES and DyVOSE projects to answer a few brief questions. Contact details confirmed at http://www.nesc.ac.uk/nesc/team.html with biographies. We asked the developers to considering specifically the Shibbolizing of the Bridges web portal and DyVOSE work, and all the myriad of steps which had to be completed to make this work (PERMIS, whatever), and asked them to please identify for us:
- what did you find difficult?
- what makes Shibboleth a good solution for accessing a service like Bridges or the DyVOSE data?
- what issues can you see in a real-world production of this with 100s of users, maybe a commercial data provider, issues for the future etc.?
- what scalability issues can you identify?
- how could the access control you've implemented be subverted by e.g. a bad person, or by an expert trying to get round the system for their own
convenience, or by a careless user?
To spark some real-world flavour we used the "naively"-formed scenario:
To the developer: Scenario: Please imagine you've by chance met a manager of a faculty resource in the corridor, and he/she knows of your experience and naively thinks you're the person who can just Shibb their target - "This afternoon, if you've time?"
Responses Received
We are extremely grateful to the following for responding so promptly to our scenario:
- Oluwafemi Ajayi
Micha Bayer (ROS: Grid/BLAST person and portlets, globus)
- Jipu Jiang
- Anthony Stell
- John Watt
The results can be seen below.
Results
Question |
Developer |
Answer |
|
1. what did you find difficult? |
|
|
|
|
First draft evaluation of objectives |
|
|
Fri 7 April |
|
First draft user etc. evaluation |
|
|
Mark on hols 6-17 April inclusive |
Take a little time for Humbul |
|
Tue 18 April |
Policy Evaluation feedback from other projects |
|
|
Fri 21 April |
Feedback to A on user etc. evaluation |
|
|
Fri 21 April |
|
Feedback to M on Policy Management (and anything else) |
|
|
|
All work drafted and ready |
|
WB 24 April |
Full time on ESP-GRID |
Full time on ESP-GRID |
|
Tue 25 April |
|
First good draft of 'final' documents |
|
|
|
Plan for web site est. and move-over from wiki |
|
Mon 1 May |
Final doc.s to JISC |
||
Fri 5 May |
Establish web site |
|
|
Fri 12 May |
Finish move-over of text and documents to permanent ESP-GRID web site. |
|
|
Possible extended work plan
Date |
Mark |
Alun |
Fri 19 May |
Dep.t user eval. for e-Science (1st draft) |
Dep.t user eval. for e-Science (1st draft) |
Fri 26 May |
Dep.t user eval. for e-Science finished forms and plans |
Dep.t user eval. for e-Science finished forms and plans |
Mon 29 May |
User requirements exercise begins |
User requirements exercise begins |
Fri 9 June |
User requirements exercise ends |
User requirements exercise ends |
Mon 19 June |
Analysis and write-up begins |
Analysis and write-up ends |
Mon 19 June |
Analysis and write-up begins |
Analysis and write-up ends |
Fri 30 June |
Final report of requirements doc. to JISC |
|