Difference between revisions of "The underachievers"
m (→Milestones) (Tag: Visual edit) |
m (Tag: Visual edit) |
||
| Line 37: | Line 37: | ||
development project and the share number of different approaches using React + any number of libraries made | development project and the share number of different approaches using React + any number of libraries made | ||
| − | it abit hard to get a overview. Angular2 was more appealing with the "one way to do things" approach, but have some | + | it abit hard to get a overview. Angular2 was more appealing with the "one way to do things" approach, but we have some |
| − | concerns about the maturity of the framework, possible lack of documentation etc.We have not decided on technology | + | concerns about the maturity of the framework, possible lack of documentation etc. We have not decided on technology |
for the visualisation of data yet, but try to focus on geting the barebone up and running first. | for the visualisation of data yet, but try to focus on geting the barebone up and running first. | ||
Revision as of 14:21, 27 October 2016
Contents
Overview
project B Data store Manager App
Data store Manager App Browse and update the values in the DHIS2 Data Store.
The Data store is used by developers to store arbitrary data for their apps. Access to the data is
limited to the users namespace and thus only accessed through the users account.Our task will
be to make a user friendly presentation and navigation of this data, and if there is time, a way to keep
and audit trail of changes. There will also be a visualization of statistics regarding the data.
List of members
Johan Graucob E-Mail
Kenneth Frisvold E-mail
Morten Fliflet Johannesen E-mail
Technologies and Frameworks
HTML 5
CSS
TypeScript
Angular2
JSON
Visualisation tool(?)
We chose Angular2 because we liked the idea of one framework for everything. This is our first web
development project and the share number of different approaches using React + any number of libraries made
it abit hard to get a overview. Angular2 was more appealing with the "one way to do things" approach, but we have some
concerns about the maturity of the framework, possible lack of documentation etc. We have not decided on technology
for the visualisation of data yet, but try to focus on geting the barebone up and running first.
JSON will be used since this is the value data type of the Data store.
Milestones
Preliminary plan, might be object to changes.
October 28th
Document features and architecture on wiki
Model basic design
November 4th
Code basic design
Make API calls to get the data from the data store
Make unit tests(If we have time)
November 11th
Unit tests done
Represent data inside app
November 18th
Delete/change data
Visualization of data
November 25th
Log of changes(if we have time) Final touches
November 27th
Final delivery
Distribution of task
We have no set distribution of tasks yet.
