-
Notifications
You must be signed in to change notification settings - Fork 0
Functional Requirements
Andparv edited this page Oct 15, 2018
·
24 revisions
The end result will contain a lot of different data to be easily accessible by the users. It is hard to define a lot of functional requirements for the data due to the unambiguousness of the end result and because there are no specific use cases outside of filtering and sorting. For better use of the data, it should meet some specifications.
- The application should be able to import datasets of different formats (CSV, JSON, XML etc.) and convert them to CSV.
- Users should be able to add/edit/remove data sources. (UC#1)
- The application should update datasets in specified intervals.
3.1 Users should be able to specify update intervals for each data source. (UC#2)
3.2 The application should display the update interval and the time of last update for each data source. (UC#3) - Users should be able to manually force an update for any data source. (UC#4)
- The application should relay information regarding an update:
5.1 In case of a successful update, the application should display a notification detailing the results of the update.
5.2 In case of an unsuccessful update, an error message is shown as a notification, detailing what went wrong, if possible. - Users should be able to create a subset of any dataset defined by one or more variables (such as time, location etc.). (Querybuilder) (UC#6)
- The application should support saving and loading presets for creating the subsets (from FR. #6). (UC#7)
- All data in the application should have standardized location information if at all possible.
- Users should be able to easily select a town/county/area from which to display information. (UC#5)
- The application should support the creation of Textviews from datasets. (UC#8)
10.1 Users should be able to select/deselect/reorder columns from datasets to create Textviews.
10.2 Users should be able to add text (in addition to columns from datasets) to create Textviews. - The application should support the saving and loading of presets for creating Textviews. (UC#9)
- Iterations
-
Use cases
- UC-1 Editable Data sources
- UC-2 Editable update intervals
- UC-3 Displayable update information
- UC-4 Manual updating
- UC-5 Selecting data based on the location
- UC-6 Creating dataset subsets
- UC-7 Saving and loading dataset subsets
- UC-8 Creating textviews from datasets
- UC-9 Saving and loading of presets for creating Textviews.