Use Case Catalog

This catalog tracks use cases for Sakai integration that are submitted by the SEPP Enterprise Discussion Group. These use cases will serve to provide requirements for core Sakai development. We have adopted Confluence to lower the hassle of creating and maintaining Use Cases. Please read and follow the guidelines below when working with the Use Case Catalog.

Contents
Use Case Process
Publishing a Use Case
Categories

Use Case Process

This catalog is intended to track use cases for Sakai integration with enterprise information systems. Use cases are organized into categories based upon the Sakai module they interface with, or upon the function they fulfill (see Categories below). This catalog is intended to strike a balance between two forces:

This is open source, so we vote with our feet. Any SEPP member should be able to submit a use case.
Our interests will help drive current and future development within Sakai, and may be provided priority or development support from the Core.

The first of these begs for a low-fuss, self-selection process, while the second requires that we somehow visibly allocate a scarce resource - the attention of discussion group and the Sakai community. To serve these two needs it is proposed that the test for inclusion of a use case be the interest of a single SEPP member. Please include any use case you find relevant to your work at enterprise integration. To serve the needs of the group, however, it may be periodically necessary to attempt to pull together similar cases in hopes of deriving more widely applicable (and thus more supportable) cases.

In order to maintain consistency and order a Use Case template has been created. Please publish your use cases using this template. Instructions for publishing your use case follow below.

Publishing a Use Case

Please follow one of the methods below to publish your use case. A template has been provided for creating use cases. A guide is available to describe the various template fields.

At present the template editting features of Confluence are limited: the template slots are text areas of limited flexability. This means that editting in-line will be tough except for simple, short field values. Please use the template anyway - it will provide a standard structure for our use cases. Use cases can be editted after creation by using the 'edit page' function of Confluence.

Method I: Create A Link, Then A Page

Select the appropriate category below.
Select 'edit page' from the menu at the right.
Create a new link with the name of your use case (see the 'Help Tips' panel on the right of the edit screen for the proper link format).
Preview your changes, then select Update when you are done.
Click on your new link - Confluence will prompt you to create the content of the new page.
Click the "select a template page" link
Select the 'Use Case' template.
Fill in the values that are easy to fill in via the form
Use the normal 'edit page' function to fill in the remaining data.

Method II: Create A Page, Then A Link

Start at the Enterprise DG Confluence Home Page
Select 'add page'
Click the "select a template page" link
Select the 'Use Case' template.
Fill in the values that are easy to fill in via the form
Use the normal 'edit page' function to fill in the remaining data.
Select the appropriate category below.
Select 'edit page' from the menu at the right.
Create a new link with the name of your use case (see the 'Help Tips' panel on the right of the edit screen for the proper link format).
Preview your changes, then select Update when you are done.