View Source

Goals

Initial open release of Brown Dog
Highlight what can be done with a Data Transformation Service through an initial suite of transformation tools, a number of sample clients, and sample data allowing a user to quickly try things out

The beta release will:

Provide the community with a first glimpse of Brown Dog
Allow the Brown Dog team to increase exposure through presentations and hands on tutorials
Allow the team to identify bugs through real world usage and harden the service towards a 1.0 release

Many users will want to try out the system without too much effort
Will need to support very novice users (easy to use interfaces/samples)
Some users will begin to regularly use the system, throwing many requests at the service

#	Title	User Story	Importance	Notes
1	Beta Tools	The user will be able to try out one of a number of tools spanning a range of scientific domains and general data usage tasks. Upon signing up for an account the user will be able to explore the tools catalog to see what transformation tools are available as well as what each is capable of doing. These tools will be deployed under the elasticity module so that a user can try the tool via one of a number of possible client interfaces. The user should come away with a sense of the breadth of data currently and potentially supported over time, the flexibility of the system, the potential for contributing tools of their own, and the types of tools that would fit as part of the service.	Must Have	http://browndog.ncsa.illinois.edu/tools/ Project Supported Transformations Progress
2	BDFiddle/Bookmarklet	Describe the user and what they are trying to achieve	Must Have	http://browndog.ncsa.illinois.edu/bdfiddle/
3	BDFiddle test files for all tools		Must Have	http://browndog.ncsa.illinois.edu/bdfiddle/examples.php
4	Beta Clients	BD CLI, Windows Client, R Library, Python Library, Matlab Library
5	Documentation			Documentation
6	Admin/Support plan		Must Have	Administration

Include any mockups, diagrams or visual designs relating to these requirements.

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
(e.g. How we make users more aware of this feature?)	Communicate the decision reached

List the features discussed which are out of scope or might be revisited in a later release.