Version:
1.3
Release Date:
February 5, 2021
Last Updated:
April 6, 2021
Authors:
Campbell Leckie, Roy Ceyleon, Tyler Price, Jeff Kolnick
Editors:
Yasmine Ali, Ruth Schmidt, Anshul Khatri, Brayden Mckay, Syed Ahmed, Mohsin Malik
This overview provides background information and a brief description of the project, the client deliverables, the project milestones, and expected document changes.
StockEye is a web application that aggregates and analyses tweets related to the stock market from the popular social media platform Twitter, and offers information regarding the public sentiments of stocks to its users. StockEye seeks to serve its audience in multiple ways. For one, Twitter is a valuable source of data due to the impact that public opinion has on the market, enabling users to make more informed investment decisions. Additionally, this platform will save users time, as they will no longer be required to research and analyse the Twitter sentiments themselves.
The following are the list of deliverables to be completed, along with their respective deadlines. The Adjusted Deadline is an internal due date set to ensure that a deliverable is tested, approved, and ready to be presented, prior to the actual due date of the respective deliverable.
Deliverable | Deadline | Adjusted Deadline | Testing Deadline |
---|---|---|---|
Specifications Document | January 15, 2021 | January 14, 2021 | January 13, 2021 |
SPMP | February 5, 2021 | February 4, 2021 | February 3, 2021 |
Requirements Document | February 12, 2021 | February 11, 2021 | February 10, 2021 |
Analysis Document | March 5, 2021 | March 4, 2021 | March 3, 2021 |
Design Document | March 26, 2021 | March 24, 2021 | March 23, 2021 |
Implementation | April 17, 2021 | April 16, 2021 | April 15, 2021 |
Deliverable | Chief | Contributors | Testers |
---|---|---|---|
Specifications Document | Yasmine Ali |
|
|
SPMP | Campbell Leckie |
|
|
Requirements Document | Anshul Khatri |
|
|
Analysis Document | Nicolas Mills |
|
|
Design Document | Leron Bergelson |
|
|
Implementation Front End | Ruth Schmidt |
|
|
Implementation Back End | Leron Bergelson |
|
|
Implementation Model Training | Anshul Khatri |
|
|
Implementation Unit Testing | Michael Okenye |
|
Role | Group Member | Responsbilities |
---|---|---|
Meeting Chair | Ruth Schmidt |
|
Communications Correspondent | Yasmine Ali |
|
Documentation Site Manager | Roy Ceyleon |
|
The objective of this project is to produce a streamlined web-based platform for investors and market enthusiasts, to view the prospective performance of popular stocks based on the analysis of Twitter sentiments. Top priorities include project completion within the specified deadline and the implementation of a fully-functional application.
Activity | Plan |
---|---|
SPMP |
|
Requirements |
|
Analysis |
|
Design |
|
Front-end |
|
Back-end |
|
The project was initiated on January 15, 2021 and will be terminated with the end of the Winter 2021 semester at Wilfrid Laurier University, on April 12, 2021.
The project uses an object-oriented design methodology process and UML for the design and documentation of the software. The development process is organized into several activities, wherein the responsibilities of each activity, such as contributing and testing, are delegated to a subset of team members. The products of these activities are finalized upon the approval of the designated Chief of the respective deliverable, along with a majority of the contributing members. The approved documents are considered work products and will become part of the official software documentation.
Major milestones are the completion of all major pieces of documentation (Requirements, Analysis, Design etc.) and the fully-functional implementation of the application.
A listing of all the development methodologies, software, programming languages, and other tools used for the completion of project deliverables and non-deliverables:
The StockEye web application will be hosted on the cloud application platform Heroku. Linking Heroku to the StockEye repository on GitHub enables automatic synchronization between the production environment and GitHub master branch, removing infrastructure maintenance inherent to alternative solutions such as IaaS.
At each stage of development, every member of the group is expected to review and approve the product. This allows each member to gain a firm understanding of the project at each step of development, enabling them to identify where improvements can be made and keep everyone on the same page. This proves particularly beneficial at the implementation stage, as it will help catch any errors or bugs that may have been left unacknowledged.
Furthermore, as the web application is intended to be accessible, thorough testing must be done on multiple devices and browsers. These will include:For the purpose of clarity and transparency, code will be thoroughly and properly documented.
GitHub will be used during the implementation phase, allowing for precise tracking of all contributions and easy facilitation of code reviews. Furthermore, all members partaking in the implementation phase are expected to provide thorough commentary in their code to ease comprehension between collaborators.
The SPMP is a living document, changing as the project progresses. Therefore, it is important to track what changes were made to the document, when those changes happened, and who made those changes. While Google Docs is used to track the editing history, the SPMP includes references to major changes of the document within itself.
Date | Description of Change(s) | Contributor(s) |
---|---|---|
February 3, 2021 | Initial draft of SPMP completed |
|
February 4, 2021 | Final draft of SPMP completed |
|
February 20, 2021 | Appended descriptions of deadlines to Definitions |
|
March 28, 2021 |
|
|
April 6, 2021 |
|
|