Web Application - Group 4 - 2018/2019, Semester B, Quartile 3

From Control Systems Technology Group

(Difference between revisions)
Jump to: navigation, search
(Undo revision 70957 by M.g.d.quincey@student.tue.nl (Talk))
(How to implement?)
Line 30: Line 30:
There are various methods of implementing a decision model. The decision model could be implemented using an existing survey/form website, i.e. using google forms<ref name="forms">Google [https://forms.google.com "Google Forms"] Retrieved on 19-03-2019</ref>, SurveyMonkey<ref name="surveymonkey"> [https://www.surveymonkey.com/ "SurveyMonkey"] Retrieved on 19-03-2019</ref> or another similar website. This method would probably be easiest and the least time consuming, however, those websites are mostly not very flexible and do not adhere to our needs. Such form website mostly offers users to fill in answers to questions, but do not follow up with a calculation of a score and be able to give advice for solutions. Furthermore, some of these websites even restrict 'free' users to a limited number of questions to be asked.
There are various methods of implementing a decision model. The decision model could be implemented using an existing survey/form website, i.e. using google forms<ref name="forms">Google [https://forms.google.com "Google Forms"] Retrieved on 19-03-2019</ref>, SurveyMonkey<ref name="surveymonkey"> [https://www.surveymonkey.com/ "SurveyMonkey"] Retrieved on 19-03-2019</ref> or another similar website. This method would probably be easiest and the least time consuming, however, those websites are mostly not very flexible and do not adhere to our needs. Such form website mostly offers users to fill in answers to questions, but do not follow up with a calculation of a score and be able to give advice for solutions. Furthermore, some of these websites even restrict 'free' users to a limited number of questions to be asked.
-
Another option would be to create a Web application, that we can modify to our exact needs. However, this would be very time consuming to build completely from scratch. Therefore, we have done some research to already existing open source web applications that are similar to our needs. This would allow us to still create a web application suiting our needs, but would be a lot less time-consuming. We found the project electioncalculator.org<ref name="electioncalculator">Jaroslav Semančík, Michal Škop,[https://electioncalculator.org/ "electioncalculator"], KohoVolit.eu, Retrieved on 19-03-2019</ref>, which does exactly what we want, but gives advice for the electives instead of anti-UAV solutions for airports. This website presents users with propositions, to which the user can answer "yes", "no" or "I dont know". Then the user can select subjects that he/she finds extra important, and the website will present political parties that most closely resemble the same ideas of that of the user. Hence by changing the website with our own propositions, layout and solutions, we will be able to represent our previously discussed decision model on a web application.
+
Another option would be to create a Web application, that we can modify to our exact needs. We decided that a client-side application built using Vue.js and some bootstrap would allow for fast development, scalability, portability and can easily be tailored exactly to our needs. The development was done on GitHub, allowing us to host our result on GitHub pages. For the design of our app we took inspiration from the Dutch "Stemwijzer"<ref name="Stemwijzer">https://www.stemwijzer.nl</ref>, and an open source voting site called electioncalculator.org<ref name="electioncalculator">Jaroslav Semančík, Michal Škop,[https://electioncalculator.org/ "electioncalculator"], KohoVolit.eu, Retrieved on 19-03-2019</ref>.  
 +
 
 +
The site displays a series of questions, to which the user can agree, disagree or remain neutral. In addition, the user can also select some questions as being "mandatory". When a question is selected as mandatory, only solutions that follow the users preference for that question will be taken into account when computing the final solution. After having answered all questions, we ask the user to identify solutions that are extra important to him. To these solutions, the app adds an increased weight. After all questions have been answered, the scores and relative % match are computed. The results page shows a sorted list of solutions, together with a description of the solution.
== What it looks like ==
== What it looks like ==

Revision as of 12:52, 1 April 2019

Contents

Web Application

Now that we have a decision model in place, it is useful to be able to display/represent it in some way. By doing so, we will be able to validate, test and actually make use of the decision model. This also gives a clear overview of how the decision model is supposed to work. The first step is to find a suitable method to represent the decision model.

How to implement?

There are various methods of implementing a decision model. The decision model could be implemented using an existing survey/form website, i.e. using google forms[1], SurveyMonkey[2] or another similar website. This method would probably be easiest and the least time consuming, however, those websites are mostly not very flexible and do not adhere to our needs. Such form website mostly offers users to fill in answers to questions, but do not follow up with a calculation of a score and be able to give advice for solutions. Furthermore, some of these websites even restrict 'free' users to a limited number of questions to be asked.

Another option would be to create a Web application, that we can modify to our exact needs. We decided that a client-side application built using Vue.js and some bootstrap would allow for fast development, scalability, portability and can easily be tailored exactly to our needs. The development was done on GitHub, allowing us to host our result on GitHub pages. For the design of our app we took inspiration from the Dutch "Stemwijzer"[3], and an open source voting site called electioncalculator.org[4].

The site displays a series of questions, to which the user can agree, disagree or remain neutral. In addition, the user can also select some questions as being "mandatory". When a question is selected as mandatory, only solutions that follow the users preference for that question will be taken into account when computing the final solution. After having answered all questions, we ask the user to identify solutions that are extra important to him. To these solutions, the app adds an increased weight. After all questions have been answered, the scores and relative % match are computed. The results page shows a sorted list of solutions, together with a description of the solution.

What it looks like

Missing image
Figure 1: Homepage of the web app.
Missing image
Figure 2: Questions of the web app.
Missing image
Figure 3: Extra-important subjects that the user can select of the web app.
Missing image
Figure 4: Results of the web app.

Back to the root page.

References

  1. Google "Google Forms" Retrieved on 19-03-2019
  2. "SurveyMonkey" Retrieved on 19-03-2019
  3. https://www.stemwijzer.nl
  4. Jaroslav Semančík, Michal Škop,"electioncalculator", KohoVolit.eu, Retrieved on 19-03-2019
Personal tools