Skip to content

Release Planning

Jump to bottom
htbauder edited this page Nov 22, 2017 · 11 revisions

Major Use Cases / Minimum Viable Product

Project Part 4:

Habits

  • UC 01.01 Add New Habit
  • UC 01.02 View A Habit
  • UC 01.03 Edit A Habit
  • UC 01.04 Delete A Habit
  • UC 01.05 ToDoList For Today
  • UC 01.06 View My Habits List

Habit Events

  • UC 2.01 Add New Habit Event
  • UC 2.02 View Habit Event
  • UC 2.03 Edit Habit Event
  • UC 2.04 Delete Habit Event

Profile

  • UC 03.01 User Profile

Habit History

  • UC 04.01.01 View my habit history
  • UC 04.02.01 Filter my habit history list
  • UC 04.03.01 Search for habit event

Project Part 5:

Habit Following and Sharing

  • UC 05.01.01 Request to Follow
  • UC 05.02.01 Grant Permission to Follow
  • UC 05.03.01 Following Status

Geolocation and Maps

  • UC 06.01.01 Attach Location
  • UC 06.02.01 Show Event on Map
  • UC 06.04.01 Highlight Event

Offline Behaviour

  • UC 07.01 Offline Behavior

External Milestones - Project Parts

Project Part 0: Submit Team

   Due: Friday, 29 September 2017, 4:00 PM

Project Part 1: Create Team Repo

   Due: Friday, 6 October 2017, 4:00 PM

Project Part 2: Requirements Analysis, Prototyping, Project Plan

   Due: Friday, 13 October 2017, 4:00 PM

   1.   Requirements Specifications
   2.   User Interface Mockup and Storyboard
   3.   Release Planning
   4.   Glossary and Information Sources

Project Part 3: Object-Oriented Analysis and Design

   Due: Monday, 23 October 2017, 4:00 PM

   1.   Addressing Feedback
   2.   Object-Oriented Analysis and Design
   3.   Unit Testing

Project Part 4: Half-Way Prototype

   Due: Monday, 13 November 2017, 4:00 PM

   1.   Addressing Feedback
   2.   Code Base of Prototype
   3.   Code Documentation
   4.   Test Cases
   5.   Object-Oriented Design
   6.   Release Planning
   7.   Reuse Statement

Project Part 5: Final Prototype

   Due: Monday, 4 December 2017, 4:00 PM

   1.   Addressing Feedback
   2.   Code Base of Prototype
   3.   Code Documentation
   4.   Test Cases
   5.   Requirements Specification
   6.   Object-Oriented Design
   7.   Planning
   8.   Reuse Statement
   9.   Demo Presentation
   10.  Video Demo

Internal Milestones - Weekly Sprints

Oct 9th - 13th 

   External Milestone Due: Project Part 2

   1. Use Cases Detailed
   2. User interface mockup created
   3. One storyboard sequence created
   4. Plan major use cases and user stories for Project Part 4
   5. Plan what will be deferred until Project Part 5
   6. Define special terminology in glossary
   7. Find and list useful references and competitive products
   8. State open sources license
   9. Upload all proceeding objectives to Echoes' GitHub repo and wiki

Oct 16th - 20th 

   1. Implement TA feedback into items from Project Part 2
   2. Document object-oriented analysis
   3. Create UML class diagrams
   4. Start creating classes and activities to meet Project Part 4 standards
   5. Write unit tests for model classes
   6. Check that requirements for Project Part 3 are in the Echoes' GitHub repo and wiki
   7. Project Part 3 finalized

Oct 23rd - 27th 

   External Milestone Due: Project Part 3

   1. Project Part 3 polished and submitted
   2. 50% Classes and activities to meet Project Part 4 standards complete
   3. Ensure completed classes and activities are fully documented
   4. Update test cases and UML class diagrams to maintain parity with completed classes

Oct 30th - Nov 3rd 

   1. Implement TA feedback into items from Project Part 3
   2. 75% classes and activities to meet Project Part 4 standards complete
   3. Ensure completed classes and activities are fully documented
   4. Update test cases and UML class diagrams to maintain parity with completed classes

Nov 6th - 10th 

   1. 100% Classes and activities to meet Project Part 4 standards complete
   2. Ensure completed classes and activities are fully documented
   3. Update test cases and UML class diagrams to maintain parity with completed classes 
   4. Ensure that code base is synchronized to test cases and UML documentation
   5. Make sure all software reuse is properly documented
   6. Give credit to original developers and obtain approval for use of third party libraries
   7. Check that requirements for Project Part 4 are in the Echoes' GitHub repo and wiki
   8. Project Part 4 finalized

Nov 13th - 17th 

   External Milestone Due: Project Part 4

   1. Project Part 4 demoed
   2. 50% Classes and activities to meet Project Part 5 standards complete
   3. Ensure completed classes and activities are fully documented
   4. Update test cases and UML class diagrams to maintain parity with completed classes

Nov 20th - 24th 

   1. Implement TA feedback into items from Project Part 4
   2. 75% Classes and activities to meet Project Part 5 standards complete
   3. Ensure completed classes and activities are fully documented
   4. Update test cases and UML class diagrams to maintain parity with completed classes 
   5. Plan live presentation
   6. Start working on demo video

Nov 27th - Dec 1st 

   1. 100% Classes and activities to meet Project Part 5 standards complete
   2. Ensure completed classes and activities are fully documented
   3. Finalize demo video
   4. Update test cases and UML class diagrams to maintain parity with completed classes
   5. Make sure all software reuse is properly documented
   6. Give credit to original developers and obtain approval for use of third party libraries
   7. Check that requirements for Project Part 5 are in the Echoes' GitHub repo and wiki
   8. Project Part 5 finalized

Dec 4th 

   External Milestone Due: Project Part 5

   1. Project Part 5 demoed
Clone this wiki locally