Difference between revisions of "Full-Stock-Developers"
From mn/ifi/inf5750
(→Product overview) (Tag: Visual edit) |
m (Lagt til utfyllende beskrivelser) (Tag: Visual edit) |
||
| Line 10: | Line 10: | ||
== Product overview == | == Product overview == | ||
| − | The application will include | + | The application will include three different features: |
| − | * ''' | + | * '''Admin control:''' An user with admin privieges is able to freely form StockGroups using a selection of dataElements, and/or Indicators. The stockGroup will contain a reference to a dataset containging starting balance, and a set of references to contributors to the monthly depletion of stock. For instance units consumed, units discarded, units lost and more. Within the admin control menu is also the option to set min and max values, referring to the minimum and maximum number of months of stock usage the admin wish to retain each month. Lastly, the admin user is able to name the stockGroup. |
| − | |||
| − | |||
| − | |||
| − | |||
Time trend view displays a line graph with the fluctuating availability of a stock, as well as an average of this availability. | Time trend view displays a line graph with the fluctuating availability of a stock, as well as an average of this availability. | ||
The Admin control shows a user interface to add stock groups and one to edit the minimum and maximum values of existing stock spaces. | The Admin control shows a user interface to add stock groups and one to edit the minimum and maximum values of existing stock spaces. | ||
| + | |||
| + | * '''Stock visualizer:''' We display Stock visualizer as a bar graph, where each bar is an organizational unit's months of stock left. This number is calculated by dividing the current level of stock left with the average use of that stock. The user is able so select among the admin-created stockGroups and combine it with one or more organisational units to display estimated months of stock left given the prior 12 months of usage data. The user will be notified if the time left is above or below the set min or max values, set by the admin. | ||
| + | * '''Time trend view:''' Display a graph of historical levels of a given stock in a given organizational unit. | ||
| + | as well as a third feature: | ||
=== Requirements === | === Requirements === | ||
Revision as of 11:23, 7 December 2017
Contents
Members
- Andreas Finn Hansen (andrefh)
- Kristoffer Solheim (krisaso)
- Lukas Vannini (lukasva)
- Ole Marius Haanæs (omhaanae)
Assignment
Product overview
The application will include three different features:
- Admin control: An user with admin privieges is able to freely form StockGroups using a selection of dataElements, and/or Indicators. The stockGroup will contain a reference to a dataset containging starting balance, and a set of references to contributors to the monthly depletion of stock. For instance units consumed, units discarded, units lost and more. Within the admin control menu is also the option to set min and max values, referring to the minimum and maximum number of months of stock usage the admin wish to retain each month. Lastly, the admin user is able to name the stockGroup.
Time trend view displays a line graph with the fluctuating availability of a stock, as well as an average of this availability.
The Admin control shows a user interface to add stock groups and one to edit the minimum and maximum values of existing stock spaces.
- Stock visualizer: We display Stock visualizer as a bar graph, where each bar is an organizational unit's months of stock left. This number is calculated by dividing the current level of stock left with the average use of that stock. The user is able so select among the admin-created stockGroups and combine it with one or more organisational units to display estimated months of stock left given the prior 12 months of usage data. The user will be notified if the time left is above or below the set min or max values, set by the admin.
- Time trend view: Display a graph of historical levels of a given stock in a given organizational unit.
as well as a third feature:
Requirements
Architecture
Describe the technical architecture of the product, including what frameworks you will be using (e.g. react, angular, others) and /why/ you have chosen these.
Main frameworks
ng2-charts (based on Chart.js)
Other frameworks
Development
Division of labor
1.nov:
- Kristoffer: get a basic visual framework up and running.
- Andreas: start working on finding the API calls for the parameters of the stock visualizer view.
- Ole: start working on finding the API calls necessary in the time trend view.
- Lukas: start working on creating a table in the API for registering min and max values for a given OU/SKU pair.
Licensing
Discuss the implications (if any) on the product you are development from the software licenses of the frameworks and libraries you are using.
All our frameworks use the liberal MIT license. This means that only credit is needed.
