Release Planning - CMPUT301F14T06/Team06MapleSyrup GitHub Wiki
Sep 29: Project part 1 due date.
Sep 29: Project part 2 starts.
Sep 30:
- Read through the description of project part 2, and to post Release Planning on team wiki.
- The team leader should assign work to all team members.
Oct 01:
- Need to clarify user requirements, and to post Requirements Specification on team wiki.
- Discussing basic classes and relationships between them. Then, make a hand drawing draft for UML.
- Xiaocong should start working on the storyboard and mockup.
Oct 07:
- Xiaocong should finish the storyboard and mockup and post them on team wiki.
- Liwen should start working on the UML and the Sequence Diagram.
Oct 09:
- Liwen should finish the UML and the Sequence Diagram.
- Based on the UML, Anni should start working on the basic code structure of the app.
- Bicheng should should start working on jUnit tests of different methods.
- JingJing will writing the Glossary.
Oct 15:
- Most parts of the project part 2 are completed.
- Includes:
- Requirements Specification
- User Interface Mockup and Storyboard
- Release Planning
- Glossary
- Object-Oriented Analysis (UML, basic code structure: classes, attributes and methods)
- JUnit test
Oct 17: Project part 2 due date.
Oct 17: Project part 3 starts.
The current plan should be at least 75% completed before Nov 7. Based on team members's personal time schedules, the plan may be changed.
Oct 17 ~ Oct 31:
- Use Cases(In Requirements Specification) to Implement:
- Use case #1: BrowseQuestions
- Use case #2: ViewQuestionAnswers
- Use case #3: ReplyToAnswerOrQuestions
- Use case #4: MakeAQuestion We were having exams during these two weeks, therefore the use cases that can be implement are not that much.
Note: most of the use cases in this part are about views and activities. Because the classes work on user input and storage has not been completed in this part, we will use hard code to test this part.
Oct 31 ~ Nov 5:
- Need to make progress on main features.
- Use Cases(In Requirements Specification) to Implement:
- Use case #5: AuthorMakeAnswer
- Use case #14: NumberAnswers
- Use case #11: QuestionUpVote
- Use case #12: AnswerUpVote
- Use case #13: MostUpvote
Nov 5 ~ Nov 11:
- Need to make progress on main features.
- Use Cases(In Requirements Specification) to Implement:
- Use case #6: AuthorReplyToClarify
- Use case #7: AttachPicture
- Use case #8: RestrictPictureSize
Part 3 has finished. Except the use cases in the 3rd part, we have finished some more use cases.
New planning:
Nov 11 ~ Nov 20
- Use Cases(In Requirements Specification) to Implement:
- Use case #6: AuthorReplyToClarify
- Use case #7: AttachPicture
- Use case #8: RestrictPictureSize
- Use case #9: SortByImage *Fix errors
Nov 21 ~ Nov 30
- Use Cases(In Requirements Specification) to Implement:
- Use case #21: PushDataWhenConnectInternet
- Use case #23: SetUsername
- new use case in part 4
- Fix errors
- Vedio for our app
- PPT for our presentation in Nov 25
Part 4 will be finished on Dec 1
Dec 20 ~ Dec 23
- Group meeting: add new functionality in the next patch & optimize the current code.
Dec 26 ~ Dec 31
- implement new use cases
- refine user interface
- advertisement (video & demo)
2015 Jan 5 ~ Jan 20
- implement new use cases