Obversive Wiki - View Source: UseCaseModel

The Use Case Model given here is not your standard UML model, but is based on research done at the University of British Columbia into Object-Oriented Modeling.  It should prove to be much simpler to understand, but you may have to read the document UnderstandingOOModels before you continue.

The use case model is broken down by UserType (based on those in UserProfiles) and then each action that UserType can perform on obveRsive is given.  Descriptions are only given where the name may not be clear.  For this use case model we are using two users:  "User" and "Action Developer" since the difference between what a Beginning R User and Auxillary User does is small and thus they can be combined.

! User

* Projects

** Open existing project
** Create new project
** Save project
** Save project as
** Package project -- This is so that people can backup projects or send them to others.  It basically takes all the files that the user has in their project and zips them up in an archive.
** Close project
** Delete project -- Not sure if this should be there.

* Data -- modeled after a spreadsheet

** Import data
** Export data
** View/Edit data -- view and edit are combined into one "spreadsheet" interface
** Save data
** Save As..
** Open data
** New data set
** Transform data -- a basic transformation interface will allow them to do things like alter columns and such.
** Sort data ascending
** Sort data descending
** Cut selection
** Paste selection
** Copy selection
** Insert new cells
** Insert new rows
** Insert new columns
** Find row

* Outputs -- modeled after a web browser

** Open output
** Close output
** Save Output As..
** Next output in "viewed so far" list
** Previous output in "viewed so far" list
** Search through outputs

* Actions -- modeled after "wizards"
** Run action -- this includes the following action related tasks:
*** View available actions
*** Select action to run
*** Complete action's wizard
*** Verify action wizard inputs are correct
*** Run action
*** Analyze action prompts and responses
** Add new action package
** Remove action package
** Update action pacakge
** List action packages



! Action Developers
All User tasks, plus:

* Open R Console -- gives direct access to R and can watch actions run
* View action logs -- Actions can spit out log messages that the action developer can use in debugging
* Generate straight to code -- this lets action developers have the action just write the R script it would run straight to a file for review.
* Open action builder -- this is a __possible__ feature, not sure yet.