HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki:2017T2 Zenith Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 71: Line 71:
  
 
===Project Status:===
 
===Project Status:===
[[File:Zenith_midterm_scope.png|center|1000px]]
 
 
<br>
 
<br>
 
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
 +
A breakdown of tasks is shown in our [[IS480_Team_wiki:2017T2 Zenith_project_scope|project scope]].
 +
</div>
 +
<br>
 +
[[File:Zenith_midterm_scope.png|center|1000px]]
  
 
===Project Schedule (Plan Vs Actual):===
 
===Project Schedule (Plan Vs Actual):===

Revision as of 22:38, 16 February 2018

Zenith banner.png

Home

Team

Project Overview

Project Management

Documentation

Main Wiki

Midterm Wiki Final Wiki


Zenith midterm header.PNG


Project Progress Summary

Midterm Slides

(insert link here)

Deployed site link

Zenith deployment link.jpeg

Project Highlights

Our project schedule is divided into 13 iterations.

  • We are currently on our 9th iteration (12 Feb - 25 Feb 2018).
  • Up till 19 Feb 2018, we have completed (percentage)% of our development progress.
  • 1 User Acceptance Test was conducted before Midterms. The results are shown here.
  • Achieved and exceeded Midterms X-factor.


Unexpected events:

  • New team of clients.
  • Cancellation of one User Acceptance Test by clients due to busy schedules.
  • List of requirement changes after Acceptance can be viewed here.

Project Management

Iteration Progress: 9 of 13
Features Completion: ???% (??? out of 36 features)
Confidence Level: 100%

Project Status:


A breakdown of tasks is shown in our project scope.


Zenith midterm scope.png

Project Schedule (Plan Vs Actual):

Milestones Overview:

Planned (Acceptance) Actual (Midterms)

Zenith midterm planned timeline.png

Zenith midterm actual timeline.png

Project Schedule:

Planned Schedule (Acceptance)

Zenith midterm expected schedule.png



Changes in planned schedule (Acceptance)

Zenith midterm changed schedule.png



Actual Schedule (Midterms)

Zenith midterm actual schedule.png

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.

Project Risks:

Update the proposal assumptions and risks. Describe what you learn from the risk update and mitigation steps taken.

Be sure to prioritize the risks.

Technical Complexity:

Natural Language Processing

Natural Language Processing (NLP) was used for the automated marking of open-ended questions.

Added security features

In December 2017, our MongoDB database was compromised and held hostage by ransomware. We were instructed to pay 0.1 bitcoin (USD $1594) for the return of our data. Fortunately, we had backed up the data so there was no need for us to pay the ransom. Since this incident, we have taken additional measures to ensure that this does not happen again.

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.

Intermediate Deliverables:

There should be some evidence of work in progress.

Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.

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

In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.

Team Reflection:

Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Benjamin Gan Reflection:

You may include individual reflection if that make sense at this point. The team is uncooperative and did not follow my instructions.