HeaderSIS.jpg

IS480 Team wiki: 2016T1 MonoChrome Finals

From IS480
Revision as of 10:04, 14 November 2016 by Wenda.yeo.2014 (talk | contribs)
Jump to navigation Jump to search
LogoBlackTall.png


NavHome.png   HOME

Icon5.png   OUR TEAM

NavProjectO.png   PROJECT OVERVIEW

NavPM.png   PROJECT MANAGEMENT

NavDoc.png   DOCUMENTATION


Screen Shot 2016-11-06 at 8.45.19 PM.png


Project Progress Summary


MonoCFinalProgress.png
Final Slides Deployed Site Video Pitch
PptPic.png MonoCDashboard.png MonoCVidPik.png

Project Highlights:

  • List of requirement changes
    • Added new 2 functions (Generate daily report, Configure settings)
  • UAT 4 is scheduled from 11 November to 14 November

Project Achievements:

  • Successful implementation of Reverse SSH, stable and working. (Technology that is built in-house, as there are no commercially available API for this)
  • Successful implementation of SNMP, our web application is able to monitor WiFi router health status too

Project Management

Project Status:

Screen Shot 2016-11-06 at 10.54.32 PM.png
S/N FEATURES STATUS COMMENT
1 Database Module Fully deployed and tested 100% Completed
2 Data Collection Module Fully deployed and tested 100% Completed
3 Analytics Module Fully deployed and tested 100% Completed
4 Dashboard Module I Fully deployed and tested 100% Completed
5 Sensor Module Fully deployed and tested 100% Completed
6 Notification Module Fully deployed and tested 100% Completed
7 Two-way Communication Module Fully deployed and tested 100% Completed
8 Dashboard Module II Fully deployed and tested 100% In progress
9 Database Collection Module II Fully deployed and tested 100% Completed
10 Optimization Module Fully deployed and tested 100% Completed
11 Account Management Module Fully deployed and tested 100% Completed
12 Dashboard Module III Fully deployed and tested 100% Completed
13 Notification II Module Fully deployed and tested 100% Completed
14 Downtime Manager Module In progress In progress
15 Mobile Responsive Module In progress Will always revise the mobile responsiveness for every change in design
16 Security Module Removed upon negtiation Removed upon negtiation

Project Schedule (Plan Vs Actual):

PLANNED ACTUAL
MonoCTimelinev5.png

MonoCTimelinev6.png

Project Scope (Plan Vs Actual):

PLANNED ACTUAL
MonoCFunctionalities v3.png

MonoCFunctionalities v4.png

ITERATIONS PLANNED ACTUAL COMMENT
10 - Perform speed test, Configure settings for 4 groups & flapping threshold, Generate daily summary report Oct 2016 New scope proposed by Sponsor
12 UAT 4 Nov 2016 - Scheduled UAT 4 to 14 Nov due to sponsor unavailability

Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.

Project Metrics:

Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.

Technical Complexity:

S/N TECHNICAL COMPLEXITY IMAGE DESCRIPTION
1 Front End: Maintaining React state

