HeaderSIS.jpg

IS480 Team wiki: 2017T1 Team Atoms MidTerm

From IS480
Jump to navigation Jump to search
Atoms Logo.png


Team Atom Icon Home.png

HOME

  Team Atom Icon Aboutus.png

ABOUT US

  Team Atom Icon Projectoverview.png

PROJECT OVERVIEW

  Team Atom Icon Projectmanagement.png

PROJECT MANAGEMENT

  Team Atom Icon Documents.png

DOCUMENTATION



Project Progress Summary


Atoms midterm dashboard.png

Atoms midterm slides.png Atoms midterm deployedsite.png


User: demo | Password: demopassword123

Project Management

Project Status

Atoms midterm projectstatus.png

Project Schedule (Plan vs. Actual)

Several changes were made to the project schedule due to greater emphasis on Data Classification module and preparation for Lab Release(Live usage) as requested by sponsors. Hence, Atoms had rescheduled and dropped afew tasks that were not critical for the lab completion (as reflected in the actual schedule). The changes in the iterations were made to ensure the completion of the project on time and to also optimize the sponsor's requirements. Progress of the team is well-paced and optimistic.

Planned Project Schedule

Atoms midterm plannedschedule.png

Actual Project Schedule

Atoms midterm actualschedule.png


Project Metrics

Change Management

Below is the change log for Iteration 7 to 10 (after acceptance):

Change Log
Iteration Date Type Change Request Rationale Feasibility Outcome Priority Status of Request Issued By
7 19/8/2017 Scope & Schedule Reschedule classification and clustering module Reschedule functions based on lab exercise and release dates Fits into schedule without any expected delay as a consequence. Accepted High Closed Team
8 23/8/2017 Scope Remove Neural Network function Team feels that scope is too large and functionality is not critical for labs completion Group, sponsor and supervisor agree to removal of unnecessary functions Accepted High Closed Team
8 02/9/2017 Scope Add Aggregation function Team realize that the functions is required to effectively complete Lab1 Fits into schedule without any expected delay as a consequence Accepted Low Closed Team
9 08/8/2017 Scope Add XG Boost(New Classification technique) function Sponsor highlighted that this is a commonly used classification technique and will be really useful for student projects. Team has excess time to complete this Fits into schedule without any expected delay as a consequence Accepted Low Closed Sponsor
9 08/8/2017 Scope Add static documentation web page Sponsor request for documentation/user guide to allow new users to be familiarize with the system. Team has excess time to complete this function Fits into schedule without any expected delay as a consequence Accepted Low Closed Sponsor

Project Risks

Technical Complexity

Quality of Product

Intermediate Deliverables

Topic of Interest Link
Project Management Project Schedule
Minutes
Metrics
Risk Management
Change Management
Project Overview Project Overview
Team's Motivation
Project Scope
Project Documentation Diagrams
Technologies Implemented
Low & Mid Fidelity Prototypes
Testing Testing Documentation


Deployment

Note: Application link provided is for our test server, which is only available within the SMU Network. Otherwise consider using VPN to access the SMU Network
To view application, visit
Test server: http://10.0.106.101/
Username: demo
Password: demopassword123


Note: This public server is currently being utilized for Live Usage by the IS424 Data Mining and Business Analytics students for their labs and project completion.
Production server: https://kddlabs.cn/

Testing

Atoms internaltesting.PNG Atoms UAT1.PNG Atoms UAT2.PNG Atoms Liveusage.PNG

Internal Testing

We engage in comprehensive manual testing in every iteration. The developers will conduct individual testing before committing their codes on our shared repository, GitHub. We believe in testing the application manually at this level because tests can be specially adjusted to cater to changes in the application, both on the front and back end. Furthermore, manual testing brings about the human factor, allowing us to better discover problems that might surface during real usage due to natural human behavior.

Once the developers have fixed the bugs, the fixed set of codes will be merged and integrated with the other functionalities. Subsequently, the integrated code is then deployed on the test server and the lead quality assurance will run a final check against the set of test cases created. This helps to ensure that the deployed application works with no major incidents.

The team's lead quality assurance then performs regression testing on the test server where previous functionalities developed are tested again. This helps to ensure that existing functionalities in the application are not affected by the integration. Once bugs have been identified, the lead quality assurance will then update the bug-tracking Excel sheet and notify the relevant developers of the issues and the corresponding priority level.


The team’s list of test cases can be found on our private repository here.

User Acceptance Test 1 & 2

Team Atoms has conducted 2 user tests which allowed us to better manage sponsor expectations as well as improve on usability of our application interface.

IPMAN Midterm Testing Overview.png

For more detailed version of Team Atoms user acceptance test results, access it here:

Atoms UAT1.PNG     Atoms UAT2.PNG


Live Usage

Reflection

Team Reflection

Sponsors' Testimonial

Individual Reflections