Skip to content
Afek H edited this page Jun 9, 2016 · 11 revisions

Iteration 2 - Client Side Experience

Iteration Goals & Main Issues

  • Simplify the website use in the client side.
  • Enable to users to sign up the events in the site.
  • Display the mlab contents to the client side.
  • Enable edit existent content.
  • Add google account login API to allow only the crew members to login the management panel.

Iteration 2 Milestone

Iteration roles

Role Assign To Link
Edit existent content Ori Issue
Event sign-up Tal & Dorian Issue
Simpify website use Matan Issue
Display mlab content Ori Issue
Google account service API Afek Issue

Retroprespective

After the Iteration 1 conclusions, we emphasize to have a realistic time estimation. About every issue we had in this iteration, we analyzed in depth the issue's requirements. Therefore we succeded to have a good time estimation and to have a good progress output. To the next iteration we will pay attention to divide the issues equally between all the crew members, to have the best progress we can achieve.

Code Reviews

From To Link
Dorian Ori Link
Afek Ori Link
Afek Dorian Link
Afek Dorian Link
Dorian Afek Link
Ori Afek Link
Afek Dorian Link

Testing

1. Google login test

2. Display content to client side

3. Edit existent content

4. Event sign-up (via e-mail)

Testing Method

We are testing our program and the server & client request and resposne by log the data to the console. To every function we create we are log to the console that the function has been called and the data which it get and post (if exists) In addition, we tested the google api by trying to login to the management panel with a google acount which is not defined as a crew member.

Next Iteration Planning

Iteration 3