Iter1 - esty6u/STORY-OF-LIFE GitHub Wiki

Iteration Goals

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) and the initial Database system.

relevant user stories:

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.

Initial Design

General Nav-Bar for all User types
App Login Page for administrator user contain two main functions – 'add new user' and 'delete user'
App Home page for teacher /parent /student separately.

Funcionality

Team Roles

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.

Task Management

Main Task Board

Total Estimation

8/5/18

Screen Shots of Task Board

before:
middle:
after:

Documantion

CRC Cards

in this iteration we will focus on User and Admin CRC Cards. you can see the cards in this Link.

Points summary

Add an login page
Deploy initial admin's setting page with basic working functionalities
Save manually users on database
Setting up the development environment

Code review

During Iteration 1 we encountered a number of small problems such as: designing the login page, building the categories for each function in the system, register users to firebase and more . because we are a team that usually work together, each one helped to each other in this problems.

Testing

Scenario for testing.

US1 Administrator will be able to log in into the system
- create administrator user in the system.
- add administrator user to database.
US5 Administrator will be able to add user to system
- check that administrator user could be able to create another user.
- check that administrator user could be able to add created user to database.
US2 , US3 ,US4 parent,teacher, Student wiil be able to log in into the system.
- add parent/teacher/student user to database.
- Restrict permissions to parent/teacher user according to organization requirements.
all this scenrios are checked and verified.

Deployment

you can see our devolopment at this moment in this Link

Not yet available

Lecture Implemention

In this iteration we worked a lot on imagine how the database will be , we implemented a trees to check how the DB works at firebase, and checks how to extract or insert data to that DB , after a lot of reading we add a success on storing users in the DB for our login method , what we implemented from the Lecture was team work and deep research on what we need, we were very glad with this results and we agreed to continue with this path.

Feedback from client

The client does not find time to meet with us to provide us with an opinion on the project's progress so far.

Process&Methods

we all using Visual Studio Code to work on the app, our main programming language is angular2 and we merge the codes with pull and push commands by using the git commands and commit them.

Risk Treatment

Lack of knowledge of developments software - Lots of reading on internet really improve us and our knowledge with visual code tools.
Unfamiliarity with the development environment - Pretty the same as above.
Going off schedule - Great scheduling and lots of hours working on app would make us complete the app at the time.