iter2 - esty6u/STORY-OF-LIFE GitHub Wiki

Iteration Goals

This iteration is very importent - our main goals is to design the main app functions , also to remove objects from the firebase DB.

we will put relevent to this user stories:

  • US5, US6 Administrator will be able to remove users.
  • US7 A student will building a schedule.
  • US8 A teacher will create a schedule according to student choices.

Design

  • Administrator, student, teacher Home page
  • student - schedule
  • teacher - schedule according to student choices.

Functionalty

  • remove users.
  • Receive schedule from student.
  • Teacher - create schedule to student

Initial Design

  • App Login Page for administrator user contain two main functions – 'delete user'
  • App schedule page for teacher /student separately.

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

Total Estimation

  • 20/5/18

Screen Shots of Task Board

  • before: before

  • middle: mid

  • after: after

Documantion

CRC Cards

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

Points summary

  • add button to delete users.
  • Deploy initial admin's setting page with basic working functionalities.
  • Save manually users on database.
  • Create the functionality of building the student's schedule.
  • Create the functionality of building the teacher's schedule..

Code review

During Iteration 2 we encountered a number of small problems in: delete user to the db, Extract information from the DB to build schedule and more. because we are a team that usually work together, each one helped to each other in this problems.

Testing

Scenario for testing.

  • US5, US6 Administrator will be able to remove users - button to delete users . - delete users from DB.
  • US7 A student will building a schedule.
    • Implementing a button to create a schedule.
    • Saving student choices in the db.
  • US8 A teacher will create a schedule according to student choices.
    • Pull student choices from the db.
    • Create schedule file for each student and upload the files to DB.
    • pull student choices from the db.
  • all this scenrios are checked and verified.

Deployment

you can see our devolopment at this moment in this Link

  • Not yet available

Lecture Implemention

we learned several things from the lecture, for example: Lecture 5 - planning, we learned to plan our time more effective by sperating major assignments to little ones and because of that we could spread them to all team members , also we scheduled the entire iteration by steps we need to finish in a period of time , becasuse of all of this implementions we achived a lot and finished most of our work for this iteration.

Feedback from client

The customers liked what we had done so far, including the first iteration. They liked the pages of the teacher, student, parent and the administrator. They less liked the background of each page and asked us to change the background to light purple on all pages.

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.

Next Iteration

In the next iteration we will work on:

User Stories

  • 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.

Design

  • Administrator, student, teacher messages page
  • parent - sign about the certificates he was asked to sign
  • teacher - schedule according to student choices.

Functionalty

  • System messages.
  • Parent certification system.