Difference between revisions of "IS480 Team wiki:2017T2 Zenith Midterm Wiki"
Line 134: | Line 134: | ||
<div style="font-family: Verdana;"> | <div style="font-family: Verdana;"> | ||
<center> | <center> | ||
− | {| | + | {| class="wikitable" style="font-family:Verdana; background-color:#FFFFFF; width: 600px;" align="center" |
− | + | ||
− | + | ! style="color:#ecf0f1; background-color:#565656;" width="300pt" | Stage | |
− | + | ! style="color:#ecf0f1; background-color:#565656;" width="400pt" | Specification | |
− | |||
|- | |- | ||
− | |rowspan=" | + | |rowspan="6"| Project Management |
− | || Minutes | + | || [[IS480 Team wiki: 2017T2_Zenith_Management|Schedule]] |
− | || | + | |- |
+ | || [[IS480_Team_wiki:2017T2 Zenith_minutes|Minutes]] | ||
+ | |- | ||
+ | || [[IS480_Team_wiki:2017T2 Zenith_metrics#Bug Metric|Bug metrics]] | ||
+ | |- | ||
+ | || [[IS480_Team_wiki:2017T2 Zenith_metrics#Task Metric|Task metrics]] | ||
+ | |- | ||
+ | || [[IS480_Team_wiki:2017T2 Zenith_risk_management|Risk management]] | ||
+ | |- | ||
+ | || [[IS480_Team_wiki:2017T2 Zenith_change_management|Change management]] | ||
|- | |- | ||
− | || | + | |
− | || | + | |rowspan="3"| Requirements |
+ | || [[IS480 Team wiki: 2017T2 Zenith Overview | Overview]] | ||
|- | |- | ||
− | + | || [[IS480_Team_wiki:2017T2 Zenith_project_scope | Scope]] | |
− | || | + | |- |
− | | | + | || [[IS480 Team wiki: 2017T2_Zenith_Documentation | Personas]] |
− | || [ | ||
|- | |- | ||
− | |rowspan=" | + | |rowspan="3"| Analysis |
− | || Use case | + | || [[IS480_Team_wiki:2017T2 Zenith_diagrams#Use Case Diagram | Use case diagram]] |
− | |||
|- | |- | ||
− | + | || [[IS480_Team_wiki:2017T2 Zenith_diagrams#Architecture Diagram | Architecture diagram]] | |
− | || | ||
− | |||
|- | |- | ||
− | + | || [[IS480_Team_wiki:2017T2 Zenith_technologies| Technologies used]] | |
− | || [ | ||
− | |||
|- | |- | ||
− | |||
− | |||
− | |||
− | |rowspan=" | + | |rowspan="1"| Design |
− | || [ | + | || [[IS480_Team_wiki:2017T2 Zenith_prototype |Prototypes]] |
− | |||
|- | |- | ||
− | || | + | |rowspan="1"| Testing |
− | || [ | + | || [[IS480_Team_wiki:2017T2 Zenith User Testing 1 |User Acceptance Test 1 (11 - 13 Feb 2018)]] |
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</center> | </center> | ||
− | </div> | + | </div> |
===Testing:=== | ===Testing:=== |
Revision as of 11:01, 17 February 2018
Midterm Wiki | Final Wiki |
Project Progress Summary
Midterm Slides
(insert link here)
Deployed site link
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.
Project Schedule (Plan Vs Actual):
Milestones Overview:
Project Schedule:
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
Intermediate Deliverables:
Testing:
- Internal testing is performed at the end of every iteration, and after every deployment.
- We expect to complete 2 UATs by the end of the project.
- 1 UAT has been completed before Midterms. To view the results of this UAT, click here.
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.
Stage | Specification |
---|---|
Project Management | Schedule |
Minutes | |
Bug metrics | |
Task metrics | |
Risk management | |
Change management | |
Requirements | Overview |
Scope | |
Personas | |
Analysis | Use case diagram |
Architecture diagram | |
Technologies used | |
Design | Prototypes |
Testing | User Acceptance Test 1 (11 - 13 Feb 2018) |