Difference between revisions of "IS480 Team wiki: 2013T2 DR.Jean Labs The Team Final Quality of the Product"
Line 67: | Line 67: | ||
<!-- content --> | <!-- content --> | ||
+ | ==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. | ||
+ | |||
+ | {| border="1" | ||
+ | |- style="background:blue; color:white" | ||
+ | |align="center"| Stage | ||
+ | |align="center"| Specification | ||
+ | |align="center"| Modules | ||
+ | |- | ||
+ | |||
+ | |rowspan="2"| Project Management | ||
+ | || Minutes | ||
+ | || Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7 | ||
+ | |- | ||
+ | |||
+ | || Metrics | ||
+ | || Bug metrics | ||
+ | |- | ||
+ | |||
+ | || Requirements | ||
+ | || Story cards | ||
+ | || [http://www.agilemodeling.com/artifacts/userStory.htm CRUD Customer], [http://www.agilemodeling.com/artifacts/userStory.htm Trend Analytic] | ||
+ | |- | ||
+ | |||
+ | |rowspan="4"| Analysis | ||
+ | || Use case | ||
+ | || [http://en.wikipedia.org/wiki/Use_case_diagram overall] | ||
+ | |- | ||
+ | |||
+ | || System Sequence Diagram | ||
+ | || [http://en.wikipedia.org/wiki/System_Sequence_Diagram client], [http://en.wikipedia.org/wiki/System_Sequence_Diagram server] | ||
+ | |- | ||
+ | |||
+ | || [http://en.wikipedia.org/wiki/Business_Process_Modeling_Notation Business Process Diagram] | ||
+ | || | ||
+ | |- | ||
+ | |||
+ | || Screen Shots | ||
+ | || CRUD Customer, Trend Analysis | ||
+ | |- | ||
+ | |||
+ | |rowspan="2"| Design | ||
+ | || [http://en.wikipedia.org/wiki/Entity-relationship_model ER Diagram] | ||
+ | || 1, 2, 3 | ||
+ | |- | ||
+ | |||
+ | || [http://en.wikipedia.org/wiki/Class_diagram Class Diagram] | ||
+ | || [http://en.wikipedia.org/wiki/Class_diagram 1], [http://en.wikipedia.org/wiki/Class_diagram 2], [http://en.wikipedia.org/wiki/Class_diagram 3] | ||
+ | |- | ||
+ | |||
+ | |||
+ | || Testing | ||
+ | || Test plan | ||
+ | || [[IS480_Midterm_Wiki#Testing: | instructions]] | ||
+ | |- | ||
+ | |||
+ | |rowspan="3"| Handover | ||
+ | || Manuals | ||
+ | || User tutorial, Developer manual, Setup manual | ||
+ | |- | ||
+ | |||
+ | || Code | ||
+ | || client server | ||
+ | |- | ||
+ | |||
+ | || [http://en.wikipedia.org/wiki/Deployment_diagram Deployment Diagram] | ||
+ | || [[IS480_Midterm_Wiki#Deployment: | 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 [[IS480_Final_Wiki#Project_Deliverables: | 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. |
Revision as of 14:39, 8 April 2014
{ In a nutshell } | { Acceptance Wiki } | { MidTerm Wiki } | { Final Wiki } |
<< Project Summary >> | << Project Management >> | << Quality of the Product >> | << Our Reflections >> |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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.