Difference between revisions of "N.E.T Survey"
| Line 51: | Line 51: | ||
== '''Work divided between group members''' == | == '''Work divided between group members''' == | ||
| − | Haven't divided the work between each other yet, but we've decided to use a couple of days to learn the DHIS2 architecture and learning more necessary programming that will be needed for this project. '''''To be updated after our next meeting.'''''Since we're making a webapp we won't be needing to learn basic authentication between a server and client. The client will be already authenticated when using the app. | + | Haven't divided the work between each other yet, but we've decided to use a couple of days to learn the DHIS2 architecture and learning more necessary programming that will be needed for this project. '''''To be updated after our next meeting.'''''Since we're making a webapp we won't be needing to learn basic authentication between a server and client. The client will be already authenticated when using the app. |
<br> | <br> | ||
| Line 57: | Line 57: | ||
== '''Architechture''' == | == '''Architechture''' == | ||
| − | - JavaScript, jQuery, CSS, HTML5. | + | - JavaScript, jQuery, CSS, HTML5. |
| − | - We haven't decided which GUI framework to use yet, '''''to be updated after our next meeting.''''' | + | - We haven't decided which GUI framework to use yet, '''''to be updated after our next meeting.''''' |
| − | - Instead of only skip logic, we'll try to implement the Survey app with "grow" logic. | + | - Instead of only skip logic, we'll try to implement the Survey app with "grow" logic. |
- We define "grow" logic as giving the user only the nessesary data/questions/choices at a certain time. And skipping the alternatives that aren't relevant for the answer. | - We define "grow" logic as giving the user only the nessesary data/questions/choices at a certain time. And skipping the alternatives that aren't relevant for the answer. | ||
| − | '''[Example]''' If the user has chosen their gender as male earlier in the survey, the question of being pregnant will never shown. | + | '''[Example]''' If the user has chosen their gender as male earlier in the survey, the question of being pregnant will never shown. |
| + | |||
| + | |||
| + | |||
| + | == '''Group meeting log''' == | ||
| + | '''29th October 2013:''' First meeting of the N.E.T group. Deciding the architechture and how we should proceed with the project. Next meeting will be held on '''Friday 1st November.''' | ||
Revision as of 15:51, 29 October 2013
Contents
Group members of N.E.T
- Nguyen (congnn@ifi.uio.no)
- Eivind (eivineng@ifi.uio.no)
- Thuc (thucth@ifi.uio.no)
Requirements for the Survey app
- Single event data entry form
- Skip logic (eg. If pregnant, fill in these extra forms)
- Make interface for easily defining form and skip logic (integrated with single event, but you’ll need some additional info)
- Available as DHIS2 web app and Android app (phonegap) - Touch friendly UI
(copied directly from Lecture 6 - Group projects)
Milestones set by course-teachers
Each group should follow these milestones:
Milestone 1: 1st November
Document features and architecture on Wiki
Show understanding of DHIS2 web apps
Milestone 2: 15th November
First bare-bone version - static HTML
Uploadable as DHIS2 web app
Milestone 3: 30th November
Finished, if applicable also with mobile app.
Final delivery: 8th December
Presentation: 9th December
Work divided between group members
Haven't divided the work between each other yet, but we've decided to use a couple of days to learn the DHIS2 architecture and learning more necessary programming that will be needed for this project. To be updated after our next meeting.Since we're making a webapp we won't be needing to learn basic authentication between a server and client. The client will be already authenticated when using the app.
Architechture
- JavaScript, jQuery, CSS, HTML5.
- We haven't decided which GUI framework to use yet, to be updated after our next meeting.
- Instead of only skip logic, we'll try to implement the Survey app with "grow" logic.
- We define "grow" logic as giving the user only the nessesary data/questions/choices at a certain time. And skipping the alternatives that aren't relevant for the answer.
[Example] If the user has chosen their gender as male earlier in the survey, the question of being pregnant will never shown.
Group meeting log
29th October 2013: First meeting of the N.E.T group. Deciding the architechture and how we should proceed with the project. Next meeting will be held on Friday 1st November.
