Windows share mounts

Select windows drives in Parameter space model wizard.

Use Case Descriptions

• As a user I want to select a windows drive when creating Parameter space models under the locate data table tab of the Parameter space wizard.*

Browse windows drives in Parameter space model wizard.

Use Case Descriptions

• As a user I want to be able to browse a windows network drive under the select table tab of the Parameter Space wizard.*

Use windows share drive file path locations in Parameter space model

Use Case Descriptions

• As a user I want to be able to use windows share media paths for media links in my slycat csv file which I use to create Parameter Space models*

Use windows share drive media on hover in Parameter space model

Use Case Descriptions

• As a user I want to be able to use windows share drive media paths for retrieval when hovering over a point in parameter space and should be prompted to log in and mount my drive when I am not connected to my windows drive.*

Requirements Document

1. User Requirements

1.1 User Characteristics

A typical Slycat user has a scientific background with minimal knowledge of how to use the unix operating system. Slycat users tend to be working within a windows environment and are expect to either be using chrome or Firefox within this windows environment. Due to user's general emersion in the windows environment they are used to using windows shares and network drives to collaborate and store large data sets

1.2 System's Functionality

Provide here an overview of the system and what the overall intention of the system is.

1.3 User Interfaces

Provide here a brief description of how the user will interact with the system.

2. System Requirements

2.1 Functional Requirements

List here the functional requirements of the system. Functional requirements are requirements that specify what the system should do and can be thought of as 'the system must do <requirement>'. Implementation details for each requirement should be addressed in the system design document. An example of a functional requirement would be 'the system utilizes Java version...' This list can become quite extensive and for best practice each requirement should be issued its own unique name, number, and be accompanied by a description.

#####2.2 Non-Functional Requirements List here the non-functional requirements of the system. Non-Functional requirements are requirements that specify how the system should act and can be thought of as 'the system shall be <requirement>'. An example of a non-functional requirement would be 'the system input should be able to handle any file smaller than...'