[ogsa-wg] use case template
Andre Merzky
andre at merzky.net
Mon Mar 10 19:03:57 CDT 2008
Hi,
attached ios the SAGA use case template, as asked for in
todays phone call.
Please note that we (i.e. the SAGA folx) would draft a
simplier use case template iff we'd do that again, because,
in hindsight, we asked too many questions which were not
related to the API. OTOH, for your purpose, the question
may just be right... ;-)
Best, Andre.
--
One week of hacking easily saves half an hour of thinking.
Henri Bal
-------------- next part --------------
This is a template for providing use cases to the GGF "Simple
API for Grid Applications" research group (SAGA-RG); these use
cases will be used to determine required functionality which
must be supported by the resulting SAGA-API specification, and
to provide guidance to implementors of the API. We have kept
these two features in mind while creating this template.
All sections apart from use case name and the description of
the use case itself (3) may be considered optional.
If the use case is complex, we would appreciate efforts to
split into sub-scenarios where possible, for example in the
use case description (3) and in the descriptions of customers
(4) and resources (5).
In each section we have tried to provide suggestions of
questions to try to answer.
Please send the use cases to <saga-rg at ggf.org>, or if you want
to submit anonymously for any reason, send directly to one of
the group chairs or secretaries (see
http://www.gridforge.org/).
-------------- next part --------------
Name of use case: .............................
Contact (name and address): .............................
Authors (if different form contact) .............................
1. General Information:
-----------------------
This section consists of check-boxes to provide some context in
which to evaluate the use case.
1.1 Which best describes your organisation:
Industry [ ]
Academic [ ]
Other [ ]
Please specify: ................................
1.2 Application area:
Astronomy [ ]
Particle physics [ ]
Bio-informatics [ ]
Environmental Sc. [ ]
Image analysis [ ]
Other [ ]
Please specify: ................................
1.3 Which of the following apply to or best describe this use
case Multiple selections are possible, please prioritize
with numbers from 1 (low) to 5 (high):
Database [ ]
Remote steering [ ]
Visualization [ ]
Security [ ]
Resource discovery [ ]
Resource scheduling [ ]
Workflow [ ]
Data movement [ ]
High Throughput Computing [ ]
High Performance Computing [ ]
Other [ ]
Please specify: ................................
1.4 Are you an:
Application user [ ]
Application developer [ ]
System administrator [ ]
Service developer [ ]
Computer science researcher [ ]
Other [ ]
Please specify: ................................
2. Introduction:
----------------
2.1 Provide a paragraph introduction to your use case.
Background to the project is another alternative.
(E.g. 100 words).
...
2.2 Is there a URL with more information about the project ?
...
3. Use Case to Motivate Functionality Within a Simple API:
----------------------------------------------------------
Provide a scenario description to explain customers' needs.
E.g. "move a file from A to B," "start a job."
Please include figures if possible.
If your use case requires multiple components of functionality,
please provide separate descriptions for each component,
bullet points of 50 words per functionality are acceptable.
...
4. Customers:
-------------
Describe customers of this use case and their needs. In
particular, where and how the use case occurs "in nature" and
for whom it occurs. E.g. max 40 words
...
5. Involved Resources:
----------------------
5.1 List all the resources needed: e.g. what hardware, data,
software might be involved.
...
5.2 Are these resources geographically distributed?
...
5.3 How many resources are involved in the use case? E.g. how
many remote tasks are executing at the same time?
...
5.4 Describe your codes and tools: what sort of license is
available, e.g. open or closed source license; what sort of
third party tools and libraries do you use, and what is
their availablility; do you regularly work from source
code, or use pre-compiled applications; what languages are
your applications developed in (if relevant), e.g.
Fortran, C, C++, Java, Perl, or Python.
...
5.5 What information sources do you require, e.g. certificate
authorities, or registries.
...
5.6 Do you use any resources other than traditional compute
or data resources, e.g. telescopes, microscopes, medical
imaging instruments.
...
5.7 How often is your application used on the grid or grid-like
systems?
[ ] Exclusively
[ ] Often (say 50-50)
[ ] Ocassionally on the grid, but mostly stand-alone
[ ] Not at all yet, but the plan is to.
6. Environment:
---------------
Provide a description of the environment your scenario runs in,
for example the languages used, the tool-sets used, and the
user environments (e.g. shell, scripting language, or portal).
...
7. How the resources are selected:
----------------------------------
7.1 Which resources are selected by users, which are inherent
in the application, and which are chosen by system
administrators, or by other means? E.g. who is specifying
the architecture and memory to run the remote tasks?
...
7.2 How are the resources selected? E.g. by OS, by CPU power,
by memory, don't care, by cost, frequency of availability
of information, size of datasets?
...
7.3 Are the resource requirements dynamic or static?
...
8. Security Considerations:
---------------------------
8.1 What things are sensitive in this scenario: executable
code, data, computer hardware? I.e. at what level are
security measures used to determine access, if any?
...
8.2 Do you have any existing security framework, e.g.
Kerberos 5, Unicore, GSI, SSH, smartcards?
...
8.3 What are your security needs: authentication,
authorisation, message protection, data protection,
anonymisation, audit trail, or others?
...
8.4 What are the most important issues which would simplify
your security solution? Simple API, simple deployment,
integration with commodity technologies.
...
9. Scalability:
---------------
What are the things which are important to scalability and to
what scale - compute resources, data, networks ?
...
10. Performance Considerations:
-------------------------------
Explain any relevant performance considerations of the use
case.
...
11. Grid Technologies currently used:
-------------------------------------
If you are currently using or developing this scenario, which
grid technologies are you using or considering?
...
12. What Would You Like an API to Look Like?
--------------------------------------------
Suggest some functions and their prototypes which you would
like in an API which would support your scenario.
...
13. References:
---------------
List references for further reading.
...
More information about the ogsa-wg
mailing list