HeaderSIS.jpg

Dpenz Final Wiki

From IS480
Jump to navigation Jump to search

Project Progress Summary

Place your Final slides link and deployed site link here

For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here.

This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal, midterm or other wiki information here. Highlight changes since midterm.

Describe the project progress briefly here. Is the project completed? Link to the final presentation slides and videos.

Changes since Midterm

  • Fully implemented changes from Midterm feedback (i.e. Field validations, currency code, archiving, etc.)
  • Fully implemented remaining functions (Admin panel, Export project details, Export report)
  • UT5 with client side
  • Fully implemented changes from UT5 (i.e. Aesthetic improvements such as terminology)

Project Highlights:

What unexpected events occurred and how were they handled?

  • A team member left the project and dropped the course
  • List of requirement changes
    • CRUD items replaced with CU/Sync/Archive items
    • Business analytics replaced with iPad client
  • Took 8 weeks to learn Ruby on Rails
  • etc.

Be brief. A couple of sentences on the event and another couple on what was done is sufficient. Do not repeat the next sub sections. If there are no highlights, remove this section

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:

Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.

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.

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.

Bug Metrics

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.

Design Considerations

  • In the design of our UI, we made sure to use the the principles we have learnt in IDP. For example, Nielsen's 10 heuristics .

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 Meeting Minutes
Metrics Bug Metrics
Requirements
Analysis Use case Use Cases
System Sequence Diagram
Screen Shots
Design ER Diagram 1, 2, 3
Architectural Diagram Architectural Diagram
Testing Test plan User Testing
Handover Manuals
Code

Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.

Quality:

Technical Complexity (will be up soon but for now please refer here to our slides)

Testing:

User Test 5

Reflection

- new skills: new domain knowledge, technology...etc - improving existing skills: any further development of existing skills? - challenge: wad challenges? How u overcome? How u learn on ur own? 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.

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