Team Client Meeting Number 2: Simulation and Beta Version Requirments - TechnionYP5779/eduval GitHub Wiki

Location: Taub 201 Date: 22.01.19 Time: 15:30-16:30

Attendance:

1. Eric Kiel
2. Daniella Dagan
3. Ilia Smagloy
4. Elad Yundler
5. Anny Firrer
6. Boris Shtivelman (Client)
7. Yuri Finkelshtein (Client)

Boris gives the intro speech (He gave last time, read summary of wiki number 1). Part 1: Simulation The Client gives smartphones to the team, and points out that they bought the smartphones because in real simulations most of the kids/students appeared to have problems with the instalation; low battery, old version of Android, IOS, etc. Simulation runs. All of the team logged in. Noticeable that the system takes time to update, and that group selection goes one by one. Teacher screen is organizable by hand - the teacher can change the structure as they want.

Q: Why do you need the table number if so?

A: For big classes, new teachers and etc.

Q: If I'm a bad students that makes problems in the lessons. I still have an interest to show up?

A: Yes, we believe that if so he'll earn less. Note: Notify teacher currently doesn't work.

Q: For the student to notice his points he need t o look on the screen on the time. Why shouldn't he be able to see it all the time? (In the shown demo the given points dissappear after a few seconds). Why not as a notification?

A: We belive that this is the way. But it is up for discussion. Maybe with sounds? Followup from team: ADHD prevents sounds. Client points out this is up for discussion.

Q: What is the biggest problem with the current demo?

A: First, the device problem already spoken of. Second - storing the data; Currently nothing if left after a simulation. Database is the thing we lack the most, client can't analyse currently or preserve any information so nobody has actual motivation currently. We would like at the end the teacher and student to recieve data - rewards for current session, but also graphs over time - for the teacher and the student to understand and learn from!

Q: Is there anything you want to preserve?

A: Time of lesson left - is good (sandclock). Emojis for feelings in one area and one rewards area.

Q: You shouldn't judje preformace by this application only. There are other ways to be active. What about silent kids?

A: Yes, not only - but this should be a tool for many kids that we don't know about currently. For the silent kids? There is the notify button. We cannot escape being unfair - but we can solve it partialy.

Q: How does the teacher work with the application simultaniously?

A: Currently you need 2 people - one with the app and one teacher. We would like in the future to move to a tablet, or maybe a phone with voice recognition!

Q: What about notify? with phones it shall be to hard?

A: No, it shall be possible. We tried already, and we'd like it to be a possibility.

Q: What else?

A: An administrative screen/mode where you can sign in a student and else. Should be different from the teacher screen.

Q: What does 'sitting mode' mean?

A: Ordering the sitting and the gui.

Q: No 'Journal' During the lesson?

A: We're sure that this will be a problem for the students.

Conclusions and Subjects for Further Discussions:

  1. Anny suggests making the application in Web in order to evade the technological problem with different smartphones described in the beginning of the first part.
  2. Timer is easier than a sandclock. Client says he prefers sand clock but this is ok for v.01
  3. Graphs and date of performances after lessons both for teacher and student to see! By minutes of lesson, by lessons in year and etc. etc.
  4. Connection to the lesson from far away?
  5. Voice recognition
  6. Phone/Tablet app for the teacher.
  7. Micro Transactions? Actual Transactions?
  8. New App? Old Parts?