Skip to content

Iter3 users types and posts

Jump to bottom
Arik Levy edited this page Jun 18, 2017 · 1 revision

Table of Contents

Iteration Goals

we will put relevent to this user stories:

  • US5 Administrator will be able to add/remove a club house.
  • US15 guide will be able to send general messages to parents.
  • US8 Administrator will be able to delete messages.

Design

  • Home Page.
  • General messages section.
  • Nav-bar design - unread messages.
  • Login page - loading.
  • edit User page.
  • edit clubHouse page.

Functionalty

  • delete post from home page.
  • delete/edit club house.
  • dividing the app for users types.
  • delete/edit user.

Team Roles

Task Management

links to issues and Project Board

Total Estimation

2 weeks Until 11.6.17

Screen shots

before:

Iter3

after:

Iter3

Documentation

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 general message to main page - dynamic adding - 10 points
  • deploy images to firebase database when sending general message - 20 points
  • removing Users and Clubhouse trees - 20 points
  • adding loader to login page - 10 points

Total : 60 points

Code review

During Iteration 3 we encountered a number of small problems such as: deleting users who are associated to a clubhouse when deleteting that particular clubhouse , appending messages to the main page dynamicly and more ... because we are a team that usually work together, each one helped to each other in this problems.

when arik-le was working on the upload image - he encountered a problam , after uploading the image the src path could not be cleared , luckly royok17 add a good solution - here is the bug and the solution - Link

Author by: arik-le

Testing

Scenario for testing.

  • US5 Administrator will be able to remove a club house.
    • enter edit clubhouse section.
    • select clubhouse and press delete.
    • check if removed from clubhouse tree in DB.
  • US15 guide will be able to send general messages to parents.
    • enter send message section.
    • choose send general message and select clubhouse.
    • input data to the fields and press send message.
    • check if the parents got the message by checking their user's genMessage list.
  • US8 Administrator will be able to delete messages.
    • scroll in the main page and select message
    • press delete button.
    • check if deleted from the genMessage list.

update 10.6.17 ->all this scenrios are checked an verified.

Retrospective

planing VS Execution

  1. General Messages - in this iteration we worked on the generals messages to all clubhouse users (parents/teachers) , also we added dynamicly the messages in the home page , we acomplished all we wanted to do here , still have little problems in the image function but we will finish it soon. In this section we will let the managers socials workers and the guides in the organization to send all the activities in the clubhouses by upload a general messages with images to the perants and the teachers of the children.

  2. Initial Design

  • Edit User - DONE
  • Edit Clubhouse - DONE
  • Send Private Message- DONE
  • Send General Message- DONE
  • Get Private Message- DONE
  • Get General Message- DONE
  • Main Page - DONE
  1. Functionality
  • Delete User - DONE.
  • Edit user details -DONE.
  • Delete ClubHouse - DONE.
  • Edit clubhouse details - DONE.
  • Send general message - DONE.
  • Send private message - DONE.
  • Get Private Message- DONE
  • Get General Message- DONE
  1. nothing to compare with recent iteration (iteration 2)

what was working well

  1. accomplish the functionality of all what we have planned.
  2. make A good base for our application that will help next iterations.
  3. figure the best practice to work with the DB as early as possible.
  4. Division of work correctly to exact teams.

what we need to improve

  1. better design and more unified to all app.
  2. improve our code quality and make a code quality check.

Lecture implementation

during Lecture 7 - we learn how to better combine our code with other git commands , we learned about tagging your code when finishing a meaningful milestone like this iteration . also we used what we learned in Lecture 6 - VCS , how to work simultaneously on the code with several devlopers by working on different files and then combine by pushing and pulling.

Feedback from client

Hy everyone,we saw your last email and your last updates of of the application. we are satisfied from the of the app. we like so much the idea that behind the general messages. in the section of inbox messages, if its relevant to do some feature that we will know if i allready readed the message or not ....we know that you dont have time to the form section that we spoke in our meeting but it will so appriciate if it would be in the app. we want to say thanks again about all the hours that all of you guys, worked on it. a home from every child - received in 2.6.17

Deployment

you can see our application at this moment in this Link

Next Iter4-Feature Z Planning

In the next iteration we will work on:

User Stories

  • US10 parent will be able to watch new messages about his child's clubhouse.
  • US11 parent/teacher will be able to read personal messages.
  • US12 parent will be able to send feedback form about his child to the organization team.

Design

  • Design app for each particular user.
  • social worker multi choosing for clubhouse.
  • improve general message box and image upload.
  • change nav-bar to manager/social-worker.

Functionalty

  • social worker multi choosing for clubhouse
  • manager gets all clubhouse objects
  • testing the app extensively
  • dividing the app for users types
Clone this wiki locally