HeaderSIS.jpg

IS480 Team wiki: 2018T2 Squad/Midterms

From IS480
Jump to navigation Jump to search
SQUADLogo.jpg


Squad Home.png
Squad About Us.png
Squad ProjOverview.png
Squad ProjManagement.png
Squad Documentation.png
Main Midterms Finals


Project Progress Summary


Squad MTProgressSummary.png


Midterm Slides: File:Squad MidTermsPPT.pdf
Deployment Link Web Admin: http://52.41.18.27/OleAdmin
Deployment Link to download android mobile apk: Download the application here

1. Login Details for Web Admin
Userid: admin
Password: squadxole18

2. Login Details for Mobile
Download the application and sign-up! It's free (:

Project Highlights


A few of the highlights for the project thus far is that we have managed to call the API on a timely basis, i.e: daily. The next step is to call the API according to the match time to ensure real-life update. Apart from that, we had more than 30 users for UAT and more than 50% of the users from UAT 2 said that they would recommend the application to others.

Project Management

Project Status

Squad MTProgressUpdate.png

Project Schedule (Plan Vs Actual)

Planned Schedule

Squad IterOri.png

Actual Schedule

Squad Iterations.png

Project Metrics

Bug Metrics

Squad MTBugCount.png


Squad MTBugScore.png

Task Metrics

Squad TaskMetric.png


Squad TaskMetricBreakdown.png

Project Risks

Risk Management

Squad MTClientManagement.png


Squad MTTechnical.png


Squad MTProjManagement.png

Technical Complexity

1. Directly calling API timely

Upon calling the API for the first time, early in the project, the team save the output from the API as a JSON object and used the data pulled, locally. However, as the project progressed, we understand that matches are updated regularly and in order to ensure that the application is scalable and flexible, we managed call the API used timely hence, all information regarding the matches are real-time.

Before

Squad DownloadApiToLocal.jpg



After

Squad APITimelyCode.png



2. Switched from RDS to AWS instance cloud hosting

Firstly, the Web Admin deployed in the AWS EC2 instance is not able to connect to the RDS DB due to a configuration error. Initially the team used the free tier from RDS. We tried to solve this however due to time constraints we had to choose the alternative way. Also, as the project progress, and more functions and resources are added, the load time for the application became longer and slowed down the performance of the application. Therefore, we decide to host the DB in the EC2 instance and it made performance for our Web Admin and Web Service much faster.

Before

Squad rds db.JPG



After
Squad instance db.JPG



3. Switched from Volley to OKHttp

Both Volley and OKHttp are libraries for HTTP requests in Android Java development. The team encountered a Volley timeout error during the development and decided to switch to OKHttp. Volley is an asynchronous operation while OKHttp is a synchronous operation.

Before

Squad VolleyTimeout.png



After
Squad GetOkhttp.JPG Squad PostOkhttp.JPG



Quality of product

Intermediate Deliverables

Stage Specifications Modules
Project Management Minutes Minutes
Metrics Metrics
Risk Management Risk Management
Analysis Use Case Use Case Diagram
Business Process Diagram Business Process Diagram
Design ER Diagram ER Diagram
Class Diagram Class Diagram

Testing


Click here to access detailed UAT results.

Reflection

Team Reflection

Squad MTLO Hani..png


Squad MTLO Hazirah.png


Squad MTLO Srav.png


Squad MTLO YT.png


Squad MTLO Farihin.png


Squad MTLO WE.png