RocReadaR is currently an android app that lets users view digital media related to a specific piece of print media. A magazine page is scanned by the user using the app, and the app displays multi-media content based on the page. RocReadaR has many improvements planned, such as making the app on iOS and Windows, making it scalable to 30,000 total users, hosting the image recognizing in-house, improving analytics, making the app display different themes based on the publication, and other general improvements, such as a comment system and social media sharing.
The main goal for our team is to make RocReadaR an app and scalable service that can be used by publishers around Rochester by the end of the senior project. We plan on introducing a management portal system allowing multiple publishers to manage their own content and commenting rules. Additionally, we would like to host the image recognition technology in a scalable, cloud-based system.
Three separate applications will be developed. The first is the RocReadaR app, which will display the media to users who are reading the publications. The second application will be an online image recognition service, used by the RocReadaR app. The RocReadaR app will take pictures of physical pages in publications, upload them to this service, and the service will respond with media. The third will be a back-end management portal. Publishers will be able to use the portal to upload media that will be viewed on certain pages of their publications. Administrators of the RocReadaR team will be able to use the portal to manage publishers and other aspects of the application, like the online service.
Other than the project sponsors and the current RocReadaR development team, other major stakeholders include the publishers who will be publishing their content and the users who will be using the app. Usability is very important to the sponsors, as the app users will be looking for a streamlined experience. Publishers will be interested in application security, as well as customization of their content and the app. Additionally, publishers will need the service to be scalable and highly available. The RocReadaR team will also need the service and app to be maintainable and modifiable.
The project will be developed by the Rock Raiders senior project team over the course of the 2015-16 fall and spring semesters. Design and development will start in late September, and continue through the spring semester. As usability of the portal is an important quality attribute of the portal, user testing is planned for midway through development, in the second semester.
The RocReadaR project has multiple applications in its scope as it encompasses both the application itself, as well as the server infrastructure that supplies the content. In the following the scope of the entire project is discussed. Details of the scope of the senior project are in the Vision and Scope document.
Our team will address the content display and image recognition on the RocReadaR app. This will encompass working with the current team of the app to have it use new protocols developed on the recognition server. The RocReadaR app will send images of the publication the user is looking at to the recognition server and show the content returned from the recognition server.
The final application is the content management portal. The management portal will be a web portal for publishers to use to upload content for recognition, and content that is displayed on recognition. The server should retain analytics from the devices accessing it, to be later displayed on the portal for the publishers to view information about their publications, as well as some overall analytics for use by the RocReadaR team to improve on the application.
(- in date column means we did not keep track of it at that time)
Task | Description | Start | Completed | Due |
---|---|---|---|---|
Imitate Project Plan | Start the project plan document | - | 08/27/15 | 08/27/15 |
Project kick-off | Initial meeting with coach and sponsors | - | 09/01/15 | 09/01/15 |
Setup Project Website | Setup project website with contact information, project synopsis first draft, and other pertinent information | - | 09/08/15 | 09/18/15 |
Setup 4-up Charts | Put 4-up charts on the project website | - | 09/08/15 | 09/08/15 |
Setup time tracking | Find and set up a format for time tracking for the entire team | - | 09/08/15 | 09/08/15 |
Submit Project Synopsis | Finalize the project synopsis and submit it to the sponsors and coach | - | 09/15/2015 | 09/15/2015 |
Agree on requirements | Meet with sponsors to agree on requirements set | - | 09/21/2015 | 09/15/2015 |
Define methodology | Decide on a methodology and model and document both, and the reason why, in the project and on the website | - | 09/15/2015 | 9/17/2015 |
Project Plan First Draft | Finish the first draft of the project plan, with risks and overall project schedule | - | 09/22/2015 | 09/21/15 |
Project domain model draft | Finish the project domain model showing the structure of the project and how it relates to the business | - | 09/22/2015 | 09/21/15 |
Development methodology confirmed | Confirm our development methodology and document it in our test plan | - | 09/22/2015 | 09/21/15 |
Product/Process metrics confirmed | Confirm our metrics and document them in the test plan | - | 09/22/2015 | 09/28/15 |
Domain model finalized and submitted | Finalize the domain model and go over it with the sponsor | - | 09/29/15 | 09/29/15 |
Project Plan Approved | Go over the project plan with our sponsor and coach, and make sure it is approved | - | 09/29/15 | 09/29/15 |
Domain Model Approved | Go over the domain model with our sponsor and coach and make sure it is approved | - | 09/29/15 | 09/29/15 |
Use Cases Completed (70%) | Finish detailing at least 70% of use cases | - | 10/12/15 | 10/12/15 |
Publisher Portal Wireframe Mockup | Finish the wireframes of the publisher portal | - | 10/12/15 | 10/12/15 |
Source Control Finalized | Finish deciding on source control tools and make sure all members have access. Get a branching plan in place. | - | 10/06/15 | 10/12/15 |
Preliminary Architecture Draft | Start a draft of the architecture overview, and the deployment, module decomposition, and database diagrams | - | 10/15/15 | 10/19/15 |
Finalize Architecture | Finalize enough of the architecture diagrams to begin development | - | 10/26/15 | 10/26/15 |
Database Design Draft | - | 10/26/15 | 10/26/15 | |
Milestone: Finish User Management | Finish developing features that allow us to create and modify users | Winter Break | 02/09/2016 | 02/09/2016 |
Milestone: Finish Recognition Images uploading | Finish developing features that allow us to upload images of publication pages, and finish the conversion into wtc file | Winter Break | 02/16/2016 | 02/16/2016 |
Milestone: Finish Media Uploading | Finish developing features that allow us to upload media linked to publication pages and save them on the server. Details of how they are linked is not necessary, just having them uploaded | 02/02/2016 | 02/23/2016 | 02/23/2016 |
Milestone: Finish movement of documentation | Finish moving documentation from our Google Docs to Confluence | 02/02/2016 | 03/07/2016 | 02/23/2016 |
Mid-Term Peer Evaluation | Complete the Mid-Term Peer Evaluation as required by Senior Project | 03/01/2016 | 03/09/2016 | 03/08/2016 |
Milestone: Finish Media Management WYSIWYG | Complete the feature to allow us to link publication pages and media, by providing a simple drag and drop interface to create the details of how the media is displayed. | 03/01/2016 | 04/29/2016 | 03/08/2016 |
Milestone: Finish RocReadaR endpoint hookup | Finish hooking up the recognition endpoint to the RocReadaR Android App | 02/16/2016 | 05/02/2016 | 03/08/2016 |
Create Usability Testing Plan | Create our usability testing plan with our sponsor. Testing should be done on the RocReadaR Portal with publishers and advertisers | 03/01/2016 | 03/08/2016 | 03/08/2016 |
Run Usability Testing | Run our usability testing plan and collect the related data | 03/08/2016 | 05/06/2016 | 03/25/2016 |
Mid-Term Project Review with Sponsor and Coach | Meet with our Sponsor and Coach to complete the Mid-Term Project Review as required by Senior Project | 03/14/2016 | 03/18/2016 | 03/18/2016 |
Milestone: Finish All Media Management | Finish all features related to organization of publications, issues, and media associated with those issues | 03/08/2016 | 04/28/2016 | 03/29/2016 |
Milestone: Finish Metrics Tracking and Reporting | Finish all features related to collecting and displaying metrics of publications and their views | 03/08/2016 | Not Met | 03/29/2016 |
Milestone: Finalize Documentation | Finish our documentation. Meet with other developers of the other RocReadaR teams to hand off the documentation | 03/29/2016 | 05/14/2016 | 05/14/2016 |
Run Load Testing | Run load testing to determine the limits and costs of the RocReadaR recognition system | 03/29/2016 | Not Met | 04/12/2016 |
Incorporate Usability Testing Results | Incorporate the results and suggestions from usability testing into the product | 03/29/2016 | 05/06/2016 | 04/12/2016 |
Create Project Poster | Create and present our project post as required by Senior Project | 04/05/2016 | 04/15/2016 | 04/15/2016 |
Create Technical Report | Create and submit our technical report as required by Senior Project | 04/25/2016 | 05/09/2016 | 05/12/2016 |
Create Presentation | Create and rehearse our project final presentation as required by Senior Project | 04/25/2016 | 05/11/2016 | 05/12/2016 |
Final Reflection and Senior Survey | Complete the Senior Survey and meet with our Coach and Sponsor for final reflection | 05/16/2016 | 05/16/2016 | 05/16/2016 |