HeaderSIS.jpg

IS480 OOPS Final Wiki

From IS480
Jump to navigation Jump to search

Project Progress Summary

Finalcurrentoops.png
Final Slides Deployed Site
Rocket.png Slidesmt.png

Project Highlights:

FinalHighlights.png

Project Challenges:

Oopschallenges.png

Project Achievements:

Oopsachievement.png

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.

Intermediate Deliverables:

Documentation Link
Project Overview Project Description
[Project Video Pitch]
Project Management Schedule
Task Metrics
Bug Metrics
Risk Management
Change Management
Project Documentation Prototypes
Diagrams
Testing User Testing 1
User Testing 2
User Testing 3

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:

UT1 UT2 UT3
UAT1oops.png UAT2oops.png UAT2oops.png

Reflection

Team Reflection:

TeamOopsReflection1.png

Individual Reflection:

KaedeeReflection2.png
ZhihuiReflection.png
YifeiReflection2.png
RxReflection.png

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