https://wiki.uio.no/mn/ifi/inf5750/api.php?action=feedcontributions&user=Sebastps%40uio.no&feedformat=atommn/ifi/inf5750 - User contributions [en]2024-03-29T06:28:25ZUser contributionsMediaWiki 1.27.4https://wiki.uio.no/mn/ifi/inf5750/index.php?title=GruppeX&diff=5613GruppeX2017-12-06T23:07:54Z<p>Sebastps@uio.no: </p>
<hr />
<div><br />
== Group members ==<br />
* Markus Medalen (markusme)<br />
* Petter Hallvard Tveiten Gregersen (phgreger)<br />
* Sebastian Pettersen Sigurdsen (sebastps)<br />
* Frank Lyder Bredland (franklbr)<br />
<br />
== Product descriptions requirements ==<br />
<br />
=== Assignment ===<br />
[https://wiki.uio.no/mn/ifi/inf5750/index.php/HIV_Cascade_Analysis HIV Cascade Analysis]<br />
<br />
=== Assignment description ===<br />
In this assignment we are gone create an DHIS2 application that provides a visualisation of a HIV 90-90-90 cascade. DHIS2 already has a Data Visualizer implemented to create bar charts, but lacks functionalities to have the value of each bar represents the subset of the previous bar. <br />
<br />
The application should also present this information in three different ways: <br />
* As percentages, where the first bar in the cascade is 100%, and the subsequent bars as expressed as percentages of the previous. <br />
* As raw numbers, but showing both the actual number and the gap. <br />
* As raw data and percentages (on different axis), i.e. bars with the raw data and a line with the percentage. <br />
The application can be used in different settings/ countries and thus, different DHIS2 databases. Because of this, we need to create an interface that the user can configurated and save for later: <br />
* What data elements/indicators to include in the cascade, as this might differ from country to country or even at different levels within a country. <br />
* The target for each data element/indicator. While the global target for HIV is 90-90-90, it should be possible to set the target in the app. <br />
Cascades are often done for different population groups (by sex, age etc). Therefore, it should be possible to save different configurations, and to swap between these. In addition to selection of data, it must be possible to select the time period and organisation unit to display data for, either as part of the configuration or when generating the visualisation. There must be support for downloading the visualisations. <br />
<br />
== Architecture ==<br />
<br />
=== Frameworks and external libraries: ===<br />
* [https://reactjs.org/ React] - We chose React because two people on the group knew a little bit how to use that framework from before. <br />
* https://d3js.org/ - We chose d3 for data visualisation because it has high customisability <br />
* [https://getbootstrap.com/docs/3.3/css/ https://getbootstrap.com]- We chose bootstrap for easy and good looking CSS.<br />
<br />
== Tools ==<br />
* https://www.jetbrains.com/webstorm/ - IDE<br />
* https://slack.com/ - Team communcation<br />
* https://discordapp.com/ - Team voice communication<br />
* https://github.uio.no/ - Version control<br />
Whenever someone pushes changes to the repository, the other members are notified on Slack.<br />
<br />
== Licensing ==<br />
* BSD - http://www.linfo.org/bsdlicense.html<br />
** DHIS2<br />
<br />
** MIT - https://opensource.org/licenses/MIT<br />
*** React <br />
*** Jest <br />
*** Redux<br />
*** Bootstrap<br />
*** Our HIV Cascade application<br />
<br />
== Division of labour ==<br />
Everyone works on everything.<br />
<br />
We use Git issues to create a backlog where everyone can grab assignments to work on.<br />
<br />
We also have at least two weekly meetings where we work together and discuss the project. <br />
<br />
== Mockups ==<br />
[[File:1.1-Chart.png|thumb|600x600px|Chart layout mockup|none]] <br />
[[File:2.1-Configure.png|thumb|600x600px|Configure layout mockup|none]]<br />
<br />
== Use case diagram ==<br />
[[File:Use case diagram USER.png|none|thumb|392x392px|Use case diagram - User flow]]<br />
[[File:Use case diagram admin.png|none|thumb|388x388px|Use case diagram - Administrator flow / Configure flow]]<br />
<br />
== Timeline ==<br />
[[File:Groupx.png|thumb|647x647px|Estimated timeline|none]]<br />
<br />
== Link to project repository ==<br />
https://github.uio.no/GruppeX/INF5750-dhis2-webapp</div>Sebastps@uio.nohttps://wiki.uio.no/mn/ifi/inf5750/index.php?title=GruppeX&diff=5052GruppeX2017-10-30T21:43:49Z<p>Sebastps@uio.no: /* Group members */</p>
<hr />
<div><br />
== Group members ==<br />
* Markus Medalen (markusme)<br />
* Petter Hallvard Tveiten Gregersen (phgreger)<br />
* Sebastian Pettersen Sigurdsen (sebastps)<br />
* Frank Lyder Bredland (franklbr)<br />
<br />
== Product descriptions requirements ==<br />
<br />
=== Assignment ===<br />
[https://wiki.uio.no/mn/ifi/inf5750/index.php/HIV_Cascade_Analysis HIV Cascade Analysis]<br />
<br />
=== Assignment description ===<br />
In this assignment we are gone create an DHIS2 application that provides a visualisation of a HIV 90-90-90 cascade. DHIS2 already has a Data Visualizer implemented to create bar charts, but lacks functionalities to have the value of each bar represents the subset of the previous bar. <br />
<br />
The application should also present this information in three different ways: <br />
* As percentages, where the first bar in the cascade is 100%, and the subsequent bars as expressed as percentages of the previous. <br />
* As raw numbers, but showing both the actual number and the gap. <br />
* As raw data and percentages (on different axis), i.e. bars with the raw data and a line with the percentage. <br />
The application can be used in different settings/ countries and thus, different DHIS2 databases. Because of this, we need to create an interface that the user can configurated and save for later: <br />
* What data elements/indicators to include in the cascade, as this might differ from country to country or even at different levels within a country. <br />
* The target for each data element/indicator. While the global target for HIV is 90-90-90, it should be possible to set the target in the app. <br />
Cascades are often done for different population groups (by sex, age etc). Therefore, it should be possible to save different configurations, and to swap between these. In addition to selection of data, it must be possible to select the time period and organisation unit to display data for, either as part of the configuration or when generating the visualisation. There must be support for downloading the visualisations. <br />
<br />
== Architecture ==<br />
<br />
=== Frameworks and external libraries: ===<br />
* [https://reactjs.org/ React]<br />
* http://www.reactd3.org/ - for visualization of bar charts<br />
<br />
* More to be added later...<br />
<br />
== Licensing ==<br />
<br />
== Division of labour ==<br />
Everyone works on everything.<br />
<br />
We use Git issues to create a backlog where everyone can grab assignments to work on.<br />
<br />
We alos have at least two weekly meetings to discuss the project. [[File:Groupx.png|thumb|647x647px]]<br />
<br />
== Timeline ==<br />
Estimated timeline<br />
<br />
== Link to project repository ==<br />
https://github.uio.no/GruppeX/INF5750-dhis2-webapp</div>Sebastps@uio.nohttps://wiki.uio.no/mn/ifi/inf5750/index.php?title=GruppeX&diff=4780GruppeX2017-10-25T10:26:34Z<p>Sebastps@uio.no: Added headings</p>
<hr />
<div>...<br />
<br />
== Group members ==<br />
<br />
== Product descriptions requirements ==<br />
<br />
== Architecture ==<br />
<br />
== Licensing ==<br />
<br />
== Division of labour ==<br />
<br />
== Link to project repository ==</div>Sebastps@uio.nohttps://wiki.uio.no/mn/ifi/inf5750/index.php?title=Main_Page&diff=4764Main Page2017-10-24T11:01:18Z<p>Sebastps@uio.no: /* Groups */</p>
<hr />
<div>== INF5750 Wiki - 2017 ==<br />
This is the Wiki for INF5750 2017. Information about group projects will be given here. This page might be updated during the semester, so make sure you have a look from time to time.<br />
<br />
(The wiki for 2016 has been moved [[2016|here]].)<br />
<br />
== Practical information ==<br />
The group project is only open to students who have passed the two obligatory assignments.<br />
<br />
=== Forming groups ===<br />
Groups should have 3-4 members. For those who have already formed a group with co-students, please fill [http://nettskjema.uio.no/answer/88401.html this form] with the user name of each group member (fill the form '''once''' per group).<br />
<br />
Piazza has functionality for [https://piazza.com/class/j6lzzrhfcxz8?cid=5 forming groups], both if you are a student looking for a group to join, and if you are a group looking for additional members.<br />
<br />
Those who have not submitted a group by Wednesday October 18 will be put in random groups. Note: depending on how the numbers add up, groups might be assigned an additional member.<br />
<br />
=== Using the Wiki ===<br />
Each group should create and maintain a Wiki page for the project. On this Wiki, you should document the following key elements:<br />
* ''Group members.'' List members of the group.<br />
* ''Product descriptions requirements.'' A description of the product you are developing, including features/requirements being implemented and mockups/screenshots. Also specify which assignment you have chosen.<br />
* ''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.<br />
* ''Licensing''. Discuss the implications (if any) on the product you are development from the software licenses of the frameworks and libraries you are using.<br />
* ''Division of labour.'' Describe how tasks are divided within the group.<br />
* ''Link to project repository''. Include a link to the project repository, even though the repository should be private and only visible to group members and group teachers/lecturers.<br />
<br />
=== Source code ===<br />
Use the [https://github.uio.no UiO GitHub] for source code. Create an organisation named after the group, and add the group members and teachers. Make sure the repository your create is private.<br />
<br />
There should be a README in the repository describing how to build/run app.<br />
<br />
Use github to document issues.<br />
<br />
== Assignments ==<br />
Each group should choose one the of following assignments:<br />
* [[Sharing Editor]]<br />
* [[HIV Cascade Analysis]]<br />
* [[Stock Level Visualisations]]<br />
* [[Master Facility List]]<br />
* [[Sub-National Reports]]<br />
<br />
== Timeline and deliverables ==<br />
Keep both the project Wiki and the GitHub repository updated during the whole project period. Group teachers will check these from time to time.<br />
<br />
=== Milestone - November 1 ===<br />
The project has one milestones before the final delivery. By this milestone, the group should have created a wiki covering the key areas described above, including:<br />
* The assignment you have chosen and an overview of the product to be developed, including features (i.e. your interpretation of the assignment).<br />
* Proposed architecture of the app (including key frameworks to be used).<br />
* Broad timeline for development.<br />
* Link to project repository.<br />
<br />
=== Final presentation ===<br />
Exact dates for the final presentation will be announced later, but will be in the 2 weeks following the exam. Due to the number of groups, presentations will be over several days.<br />
<br />
Each group will be given 20 minute to present their project to a panel of evaluators. The presentation should include:<br />
* Group and student names.<br />
* The assignment you have chosen, and how you decided to approach it.<br />
* An overview of the development process, including key challenges.<br />
* An overview of the key frameworks and libraries used, including /why/ you have chosen them and the implication on your product of how they are licensed.<br />
* The contribution of each group member.<br />
* A demo of the final product.<br />
All points should be covered, but make sure to give enough time for the demo of the final product.<br />
<br />
Due to the number of projects to be presented, the 20 minutes is a strict time limit, so plan your presentation accordingly.<br />
<br />
== Evaluation ==<br />
The group projects will be graded based on:<br />
* the product itself (source code)<br />
* the project documentation (wiki)<br />
* the final presentation by the group.<br />
The groups will as a general rule be graded as a whole, however, if it is clear from the documentation, presentation and/or commit logs that certain group members have not contributed fully to the group, their grade might be adjusted.<br />
<br />
The grade for the group project makes up 60% of the overall grade in the course.<br />
<br />
== Groups ==<br />
Add a link to your groups wiki page here:<br />
*[[Stock Sharks]]<br />
*[[IngenRomForFeil]]<br />
*[[RomForFeil]]<br />
*[[Kokeriet]]<br />
*[[Pied Piper]]<br />
*[[BEE]]<br />
*[[IDLE]]<br />
*[[HSK]]<br />
*[https://wiki.uio.no/mn/ifi/inf5750/index.php/Visualie Visualie]<br />
*[[LittRomForFeil]]<br />
*[[PSM]]<br />
*[https://wiki.uio.no/mn/ifi/inf5750/index.php/GruppeX GruppeX]</div>Sebastps@uio.nohttps://wiki.uio.no/mn/ifi/inf5750/index.php?title=GruppeX&diff=4763GruppeX2017-10-24T11:00:14Z<p>Sebastps@uio.no: Created page with "..."</p>
<hr />
<div>...</div>Sebastps@uio.no