Iteration 4

Iteration 4 goals:

• Duty and degree of employ will be defined.
• Employ can cancel lessons, update information, confirm contract and put contract into effect.
• Customer has the option to buy a new contract, by the types of contracts.
• Having option to see a constant list of teachers.
• Having an option to contact with the gym / open an email at the user with the address of the gym inside the mail.
• Having an option to Access roads to the gym with google maps.
• Having the option to see history of lessons separated from list of future lessons .
• Having the option to read information about the importance of the health, sport and exercise.

###Information about the tasks: Huboard
Issues
Our gitter

###Testing optional tests on the main tasks of this iteration:
1.
test: Employ cancels a lesson
expected result:
-when Customer wants to register to a lesson that one does not exist in the lesson list.
2.
test: Customer buys a contract.
expected result: it will be shown in personal details that contract is in effect
3.
test: adding a teacher to db
expected result:
-in teachers list we see him and his duty and degree
4.
test: Customer clicks to buy a contract
expected result: He will get a list of option according to the types of contracts
5.
test: click list of teachers in navbar
expected result: A list of all teachers in the gym will be shown
6.
test: Click contact in contact page
expected result: An email at the user will be opened with the address of the gym inside the mail
7.
test: Click show map
expected result: An access roads to the gym with google maps will open
8.
test: Click show history in users lesson page
expected result: A list of all lessons user joined will show
9.
test: Click on articles in navbar
expected result: An information page about the importance of the health, sport and exercise will be shown

###screenshot of the huboard before of this iteration

###screenshot of the huboard in the end of this iteration

###conclusion of the iteration: We finished all the tasks of past iterations, and added more that were important for the perfection of the project.

There is still the risk that we won't manage to accomplish the project till the end of the semester (which is really very close...) so all the team must be responsible and care about our project: checking mails twice a day (at least), doing their tasks from the huboard not in the last moment...

###Meeting and discussion summary, feedback of the customer: *We decided to organize the work in hierarchy order-there are some tasks that have to be done before another *We straightforward line with every body to make sure that we all know visual studio, c# , git etc.

##Project Summary Report

###Manual:

user manual

###Team's Spirit

At the beginning ,we have used the Code of Conduct for the project being at progress. We all believed in "if it ain't broke, don't fix it". The reason we think it is relevant here is because we need to do maximum work in minimum time. We make efforts to preserve the quality of code, but one way or the other we prefer to finish the work and do code refactoring in iteration 4 as planned. Moreover, we believe in "the idea is that quality does not necessarily increase with functionality", which reinforces the idea of prefer working and less quality instead of not working and more quality. Of course, we maintain on naming conversion, in order to make our code readable and understandable.

###Developing Process

The develop progress was divided into 4 iterations.

Summary for all iterations:

Iteration Duration - each iteration took about less then two weeks, it was enough time to finish all iterations' tasks (it's all about manage your time right). Number of iteration - the number of the iteration was enough, it enabled us to divide the main tasks into sub-tasks per iteration. Every iteration had a context, an unique milestone, that expresses a main idea in the project.

• If there are things we should learn before comitting the changes. Iteration conclusion - helped us to plan our next iteration better, and learn from the good and wrong in previous iterations.

###Project Reflection