skip to main |
skip to sidebar
Send all documents for printing and compilation
Order of report:
- Cover page
- Main Content (Content of all Main Documents)
- Software Project Plan
- Planned Timeline
- Task Allocation
- Quality Assurance
- Change Management Report
- Change Request Report
- Request for Enhancement/Modification Report
- Defects Report
- Software Requirements Specification
- Use Case for Registered Users
- Use Case for Normal Users
- Use Case for Administrator
- Use Case for Ticketing Officer
- Software Design Specification
- Relationships
- Data Dictionary
- Sample User Interface
- Software Test Specification
- Test Case for Add Movie
- Test Case for Booking
- Test Case for Registration
- Test Results
- Project Tasks
- Iteration Plan
- Iteration 1 Plan
- Iteration 2 Plan
- Iteration 3 Plan
Meeting Time: 19 00 hrs to 22 45 hrs
Attendance: Full
Finalized and Approved all documents:
- Software Project Plan
- Software Requirements Specifications
- Software Design Specifications
- Software Test Specifications
Meeting Time: 18 45 hrs to 21 30 hrs
Attendance: 3 present, 2 absent
Test cases up and done.
Started evaluating the test results:
- Registration
- Passed test cases - 83.3%
- Failed test cases - 16.7%
- Add movie
- Passed test cases - 78.6%
- Failed test cases - 21.4%
Meeting Time: 19 00 hrs to 23 00 hrs
Attendance: Full
Test plan is yet to be finalized as the test cases and test results are yet to be done.
Started on the testing the system with respect to the test cases.
Actual results, passed/failed criteria and remarks added in the test cases.
Section 6 - Summary
Acceptance testing shall be carried out prior to acceptance of the SRS by the MOD PM. The acceptance tests shall be performed against an Acceptance Test Specification that are agreed between the Software Design Authority, the Design Authority and the MOD PM. The results should be recorded in the Acceptance Test Report. Acceptance shall be based upon the content of the Software Safety Case, the signing of the SRS Certificate of Design and satisfactory acceptance testing.
Binary images (including firmware) incorporating SRS shall be produced in a way that preserves the integrity of the SRS. The replication shall be controlled, with the version and configuration of firmware be uniquely identified in accordance with Def Stan 00-22. The binary images (including firmware) is checked by comparison with the master copy of the image. The replication process is subjected to safety analysis as part of the safety analysis of the SRS development process. The replication process and associated checks shall be defined so that the safety assurance is appropriate or the level of integrity of the SRS.
Task 3:- The reuse module might have processes that are not require or do not serve it purpose in the project. This redundant process will or might affect other processes indirectly, so software may not behave as expected
- Too many reuse functions might not work well together
Task 4:- Portability of a function or software enables it to run on multiple platforms, so it reduces development time for company that wants to engage different user using different platforms
- e.g. Surfing the web using IE or firefox
- Internal - correctness, reparability, maintainability
- External - performance, visibility, understandability
- Product - usability, portability
- Process - timeliness, interoperability
