TeamHope

From mn/ifi/inf5750
Revision as of 13:07, 27 October 2017 by Mikkelmb@uio.no (talk | contribs) (Mockups: Added division of labor from prototype of time trend)

Jump to: navigation, search

Group members

Mikkel Bakken

Ingvild Larsen

Carl Petter Boehlke

Kristian Pedersen

Assignment

Stock Level Visualisations

Requirements

Description

The application shall have two modes:

- Estimates, showing estimated months left of a selected stock, for chosen organization units.

- Time trend, showing time trend of stock for a single organization unit.

Functional requirements

The user can choose between the two modes described above.

Both:

- Default min/max boundaries can be set by an administrator (administrator view in mockup).

- The user can specify their own desired min/max boundaries as well (user view in mockups).

- If the administrator has not set a default min/max boundary, there is no default min/max boundary in the plot.

For "Estimates":

- The user can specify one stock type, and multiple organization units.

- Show current estimates as columns in a column diagram.

- Columns outside the specified min/max boundaries will be highlighted.

- Estimates are calculated based on average consumption over the last 3 months, and current stock levels ((current stock) / (average consumption) = estimated months left).

- Default min/max boundaries are shared by all organization units.

For "Time trend":

- The user can select an organization unit, and a stock type.

- Show time trend(months) of available stock as a graph.

- The min/max boundaries are shown as lines in the graph.

- The user can choose the time period they wish to see the time trend for (by default the last 6 months).

- Default min/max boundaries are associated with a specific organization unit and stock type.

Mockups

Mockup estimates admin view.jpg

Architecture

We have chosen React, because of the view focused framework. We also feel that the group as a whole has more experience with React.

- Highcharts

Licensing

To do

Timeline

Milestone Goal Date Comment
1 Wiki page ready November 1st
2 Start of coding October 31st
2 Prototype ready November 7th
3 App ready for use November 20th

Division of labour

We divide the labour by component and give the tasks for each member between the meetings. We do this to be flexible and get a fair division of labour.

Components

- Select mode (ModeSelector)

Estimates (Estimates):

Sidebar:

- Search for organization units (MultipleOrgSearch)

- Search field (OrgSearch)

- Selected orgs list (OrgList)

- Input min/max boundary (UserBoundaryInput)

- Min (InputNumber)

- Max (InputNumber)

- Select stock (StockSelector)

- Showbutton (Showbutton)

- Admin box (AdminBox)

- Input min/max boundary (AdminBoundaryInput)

- OK button (OK)

Visualization:

- Diagram (EstimateDiagram)

Time trend (TimeTrend):

Sidebar:

- Search for organization unit (SingleOrgSearch)

- Search field (OrgSearch)

- Input min/max boundary (UserBoundaryInput)

- Min (InputNumber)

- Max (InputNumber)

- Select stock (StockSelector)

- Select period (PeriodSelector)

- From (SelectDate)

- To (SelectDate)

- Showbutton (Showbutton)

- Admin box (AdminBox)

- Input min/max boundary (AdminBoundaryInput)

- OK button (OK)

Visualization:

- Time trend (TimeTrendGraph)

Background:

- Stock level retriever (StockFetcher)

- Estimate calculator (EstimateCalculator)

Division:

Protype:

Time trend:

Ingvild:

Mode selector

Input min/max (user&admin)

Kristian:

Visualizer

Carl:

Search org unit

Mikkel:

Select to/from

Stock selector

Repository

https://github.uio.no/TeamHope/project