Development:Box.net Repository Plugin: Difference between revisions
From MoodleDocs
Line 32: | Line 32: | ||
====Base scenario==== | ====Base scenario==== | ||
# | # User goes to the Box.net Repository Settings page. | ||
# User sets the API_KEY | |||
# User selects the save operation. | |||
# System displays a "success" message | |||
====Pre conditions==== | ====Pre conditions==== | ||
:- the plugin is installed | :- the plugin is installed | ||
:- the user has Administrator role | :- the user has Administrator role |
Revision as of 07:16, 27 June 2008
Functional Specification Revisions:
- 0.1 - 27/06/2008 - Jerome Mouneyrac - Draft Version
Audience:
- Developer/QA tester
Status:
- not implemented (Tracker Issue)
Related Documents:
Introduction
This document is about functional specification for Box.net Repository Plugin
Requirements
- Administrator should be able to administrate the box.net plugin
User Interface
Administration: Box.net Settings page
- API_KEY of box.net need to be set by the administrator
- A text reminds the administrator that he needs to save the callback url on box.net (the system can show him the callback url and have a link to box.net popup)
Box.net Account page
The authentication is done on the box.net side. This authentication will be done in the file picker (TBD: File Picker specification)
Use Cases
UC003-1 Administrate Box.net Plugin
Base scenario
- User goes to the Box.net Repository Settings page.
- User sets the API_KEY
- User selects the save operation.
- System displays a "success" message
Pre conditions
- - the plugin is installed
- - the user has Administrator role