IS480 Team wiki: 2016T1 MonoChrome Finals
Project Progress Summary
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:
S/N | FEATURES | STATUS | CONFIDENCE LEVEL(0 - 1.0) | COMMENT |
---|---|---|---|---|
1 | Database Module | Fully deployed and tested 100% | 1 | Completed |
8 | Dashboard Module II | In progress | 1 | In progress |
9 | Database Collection Module II | In progress | 1 | In progress |
10 | Mobile Responsive Module | In progress | 1 | Will always revise the mobile responsiveness for every change in design |
11 | Optimization Module | In progress | 1 | New scope proposed by Monochrome: Archiving; Half of Security Module moved to this new module. |
12 | Account Management Module | In progress | 1 | "Register new user account" to be completed in Iteration 11 |
13 | Dashboard Module III | Scheduled for Future Development | 1 | To Be Completed |
14 | Downtime Scheduler Module | Scheduled for Future Development | 1 | To Be Completed |
15 | Security Module | Removed upon negtiation | N.A | Removed upon negtiation |
Project Schedule (Plan Vs Actual):
PLANNED | ACTUAL |
---|---|
Project Scope (Plan Vs Actual):
PLANNED | ACTUAL |
---|---|
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:
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
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 |
System Sequence Diagram | client, server | |
Business Process Diagram | ||
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ER Diagram | 1, 2, 3 |
Class Diagram | 1, 2, 3 | |
Testing | Test plan | instructions |
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | client server | |
Deployment Diagram | instructions |
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
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:
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
Reflection
Compile common lessons and reflection for the team and for each team member. Be brief.
Team Reflection:
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Individual Reflection:
Ian's Reflection:
Yong Jin's Reflection:
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.