Difference between revisions of "CloseSource"
| Line 18: | Line 18: | ||
* [https://reactjs.org/ React] | * [https://reactjs.org/ React] | ||
| − | We intend to use React because it is | + | We intend to use React because it is the second most used JavaScript frameworks. Furthermore one of the group members had experience with React from before, and the rest of the group wanted to learn React. As it has a fast learning curve and a very active community, getting help will also be straightforward. |
| + | |||
| + | We also saw in the lecture that for smaller projects React supposedly is more efficient than for instance Angular 2. In addition React has reuseable components, so if anyone at DHIS2 want to re-use our code for other illnesses or statistics, this can easily be done with React. This way we can also hope to help extend DHIS2 as a platform, by building reusable, sustainable code in a true Open Source fashion. | ||
===Libraries/Tools=== | ===Libraries/Tools=== | ||
| Line 30: | Line 32: | ||
== Division of labour == | == Division of labour == | ||
| − | We all want to have a fullstack understanding of the application, so we will divide the working power where it needs be. Even so we have defined the most essential parts of development and divided responsibility for these. In practice this means that for the following tasks, each group member is responsible that their part of the application is up to speed with the rest of the application during development. In this way we ensure | + | We all want to have a fullstack understanding of the application, so we will divide the working power where it needs be. Even so we have defined the most essential parts of development and divided responsibility for these. In practice this means that for the following tasks, each group member is responsible that their part of the application is up to speed with the rest of the application during development. In this way we ensure that all group members are familiar with the other parts of the application, so we never end up in a situation where one member is unavailable and the development stops. We also ensure that someone is keeping track of the different parts of the application and can communicate if that particular part starts lagging behind. |
{| class="wikitable" | {| class="wikitable" | ||
!Group memeber | !Group memeber | ||
| Line 39: | Line 41: | ||
|- | |- | ||
|Duy Johnny Khac Nguyen | |Duy Johnny Khac Nguyen | ||
| − | |Graph/Chart development | + | |Graph/Chart development |
|- | |- | ||
|Edvarda Eriksen | |Edvarda Eriksen | ||
| − | |UX design and overall application | + | |UX design and overall application interface |
|} | |} | ||
== Link to project repository == | == Link to project repository == | ||
[https://github.uio.no/CloseSource/closesource_hiv_project CloseSource: HIV Cascade Analysis] | [https://github.uio.no/CloseSource/closesource_hiv_project CloseSource: HIV Cascade Analysis] | ||
Revision as of 16:41, 31 October 2017
Contents
About CloseSource
This is the Wiki for CloseSource, one of the groups enrolled in INF5750 - Open Source Development 2017. Information about our group project will be added here throughout the semester.
Group members
The group consists of the following members:
- Edvarda W. Eriksen (ererikse)
- Duy Johnny K. Nguyen (djnguyen)
- Milad Sharif (milads)
Product descriptions requirements
We have chosen the task
More coming soon.
Architecture
Frameworks
We intend to use React because it is the second most used JavaScript frameworks. Furthermore one of the group members had experience with React from before, and the rest of the group wanted to learn React. As it has a fast learning curve and a very active community, getting help will also be straightforward.
We also saw in the lecture that for smaller projects React supposedly is more efficient than for instance Angular 2. In addition React has reuseable components, so if anyone at DHIS2 want to re-use our code for other illnesses or statistics, this can easily be done with React. This way we can also hope to help extend DHIS2 as a platform, by building reusable, sustainable code in a true Open Source fashion.
Libraries/Tools
More coming soon.
Licensing
Coming soon.
Division of labour
We all want to have a fullstack understanding of the application, so we will divide the working power where it needs be. Even so we have defined the most essential parts of development and divided responsibility for these. In practice this means that for the following tasks, each group member is responsible that their part of the application is up to speed with the rest of the application during development. In this way we ensure that all group members are familiar with the other parts of the application, so we never end up in a situation where one member is unavailable and the development stops. We also ensure that someone is keeping track of the different parts of the application and can communicate if that particular part starts lagging behind.
| Group memeber | Task |
|---|---|
| Milad Sharif | Data retrieval and manipulation between DHIS2 and application |
| Duy Johnny Khac Nguyen | Graph/Chart development |
| Edvarda Eriksen | UX design and overall application interface |
