CFR - oronsa/shoulder2shoulder GitHub Wiki

Client's Final Requests

Table of Contents

Iteration Goals

  • This iteration main goal will be to present the client with a raw product towards completion;
  • Asking for fine tuning regarding the access control functionality
  • Get a review regarding the website UI and adjust accordingly.

Iteration Roles

  • Amir Lavi and Oron Sason: Controllers, Services and Back-end bugs detection/fixes
  • Shimri Peretz and Maen Abu-Gosh: Client side UI and Front-end bugs detection/fixes

Iteration Current Tasks

Screenshots before Iteration

https://github.com/oronsa/shoulder2shoulder/blob/master/Doc/Images/Iterations/iteration-4-before.jpg

Screenshots after Iteration

https://github.com/oronsa/shoulder2shoulder/blob/master/Doc/Images/Iterations/iteration-4-after.jpg

Completion Points Assumptions

  • Pages email redirecting organise - 10 Points
  • Super Admin's pages finalise - 18 points
  • Forgot password mechanism - 20 points
  • Transforming the Admin's options - 18 points
  • Users sessions - 20 points
  • Filter by dates - 16 points Total: 102 points

Testing Methods

  • Server side - Printing to console by "console.log(..)" results output to NodeJS command prompt
  • Client side - Opening Goggle Chrome's developer console and applying breakpoints at desired line to view data during run time
  • By the creation of mock objects by [mLab's] (https://mlab.com) we are able to simulate a real environment used by the actual users and see what happens when we retrieve their data from the database during run-time

Sprint Issues

  • Team Meeting

  • Went over the entire application pages dividing the work left between the team members

  • Client Feedback

We gave the client credentials for the website. The client was thrilled about the new organisation website, we told her to play with it a little bit let us know if she can find any bugs (which will be), either way we'll stay at her service after the semester is over.

Project Summary

  • Review

This course was an adventure for us. We worked as a group from the beginning to the end. We were Four, motivated, hard-working students with weekly meetings, late night phone calls, endless code documentation pages, etc.. Combined forces to help an Organisation that is already doing so much for the community and really deserve to enjoy a worthy application which can make their contribution much easier. We formed into two groups - Front-end and Back-end - this way it felt right for us, this proved it self along the road; In the first month it was quite hard to learn technologies and at the same time divide the work among us. When we got use to it, each and every one of us knew exactly what to do, and how. Now we can actually see the product and its quite amazing. After showing it to the client, which went over the roof, we are even more excited and very satisfied with the result.

  • Team Spirit

As mentioned above, in the first month we were having difficulties learning the new technology. This affected directly on the team spirit, Shimri and Maen started to work on the Front-end, but there was no back end to connect it to, which caused stress and arguments among us, we even thought switching the frame work a few times. History shows that with diligently, one can accomplish anything he wish for - As for us; Once we've learned how to use the framework, the project became meaningful, enjoyable and very tutoring for us. Eventually, we got use to work with each other, knew everyone's ability and encouraging each other in the process.

  • Development Process

  • Framework chosen - Mongo, Express, Angular and Node - MEAN Stack

  • Detecting and describing the best we can the features we need to develop.

  • Develop the bare-bone of the project to get the ability to expend the code easily as the project progresses.

  • Make sure the Client is aware of the application features and our tasks.

  • Weekly sprint meetings to align our work and expectations from each other.

  • Fixing minor bugs on-the-go as they occur.

  • Self team check up at each other in the weekly intervals - all team members needed help on some point with their work.

  • Don't bite off more than you can chew - at first our tasks were quite huge because we didn't have the knowledge to assess them correctly. As the project progresses we've learned how to estimate each task more accurately.

  • Reflection

  • The Client should be the first priority - we met with our client only three times, but we kept her posted and simulated to our progress with the live application over the phone every week. For those reasons our last call with the client was very touching, she was very enthusiastic with the result, as well as the organisation's employees. This made us feel that we really made a change in the organisation work process and in the families lives.

  • Our chosen framework was new to us, as well as the project development process. We've learned so much in the process, starting with advanced programming, internet security, working in front of an actual client and all the way to bureaucracy administration. The most noticeable thing that happened for us was in the end of the second iteration, we found out that going over the assignments, thinking about user's stories, talking to the client, meeting every week, developing code, etc.. is becoming more and more as natural to us. That point made us feel like a true software engineers that are taking an idea from scratch and bringing it to life as a real tiny company, rather then programmers who only code. We did our best following the bureaucracy, along coding the user's stories to features into the application.

  • The Bureaucracy was perfect (Some of us work in web development). It is very similar to what you actually do in the real world, the only issue was the time. We thought that this course would function much better in an annual program. It's hard to develop a real product to real users in such short period of time along with other numerous courses.