Release Planning - CMPUT301F13T13/StoryHoard GitHub Wiki

By Monday Oct. 28th, 2013

Finish following use cases:

  • Use Case 1: addStory Done
  • Use Case 2: addChapter Done
  • Use Case 3: allowIllustrations unecessary
  • Use Case 4: addChoice Done
  • Use Case 5: browseAuthorsOwnStories unnecessary
  • Use Case 6: browseChapters Done
  • Use Case 7: readStory Done
  • Use Case 8: readChapter Done

Front End:

  • browseAuthorStoriesActivity (main menu): Kim all the browse story activities became ViewBrowseStories
  • browseChaptersActivity: Kim Done
  • displayStoryActivity: Alex (just the main page of story) and Kim Done
  • displayChapterActivity: Kim Done
  • StoryApplication: modified by everyone as needed
  • View interface: Josh

Back End:

  • Set up database (schema, dbHelper, singleton): Steph + Ashley Done
  • Model : Steph
  • Chapter class : Ashley Done
  • Chapter manager class : Steph Done
  • Story class : Steph Done
  • Story Manager class : Steph Done
  • Choice class : Ashley Done
  • Choice Manager class: Ashley Done

By Nov. 4th, 2013

Finish following use cases:

  • Use Case 9: editStory Done
  • Use Case 10: editChapter Done
  • Use Case 13: viewIllustrations Done

Front End:

  • start on browse published (josh), browse cached (Kim) unecessary
  • editStoryActivity: Alex Done
  • editChapterActivity: Kim Done
  • editChoiceActivity: Josh
  • searchStoryActivity: Kim Done

Note: the edit___Activities also now encompass what were the Add____Activities.

Back End:

  • integration from last week's back end classes with the activities: everyone
  • GeneralController: Steph + ashley Renamed to SHController Done
  • MediaManager: Steph + Ashley Done
  • MediaClass: Steph + Ashley Done

General:

  • have addressed feedback from TA
  • Documentation from everyone!
  • JUnit tests from everyone!

By Nov. 10th, 2013

Use Cases:

  • Use Case 12: addIllustrations Done
  • Use Case 15: takePhoto Done
  • Use Case 18: viewPhotos Done

General:

  • Front end + backend working with each other completely for work done so far
  • Get broswse gallery working
  • Front end clean up the code a bit (Kim, Josh, Alex)
  • be working on new requirements
  • catching up on any work not completed by previous deadline

By Nov. 17th, 2013

Finish following use cases:

  • Use Case 16: postPhotos Done
  • Use Case 17: publishStory Done
  • Use Case 19: browsePublished Done
  • Use Case 20: cacheStory Done
  • Use Case 21: browseCached Done
  • Use Case 22: searchStory Done

Front End:

  • testing: all (includes cleaning up unit tests)
  • browse + search published stories functionality tests
  • SearchActivity: Kim
  • SearchResults: Alex

Back End:

  • deal with server integration (serverManager class and methods): Steph + Ashley Done
  • elastic search: Steph + Ashley Done
  • Try and get all tests passing for back end test classes

By Nov. 18th, 2013

Use Cases:

  • Random Choice Done
  • I'm feeling lucky Done
  • local mirroring Done

Front End:

  • Beautify the GUI: Kim Done
  • Refactoring

Back End:

  • Refactoring

By Nov. 20th, 2013

Use Cases:

  • Use Case 14: remove Illustrations Done
  • Use Case 11: editChoice Done
  • other in progress use cases

Other:

  • start (hopefully finish?) on sequence diagram during 3:00pm meeting
  • decide how to deal with updating published stories
  • decide on last bit of functionality we want to implement (delete objects?)
  • fix issue with activity test cases

By Nov. 25th, 2013

  • Complete and updated list of use cases Done
  • Tests complete and passing Done
  • Refactoring Done
  • JAVADOCS FROM EVERYONE Done

PROJECT CODING PART DONE BY TODAY!!!

By Nov. 27th, 2013

  • Finish Up Class Diagram (complete, notes, detail on key attributes/methods and design patterns) Done
  • Sequence diagram for a non-trivial scenario Done
  • Release planning for next iteration that won't be happening Done
  • tests all passing Done
  • Major Refactoring done and documented Done

By Nov. 29th, 2013

  • code clean without errors or warnings (lint errors!)
  • Wiki clean and updated
  • bugs sorted out
  • Video Demo: Josh (could push back to Dec. 1st if really needed) Done

By Dec. 1, 2013

  • All documentation Done
  • help guide completed Done

By Dec. 9, 2013

Use Cases:

  • permissions
  • multimedia use case that includes video and audio

Refactoring:

  • Clean up the front end. Separate dialogs and Async tasks into separate class to make activity classes smaller (front end people)

Features:

  • Implement story cover image. User can take photo or browse photo to make as cover
  • When browsing chapters, have it display the first illustration if there are any illustrations available

New Classes:

  • Media class (now an abstract class)
  • Image class (Ashley)
  • Audio class (Steph)
  • video class (Alex)

Front End:

  • Add functionality to upload new types of media (Kim)
  • Add a separate media editing activity (Josh)

Unit tests:

  • write new unit tests for the new functionality classes and methods

Also decide how versioning will be handled so everyone is on the same page.

By Dec. 16, 2013

Use Cases:

  • versioning
  • resizing images

When you click on a published story to download it, have the option of creating a brand new copy so the version on your local database doesn't get overwritten.

Front End:

  • make sure app can handle resizing images
  • implement the versioning dialogs
  • Kim GUI update for new activities made that are stable

New Class:

  • VersionManager (Steph + Ashley)

Other:

  • Also make unit tests for new classes
  • Continue small refactorings

By Dec. 20, 2013

All:

  • have decided how fighting fragments will be implemented
  • updated class diagram, and sequence diagram for how fighting chapters will be implemented

GUI:

  • have made our own theme for the app, zero hard coding to be seen anywhere

By Dec. 28, 2013

Use Cases:

  • Fighting Fragments
  • sync

Additional functionality:

  • can create a new fragment from an existing old one to save time for the author when creating them

BackEnd:

  • Create a new subclass of chapter, called fighting chapter
  • fightingChapterController to be manipulating the stats
  • tests for fightingfragments and controller
  • extend the Syncher class to do on going synching (done on separate threads)

Front end:

  • modified gui (specifically editChapterActivity and ViewChapter) to incorporate
  • have debugged and tested thouroughly

By Jan. 8, 2013

  • Have caught up on any late requirements until now

Extra Use Case:

  • User able to customize the app theme (front end)
  • Deletion of stories, chapters, and choices (locally and on server)

Other:

  • Completely updated uml diagrams
  • Meeting with customer to show the app
  • More refactoring (run JDeoderant), general code clean up
  • full documentation for all new classes completed