CATEGORIES:
BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism
Technical Specifications
SQL Database
Training
Implementation
Perform System test
Verify code
Verify System
Installation
Install new programs into environment
Obtain user acceptance of production system
Monitor system
Verify performance
Verify functionality
Software Testing Description
Final Studio Paper
Partly due to the educational nature of the project, it is limited by a rather large number of factors:
The following hard deadlines:
ü Project deadline: May 1st, 2016
ü Intermediate presentation: May 10th, 2016
ü Final presentation: May 16th, 2016
• A holiday week January 1th - 6th and public holidays on January 7th
• Exam periods December 21th - 31th and April 18th – May 15th
• Scheduled lectures and homework March 28th- April 9 th
Risk management
During the project, several things can go wrong. The risks that have a high impact and that are most likely to occur will be treated here. Risks can be separated between internal risks.
| Risks | Probability | Prevention |
| Illness or absence | Medium | try to be healthy |
| Incomprehension of each other | High | during weekly meetings, make sure understanding of each other and given task |
| too many planned features lead to non user-friendly design | High | Every item should have a priority. |
| loss of main information or part of project | Medium | The base assumption Should be that there is a backup of every single piece of information at any single time. |
| Lack of Skills and knowledge of tools needed for statistical analysis | Medium | Independent learning the necessary information |
| Deficiency in the knowledge and understanding of the problem and its solution | High | Try to understand what type of knowledge insufficiently and take advise someone who expert in this question |
Communications and reporting
| Milestones | Description | Planned Date |
| M1 | Start Project | 10.09.15 |
| M2 | Start Planning | 5.10.15 |
| M3 | Design Document (complete) | 20.10.15 |
| M4 | Start Execution | 5.11.15 |
| M5 | Confirm Execution | 10.01.16 |
| M6 | Acceptance Test Plan | 15.02.16 |
| M7 | Release Product | 1.03.16 |
| M8 | Project end | 15.05.16 |
Delivery plan and schedule
| User Iinterface Mock-up | 1.09.15 |
| Literature Search | 20.09.15 |
| Data Model | 5.10.15 |
| Draft for Statement of Work | 20.10.15 |
| Draft for Software Project Management Plan | 4.11.15 |
| Software Requirements Specification – general requirements for search engine tester | 17.11.15 |
| Software Quality Assurance and Verification & Validation Plan | 20.12.15 |
| Code Prototype | 25.12.15 |
| Presentation of Prototype to Client | 10.01.15 |
| Prototype - more queries and analysis | 15.01.15 |
| Software Testing Description | 1.03.15 |
| System Integration | 5.03.16 |
| Final Product Delivery - Final User Manual Final Presentation to Mentor | 20.04.16 |
Quality assurance
The following methods and techniques will be used to develop project:
1) UML, State Charts: These techniques will be used to formalize and describe operations in the test harness that involve user events and mode changes.
2) Coding Standards: We will use the defined coding standard and we will try ensuring that all produced code is consistent with this standard.
3) Traceability: We will use standard traceability matrices to ensure that all requirements and all
Design specifications are fulfilled by the final products.
Date: 2016-01-05; view: 762
| <== previous page | | | next page ==> |
| Project Deliverables | | | I Spaţiul limitat în locurile de detenţie |