Before:

   From vertical menu: 
   $(‘#deleteSensorMac’).val(macAddress);
   
   In DeleteSensor.jsx: 
   var macAdd = $(‘#deleteSensormac’).val();

Problem: Erratic / unreliable

Redux.png

In traditional React applications, props can only be transferred from a parent to child component. this, however, can be inconvenient as certain components in complex web applications may need to receive props that cannot be passed on from its parent.

  • Our modals, for example, require information such as the mac address of a sensor. the DeleteSensorModal component, for instance, is a child of the Dashboard component.
  • There are two issues here:
    • Firstly, the component that triggers the DeleteSensorModal component to appear is not its parent. As such, it is unable to directly pass the mac address prop to the DeleteSensorModal component.
    • Secondly, the Dashboard component does not know which mac address is required as does not interact with the DeleteSensorModal component.
  • As such, we used Redux -- a React framework that is used to help to maintain state.
  • Actions are triggered from a component on user interaction. These actions store the mac address (or any other useful pieces of information) in a global state store. The component that requires the information retrieves it after.
2 Pinging Servers
Screen Shot 2016-11-14 at 2.41.14 AM.png

One of the issues that surfaced while we were testing for fault tolerance came about due to the way fault tolerance was implemented.

  • Data from Raspberry Pis is sent through FluentD, a unified logging layer, which buffers and stores it locally in case of connectivity issues. This ensures that data is not lost even if a Raspberry Pi is disconnected from the internet.


  • However, an unexpected limitation came when a sensor was disconnected for an extended period of time. The buffer was full when the internet connection came back, and the sensor began sending it's stored records. The records were sent in chronological order, which meant that the data being inserted to the database initially was out of date. It took nearly a half hour for the buffer to completely sent.


  • The fact that the records were older meant that the sensor was labelled as "down" on the dashboard, it was technically alive and sending data.


  • To circumvent this issue, we developed a secondary architecture for data logging, which involved sending small packets of data to indicate that a sensor was "alive". These logs are not sent through Fluentd, thus eliminating the buffering issue. The data in these logs is limited to a sensor's mac address and a timestamp, periodically inserted into the server's database. Their sole function is to indicate whether a Raspberry Pi is "alive" or "down". This information is displayed in conjunction with the Raspberry Pi's status.


  • With this new system, a scenario where a Raspberry Pi is sending its buffer would have a ping result indicating that the Raspberry Pi is still alive, despite its being labelled as "down".
3 SNMP (Simple Network Management Protocol)
Screen Shot 2016-11-14 at 2.44.38 AM.png
Reasons why a Raspberry Pi might go "down" can be generalized into 3 categories: Issues with the Raspberry Pi, issues with its router, or connectivity issues.
  • The first can be easily discerned by the Raspberry Pi's status, but the latter two are more tricky. Routers often do not run the same operating systems as Raspberry Pis, making it harder to place custom scripts on them to allow collection of data.
  • The use of Simple Network Management Protocol (SNMP) allowed us to solve this issue. Assigning one of the Raspberry Pis to run the snmpwalk program provided access to information about the router, including CPU usage, temperature, RAM, etc.
    • Users can then use this information to evaluate the status of the router, to determine if any issues with Raspberry Pis are due to the router as opposed to the Raspberry Pi itself.
  • This is used in conjunction with an internet speed test. Similar to the abovementioned snmpwalk, a Raspberry Pi is assigned to periodically run the speed test, and the results are displayed on the dashboard. Poor speed test results could indicate that high downtime is due to poor internet connectivity, as opposed to issues with the Raspberry Pis or the router.

Quality of product

Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.

Project Deliverables:

List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.


Stage Specification Modules
Project Management Meeting Minutes MonoChrome Meeting Minutes Page
Task Metrics & Bug metrics MonoChrome Metrics Page
Requirements Story cards CRUD Customer, Trend Analytic
Analysis Use case overall
Market Analysis IS480 Team wiki: 2016T1 MonoChrome Market Analysis, Detailed Market Analysis Report
Business Process Diagram
Screen Shots CRUD Customer, Trend Analysis
Design Use Cases & Use case scenario IS480 Team wiki: 2016T1 MonoChrome Documentation
Class Diagram 1, 2, 3
Testing Test plan instructions
Handover Manuals User Tutorial
Code Client server
Deployment Diagram instructions

Quality:

Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.

Deployment:

In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.

Testing:

Functionality & Regression Testing

Testing Remarks Total
Functionality Testing Every module test 7
Regression Testing Every iteration test 9

UAT:

  • Till date, we have completed 3 UAT.
  • The objective, test cases and results can be view on the UAT page. Click on the image to go to the UAT page
USER TESTING DATE USER PROFILE LINK
UAT 1 3 August 2016 Thomas Wong (Sponsor) + 5 random users UserTesting 01.jpg
UAT 2 22 August 2016 Thomas Wong (Sponsor) + Cecilia Sim (Sponsor) + Hazmei Bin Abdul Rahman (ORT Intern) UserTesting 02.jpg
UAT 3 13 September 2016 Thomas Wong (Sponsor) + Sean Ang (Full time staff) + Lim Shuen (Intern) UserTesting 03.jpg

Reflection

Team Reflection:

We learnt that it is important to keep an open-mind when developing an application for a client because along the way there will be unforeseen circumstances, many unknown unknown that we need to solve as well as take in feedbacks from the various stakeholder. IS480 have given us an opportunity to learn real life skill sets and to stretch us beyond our limits.

Ian's Reflection:

This project has been quite a journey. Before we started, my knowledge was limited to what was taught in the classroom. Six months later, this project has, in a sense, forced my teammates and I to learn, explore, and experience unfamiliar technologies and techniques. For instance, reverse ssh is one of the techniques I picked up during this project, and making it persistent and stable became an experiment in and of itself.

Marcus's Reflection

I've made the adage "good artists copy, great artists steal" my motto throughout the course of the project. Rather than trying to reinvent the wheel, I scoured the internet for ideas on dashboard design elements and pieced a couple of good ones together as a deliverable. I've learned to be more acceptive of criticism and ideas that oppose mine. This, in turn, helped to spark fresh ideas that had far more depth. As a team, I'm proud to say that we've accomplished what we labeled as "impossible" at the start of the project.

Yong Jin's Reflection

Before embarking on this project, I have been working in classroom projects with a feeling of certainty. I was first taught the necessary knowledge, then applying them on a well-thought out problem. This project has been a total experience for me, knowledge has to be self-acquired with the application on a real existing problem which can be everchanging. There is no longer certainty anymore, I have to lean on myself and my team for strength where we learned progressed and grew together over these past 7 months.

Sarah's Reflection

During the course of this project, I have learned the importance of quality assurance. Learning to make changes based on user testing results has allowed the team to constantly improve on the dashboard, ensuring the client's satisfaction. This project has been a new experience for me as I often worked alone in the past. Working with my teammates on this project has shown me how to work efficiently as a team leaning on each other for help under the pressure of the project. I am glad to say we have grown together as a team through this process.

Wen Da's Reflection

"Coming together is a beginning; keeping together is progress; working together is success", this quote speaks dearly to me for my whole IS480 journey, because my job as PM I need to ensure that my team keep together, I will think about the welfare of my team to keep them motivated and not feel burn out too often. Encouraging them and appraising them for their hard work. I also learnt that as a PM, it is important to be adaptive to the situation, using the metrics that I have to reschedule and reprioritize the tasks to ensure that we are able to deliver a quality system in time. Lastly, I am proud to say that we are able to work along together well for almost 8 months, my team supported each other during tough periods, committed their utmost effort and made sacrifices for each other.

Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.



BannerBlack-01.png