Week 3 Summary

Week 3:

Sunday (5.11.17) :

The week started with a meet & greet with the product's client - Professor Rakefet Ackerman. In the session with Rakefet we introduced the team and the team host and then Rakefet explained in great detail the main requirements she has of the product. She talked a lot about the products she is currently using and the process she is going through every time she wants to create a test for her subjects, and it was very clear to the team why she desperately needs the new product we are designing. She went ahead and showed us which features are crucial to have in the product, mainly, a few important features are:

• The time measuring of different parts of a test.
• The database we should maintain for Rakefet to draw information and test results from.
• The so called "distractions", the different types and the way Rakefet wants to have them organized in a test. In the meeting, almost all the questions we prepared were answered, and those that weren't are such that there are topics that we should investigate and read on and decide for ourselves, of course while running our decisions through Rakefet for reviewing and approving.

Monday (6.11.17) :

Monday noon was when we had a team meeting (without Tanya) for catch-up and some summary of the previous day (12:30-13:30), since we needed to fill Ben up with the details of the meeting with Rakefet. After that, we met with Tanya to discuss the main topics and ideas we are taking away from the meeting with Rakefet. Tanya has also very graciously gotten us information about certain tools and/or frameworks to help us with the implementation of some parts of the project. We continued to discuss about which parts and which demands and requirement are feasible in our opinion. Taking Rakefet's final product into account, we did have to let go of a few feature right off the bat because of their incredible complexity (we can only afford to waste so much time on crazy GUI tools to modify appearance of a test in one semester... or even two..), and as Tanya has stated, it is perfectly okay to tell Rakefet what we think we just cannot do. We settled on a few major topics and features we must investigate and read on to let Rakefet know how exactly we are going to implement these features.

Lastly, as Tanya said, we agreed to build a full HLD document of the project by next week's meeting. After Tanya has left, the team stayed and we discussed about dividing the work on the HLD between us. The division is as follow:

• Ophir - Investigation on how to integrate the web application (the technology we will use for writing the web application), with the server side logic of the software. Also how to interact with different types of servers via the PL we will work on our server side logic (probably Java...).
• Mark - For the entire implementation of the project, investigate on which basic modules will probably be needed to implement the logic of the web application.
• Ben - For the entire implementation of the project, investigate on which basic modules will probably be needed to implement the GUI of the web application.
• Daniel - Investigation on different platforms for writing and implementing the web application. Need to find examples we could all rely on when explaining to Rakefet which platform we did choose. (Reminder - Rekefet will probably want to see the code and change it to her needs, so it does need to be a fairly easy and understandable platform, with tons of sources online to help her with it!).
• Guy - Investigation on working with different types of data servers (SQL, ACCESS and so on...). Also which server will deploy out web application.
• Peer - Investigation on server infrastructure, which means going to the faculty where they hold the servers and checking with them if what they have there is enough to satisfy the requirements of the software.