In this iteration we begin to build the infrastructure of our application development. This will be expressed by focusing on a number of topics of development:

1. We will continue to improve our knowledge in Angular 2.0, the development environment with which we work, a new language almost unknown to us, and we will have to learn it well.
2. We will devide team roles.
3. Create task mangment tools to make a user stories
4. Improve the prototype of the system.
5. We will begin preparing the infrastructure for the next iteration.

• US1 The administrator will be able login to the system.
• US2 Student will be able login to the system.
• US3 Teacher will be able login to the system.
• US4 Parent will be able login to the system.
• US5 The administrator will be able to create new users.
• US6 The administrator will be able to delete users.
• US7 A student will building a schedule.
• US8 A teacher will create a schedule according to student choices.
• US9 A student will be able to watch private messages.
• US10 A parent will be able to watch private messages.
• US11 A teacher will be able to watch private messages.
• US12 The administrator will be able to watch private messages.
• US13 All users will be able to watch public messages.
• US14 The administrator will be able to write messages.
• US15 A teacher will be able to write messages.
• US16 A teacher will be able to delete messages.
• US17 A parent will be able to sign the certificates he was asked to sign.
• US18 The administrator will be able to reset the user password.
• US19 A teacher will be able to enter the gallery and view pictures.
• US20 A student will be able to enter the gallery and view pictures.

• Yaki - The representative of the team who always in contact with the organization. to.
• Michal - responsibilty to manage the schedule time of the development.
• Miriam - The "brain behind the scene" responsibilty of building the complexity algurithms in the system.
• Esty - The team's design artist - responsible for everything related to the app design ,responsible also for building the application according to user convenience.
• Rotem - The project's safety officer - responsible for checking the performance of the tasks according to the schedule and performing the tests of the system.

• SRS-documantion
• SDS-documantion
• User manual
• Developer manual

The current tasks, and their matching iterations and priority can be found in the issues page

The main project Kanban board can be found here

Each iteration estimation is set in each milestone

Each meeting summary and reviews can be found in the respective iteration documentation page on the wiki starting from the first iteration.

The number of admin users will be single one. This user is in charge over managing the system and will have the widest access to the system compared to other users. The administrator is the only one who can create new users (such as teacher, parent and student) including the user name and password, delete users, control over the messages system and the gallery.

The number of teacher users will be about 100. The teacher is responsible for making the individual study program for each student, monitor the student's experiences in school, uploading photos to the gallery, create an individual life story for each student, and send messages to the parents about public information and personal.

This type of user has a large number in our system, the number of student users will range about 720-1000 students per period (40 students in class double 6 classes for period double 3 years). Student needs to fill in data about himself – which courses he prefers to learn, the best way for him to learn, what his strengths are, review his personal studying program the teacher build for him and the experiences he had in school through a photo gallery and "life stories" that the teacher created for him.

This type of user has the largest number in our system. The number of users will be around 1500 per period (two parents for each student). This user will have the ability to see his child experiences in high school (life story's only). As well they will receive general messages and personal messages from the administrator and teachers that some of them will have to sign.

• Visual Studio Code
• Firebase Database
• angular

In this iteration, we will start building the system's main page, which is the user's login page to the system. We will start building the main screen of the application after connecting each of our types of users: home page for administrator /teacher /parent /student.

The first iteration planning can be found here