Skip to content

Meeting Note

Jump to bottom
Lily(Zhi) Li edited this page Mar 3, 2017 · 37 revisions

meeting note

Feb/08/2017

Discussed and designed the UIs together, and got a breif UI pattern.

Main UI: login(sign up; sign in) (forgot password?? Remember user?? ) (unique user name)

  • Sign_Up_Activity:
  • User name
  • (Date created?)

(After logging in)View_TotalActivity:

  • Mood History(list[sorted by date and time, most recent coming first]) + map (users? Or the following user’s?) plus sign at right top corner(change to Create_Activity)
  • View(01.04.01)(change to View_Activity??)
  • Edit(01.05.01)
  • Delete(01.06.01)
  • Filter function

(After clicking VIEW Option)View_Activity(TBD):

  • Edit(01.05.01)
  • Delete(01.06.01)

Feb/09/2017

Discussed and designed the UIs together again, and came up with an almost completed UI plan.

Create_Activity(Mood_Event):

  • Current Date and Time, (required 01.01.01)
  • Emotional state (required 01.02.01):
    1. Includes: anger, confusion, disgust, fear, happiness, sadness, shame, and surprise.(at least)
    2. Depicted and distinguished by：consistent emoticons and colors in any view.
  • Optional trigger, ????(required 01.01.01)
  • The reason:
    1. Textual (limit to 20 chars or 3 words ) (is this optional???) (02.01.01)
  • A picture: (under 65536 bytes ~=65KB) (is this optional???)(02.02.01)
  • Optional social situation: alone, with one other person, two to several people, or with a crowd.(02.04.01)
  • Optional location:(06.01.01)
  • Filter_Activity(04.02.01 to 04.02.03)
    1. Right pull menu
  • My_main_page_activity()
    1. Only check own post
    2. follower and follow
    3. Filter Function

Feb/15/2017

We discussed about how to write User Cases, we decided to number them according to function category. There are six category in total:

  1. About mood event (creation, deletion,edition etc.)
  2. About user input of mood event specifications
  3. Login option
  4. Filter
  5. Follow relationship
  6. Map
  7. Synchronization
(Refer to Requirements Speciation-> Use Cases)

We also discussed about release plan.

We decided to release the following function on project part 4:

  • Login page
  • Edit Activity
  • Main Activity
  • Filter Activity
  • Friend Activity

We decided to release the following function on project part 5:

  • Map Activity
  • Synchronization Activity

(Refer to Release Plan)

We have also started a prototype of StoryBoard.

Feb/20/2017

Assigned task to each person (UI skeleton):

  • Mengyang: add, edit, view friend activity
  • Xinlei: Home Screen(Main Activity)
  • Zhi:Signin, signup, user, moodEvent
  • Yipeng: Friend
  • Heyue: Filter, Map

Feb/22/2017

  1. UI skeleton finished(code)
  2. merged to github<>
  3. initial thoughts about UML

Feb/25/2017

  1. UML finished
  2. upload unit tests
Additional models: - Xinlei:MoodEventList - Zhi:UserList

Mar/2/2017 (With Shida)

  1. What we have finished (see meting notes above)
  2. Try to start elastic search first because it is very timie consuming server index,type id... user the unique index for our own team.
  3. Discussion about project 2 feedback (UC) and elastic search

Mar/3/2017

Clone this wiki locally