1. EGI use case description and development planning template Use case(s):
Provider: …

2. First part
Background and Users

3. Who will be the user? Can the users be characterised? How many are they?

4. What value will the envisaged system deliver for them (the whole setup)? What will the system exactly deliver to them?

5. How should they use the system?

6. What's the timeline for development, testing and large-scale operation
What's the timeline for development, testing and large-scale operation? (Consecutive releases can/should be considered.)

7. Design and implementation plan
Second part
Design and implementation plan

8. What should the first version include
What should the first version include? - The most basic product prototype imaginable already bringing value to the users (the so-called Minimal Viable Product - MVP)

9. Which components/services already exist in this architecture?

10. Which components/services are under development (and by who)? (if any)

11. Which components/services should be still brought into the system
Which components/services should be still brought into the system? (by EGI)

12. Next steps
What, who, when …