Difference between revisions of "IS480 Team wiki: 2012T2 box.us Final"
Qyang.2010 (talk | contribs) |
Qyang.2010 (talk | contribs) |
||
Line 204: | Line 204: | ||
[[Image:Boxus_Schedulemetricsfinals.png | 500px]] | [[Image:Boxus_Schedulemetricsfinals.png | 500px]] | ||
− | |||
− | |||
==<p><div class="NavHead" style="background-color:#810541;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 12pt;"><span style="color: White"> '''Quality of product''' </span></div></p>== | ==<p><div class="NavHead" style="background-color:#810541;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 12pt;"><span style="color: White"> '''Quality of product''' </span></div></p>== |
Revision as of 23:17, 20 April 2013
HOME | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Contents
Project Progress Summary
What Is This Project About?
Check out our 1 min ++ video pitch to find out what this project is about at Youtube
Quick Links
Final Presentation Slides: coming soonDeployed Site: Empact ACTDemonstration Site: Empact ACT(Staging)Initial Proposal: Proposal |
---|
Project Highlights:
Managing the Great Amount of Issues being Highlighted during Deployment
|
Volunteers did not find language in the system friendly
|
Addition of 2 functionalities
|
Project Challenges:
Gathering Requirements from Empact
How we Managed
|
Dealing with Changes
|
Project Management
Project Scope:
Change | Change Description |
---|---|
1 |
Export Task
|
2 |
Notification
|
Project Schedule (Plan Vs Actual):
Project Metrics:
BUG METRICS
Iteration | Bug Score | Any Actions Taken |
---|---|---|
11 | 31 |
Increase in Bug Score due to bugs that were recorded from User Testing 2
|
12 | 16 |
New features of the system(Statistics, Dashboard and Notifications) were being released and enabled Empact to verify the functions
|
13 | 58 |
More thorough testing was being performed for the UAT
|
SCHEDULE METRICS
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 | Meeting Minutes |
Metrics | Bug metrics | |
Requirements | Story cards | CRUD Customer, Trend Analytic |
Analysis | Use case | Use Case Diagram |
System Sequence Diagram | client, server | |
Business Process Diagram | Process Diagrams | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | ERD Diagrams | V1,V2,V3,V4,V5 |
Class Diagram | 1, 2, 3 | |
Testing | User Testing 1 Test Plans | Test Plans used |
User Testing 2 Test Plans | Test Plans used | |
Heuristic Evaluation User Scenarios | User Scenarios used | |
Integration Testings | Integration Testings | |
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:
Release 0.1 |
---|
Key Changes
|
Feedback Collected
|
Release 0.2 |
---|
Key Changes
|
Feedback Collected
|
Release 0.3 |
---|
Key Changes
|
Feedback Collected
|
Release 0.4 |
---|
Key Changes
|
Feedback Collected
|
Release 0.5 |
---|
Key Changes
|
Feedback Collected
|
Testing:
User Testing | Integration Testing | Deployment Testing |
---|---|---|
Objective: To collect feedback concerning usability of our application | Objective: To test the quality of our application | Objective: To collect feedback when application is being used in live environments |
When: | When: | When: |
How: | How: | How: |
Findings: | Findings: | Findings: |
Reflection
Compile common lessons and reflection for the team and for each team member. Be brief.
Team Reflection:
- Managing client expectations
- Learning to collaborate more effectively in a team
- Leveraging one another's strength and weaknesses
- Being a good team player within the team
- Learning to have fun as a team!
- Our IS modules have helped to prepare us for the demands of an IT project
Individual Reflection:
Kevin
As I review through my initial learning outcomes that I set out to learn, I felt that I have managed to meet these outcomes in the following way:
- Motivating IT Project teams: Bringing together people from different walks of life together to work on an IT project has sharpened my skills in handling with people and being more cognisant of people management issues and how to deal with group cultures and team norms
- Evaluating IT project ideas: FYP has taught me how to be aware of what are the current issues facing IT projects. It has taught me how to evaluate these and adopt a T-model by being able to think about what are the broad issues that are going to affect IT decisions and what are the deep issues that are specific to the issue being raised.
- Time Management Skills: FYP has taught me to be aware of the time that I spend managing the team, managing my own workload within the team and juggling my workload with my other modules that I was taking in school.
- Client Negotiation skills: I was able to apply the negotiation skills that I learnt from a module to achieve integrative outcomes for the client and the team, and what are the tactics that are readily available to deal with such situations.
- Applied Project Management Skills: The FYP experience has been an extension of what I have learnt in Software Engineering and I was able to refine my skills in scope management, schedule management and further extend the practicality of metrics being used within a project.
Sponsor Comment:
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.