Box.net Repository Plugin

Functional Specification Revisions:

0.1 - 27/06/2008 - Jerome Mouneyrac - Draft Version

Audience:

Developer/QA tester

Status:

not implemented (Tracker Issue)

Related Documents:

• Repository API
• Use Case Number Attribution

Introduction

This document is about functional specification for Box.net Repository Plugin

Requirements

• Administrator should be able to administrate the box.net plugin
• User should be able to setup an access to a Box.net account

Use Cases

UC003-1 Administrate Box.net Plugin

Base scenario

1. Administrator goes to the Repository Settings page.

Pre conditions

- the plugin is installed

- the user has Administrator role

Post conditions

- The API_KEY of box.net can be changed.

- The callback parameters should be specified here.

UC003-2 Box.net side setting

Base scenario

1. The authentication process is done by box.net, so box.net need a callback page to tell Moodle the authentication result

Pre conditions

- the plugin is installed in moodle side

- a new project has been created in box.net, see http://enabled.box.net/my-projects/

Post conditions

- API_KEY

- Call-back URL can be set here.

UC003-3 Setup a Box.net access

Base scenario

1. User opens a file picker, try to fetch a file from box.net

Pre conditions

- the user has a Box.net account

Post conditions

- the user can navigate into his box.net repository in the file picker