HeaderSIS.jpg

IS480 Team wiki: 2017T2 Bare Code Wiki Finals

From IS480
Jump to navigation Jump to search


link=IS480_Team_wiki%3A_2017T2_Bare_Code

HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

MAIN WIKI

WIKI FOR MIDTERMS

WIKI FOR FINALS


Project Progress Summary

  • Please see deployed site link here:
  • Please see presentation slides here:
  • MSL @ NP is now available for download on Apple App Store!

Progress Update:

  • As of 4 April 2018, MSL @ NP is 100% completed.
  • As of 2 April 2018, 3 UATs were conducted with a total of 53 students for the iOS application.
  • MSL @ NP has gone live on Apple App Store on 15 March 2018

Project Highlights:

  • Priorities were changed based on midterms feedback and sponsor's preference
    • Added mobile features to the application (e.g. upload photos & location-tagging)
    • Added an offline function to facilitate learning-on-the-go
    • As a result, the team dropped the "Survey Module" to work on the two above-mentioned functions
  • Took 3+ weeks to learn and develop offline function

Project Challenges:

Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.

Project Achievements:

  • Achieved our initial scope set as a 6-men team, despite having to downsize unexpectedly to a 4-men team.
  • Application successfully deployed to Apple App Store
  • Focusing on the experience rather than the outcome also helped alot in relieving stress for the team, which translated into better productivity and morale
  • To ensure everyone is on the same page after every meeting, each member is assigned a role in minutes taking. E.g. Cheryl takes minutes, Ailin will vet through Supervisor Meeting Minutes, Grace will vet through Client Meeting Minutes & Pei Jia will vet through Team Meeting Minutes.

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Schedule (Plan Vs Actual):

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.

Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.

Iterations Planned Actual Comments
1 Customer CRUD 1 Sept 2010 25 Aug 2010 Fiona took the Sales CRUD as well.
Trend Analytic 1 Sept 2010 15 Sept 2010 Ben is too busy and pushed iteration 1 back
2 User tutorial 1 Oct 2010 Removed proposed by Ben
Psycho analysis 1 Oct 2010 New module proposed by sponsor

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 Minutes Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7
Metrics Bug metrics
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:

Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.

Cheryl Lee Sze Min:

Cheau Nor Ailin:

Grace Foo Huan Ting:

Lee Pei Jia:


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