Monday 3rd Apr
Wrapping up version 3:
User testing: Joseph + Berke
Tutorial document: Berke
Website updates: Berke
Monday 27 Mar
Version 3 discussion:
David: Will convert all buttons in app to the same style as the positive affirmation screen
Berke: Will implement a “first time use” popup notification message
Positive Affirmations: (David/Joseph)
- Remember notification settings and update UI at each load
- Use an 12 hour time with AM/PM selector, instead of 24 hr time
- Improve the layout of the "Notification frequency" area:
- Label all UI elements (ie. “month” “day” “hour” “min”)
-Labels appear/disappear as needed to match frequency selection
- Selection wheels should replace buttons (instead of appearing above them)
- Improve layout/alignment of UI elements
Square Breathing
- We need to meet the "analysis" requirement of the assignment:
- Add a button linking to a new “Stats” page
- Display average, minimum and maximum activity statistics
- Include a “Reset” button to reset all stats
- Show a random positive affirmation when the timer reaches 0 at end of the exercise
-> David: Will do this for Square breathing and grounding exercise
- Make vibration occur at middle of animation: Add a 0.8 second delay
- Bug: Background image doesn't display
- Put a border around the timer elements to frame them and show progress?
Grounding Exercise
- Make the UI more intuitive
- Display a countdown for each image of step (1/5, 2/5, 3/5...)
- Add borders framing empty image positions in the image bar. Images fill the
frames as each picture gets taken
- Show a random positive affirmation when the timer reaches 0 at end of the exercise
-> David: Will do this for Square breathing and grounding exercise
- Animate the gallery as it displays the images at end of exercise
Panic alert
- Make links look like links
Help screen
- Write help screen text (Adam)
All:
- Fix alignment between header sections
- Title/header text: Fixed header font letter clipping
Confirm user testing appointment with Dylan: Berke
User testing: Joseph + Berke
Update Trello (Adam)
HW5 documentation:
Adam:
- Requirements, Design, QA
- Presentation - PowerPoint
- Demo video
- Features fulfillment document
Berke:
Tutorial document
Monday 20 Mar
Joseph: Will email herbert re: Lack of contribution
Build review: Code complete?
Square breathing:
Deadline: Berke - tonite
- Make circles blue
- Match UI colors, font and layout to panic alert screen
- Update test code + write new tests
- Update test section in the QA Document
- Comment all code, including tests
Positive Affirmations
Deadline: Joseph, David: tonite
Grounding
Deadline: David: Tonite
Panic alerts
Deadline: Adam: EOD Tuesday
All: Fix compilers warnings
Discussion of version 3 UI improvements
Documentation:
Website: Berke
- HW4 page
- Meeting minutes
Monday 13 Feb
Website updates:
- Add new Meeting minutes
- Add "Update 3" details to the front page
- Typo: Assignment 2 page: "graphs" -> "graphs"
-> Berke/Joseph to complete immediately
HW4 Discussion
- Individual feature reports: Where are we at?
- David: Research only
- Joseph: Create/delete/infinite looping -> All in memory: Has not done loading/saving from file
- Berke: Animation started
- Adam: Completed first pass on help screen, dynamic UI base
- Group deadline for code complete: EOD Friday
-> Decision: Target iOS 9 and 10, regardless of technical difficulty
- UI: Everyone responsible for copy/pasting UI from Panic Alert storyboard
- Design feedback?:
- MUST be tested/work perfectly from iPad to iPhone 4
- Deadline for UI: Sunday
- Update automated tests for HW4
- Deadline: Tuesday
- Documentation:
- Updated 3 docs
- Feature delivery changes
- Spreadsheet: Deliverables
Monday 6th Feb
Build Review:
Presentation review
Testing discussion
Monday 27th Feb
Assign programming responsiblities:
Discussion: Stick to design document as closely as possible
- Use corrent naming conventions
- Must implement all features in "feature priority" section for HW3
-> Discord chat channel:
- Joseph will set up discord channel by end of meeting
-> HW 3 programming deadlines: DUE 8 MARCH = 9 days left
- All programmers to have completed 50% of work by end of day thursday 3rd
- Check in meeting after class on wednesday Mar 2nd
- All programmers to have completed 100% of feature work by end of day Sunday 5th March
- Final testing and integration testing: Monday march 6 to Wednesday 8 March
-> Other discussions:
- Deadlines are HARD, no excuses for being late!!!!
- Regular check-ins
- Ask for help if you're stuck
- Don't leave it to the last minute
--- END HW3
Monday 20th Feb
We need to email Dylan re: Acceptance testing
- Berke doing immediately
Proof reading:
- Adam will complete a pass by EOD Thursday 23rd Feb
- David will complete a pass before EOD Wednesday 22nd Feb
Requirements doc - Tutorial images:
- Joseph will insert images immediately after meeting today
HW2 Citations:
- Everyone responsible for creating their own
- Berke: Will have his done Thursday PM
Requirements document:
- Definition of grounding - Adam will complete
HW2 Submission
- Adam will submit all files by EOD Thursday
HW3
- Need to start programming ASAP
- Joseph, Berke, David will start programming Saturday: Basic page framework
HW2 Website updates:
- Fix issues from HW1
- Upload 3 new docs (PDF) - Adam will provide files by EOD thursday after submission
Tuesday 14th Feb:
Group review of all 3 documents.
Joseph: Did not complete
Final draft due by Monday.
Discussion: Starting work early as to avoid delays to deadlines.
Monday 6th Feb:
- All group members taking notes: Individual commitments and deadlines
- Should we meet Monday 13th Feb (during spring break)?
Yes - HW2 due friday 24th (3 wks)
HW2 Planning:
1) Requirements document ("User manual + requirements document")
-> David and Joseph
2) Design document
-> Adam
3) QA Plan
-> Berke
HW2 Deadlines:
1st draft:
Due Monday 13th Feb
Every section is to be nearly completed, unless specifically blocked by some other portion of the document
2nd draft:
Monday 20th
"Final" document version. All work to be completed in full
Proof reading:
Feb 20th to 24th.
HW2 Notes:
-> We must all refer to the specific textbook sections referenced by Herbert in the HW2 specifications for all document writing
-> If a team member does not adhere to the specific examples provided by Herbert in the HW2 documentation, they’re fully responsible for re-doing the work
Organization Notes:
The group will start taking advantage of Trello for tracking tasks
-> Input current tasks into Trello
David will clean up outdated Slack pins