As a senior coder and experienced test engineer, you have been given a new software testing future key project where you were asked to develop and conduct test cases that would occur throughout the software development life cycle. Your project first was to choose between the following three possible key project software implementations:
- COTS and Contract software
- Data Warehouse software
- Web-based software
Now that you have selected your software project, it is time to plan the testing process.
Each week you will be working on a key assignment. You will create a proposal to be used at a Test Planning Milestone Meeting (TPMM) meeting. To begin your key assignment, create the following sections in your proposal:
- Title
- Tables of contents
- Software Testing Environment
- The importance of unit/usability/system test planning process
- Characteristics of test plans
- Test planning approach
- Approach taken for your test project
- Outline of the test plan
- Scope (identification, system overview)
- System description and operation (name of test sites, test configuration)
- Test identification & test levels
- Planned tests & test schedules
- Requirement traceability
- Summary
- Reference
For your Section 2 of the project due this week, it will be critical to provide to your customer an identification of the software-testing process through developing the structure for the unit/usability/system test plan, method/procedure, and report. The client is not sure of your intentions with the test-planning process; therefore, he would like to understand the test planning concept. For this assignment fill in the following sections:
- The importance of unit/usability/system test planning process
- Characteristics of test plans
- Test planning approach
- Approach taken for your test project
- Outline of the test plan
- Scope (identification, system overview)
- System description and operation (name of test sites, test configuration)
- Test identification & test levels
- Planned tests & test schedules
- Requirement traceability
- Summary
- Reference
undefined
it will be critical to provide the customer with a populated requirements traceability matrix (RTM):
- The creation of at least 20 “shall” driven requirements. Ensure that you have more than just functional requirements which means you may need to adjust the list of requirements you started in Week 1. At a minimum:
- 5 external interface requirements, 5 safety, 5 security, 5 performance that will support unit, usability and system test; and the draft unit/usability/system test plan, test method/procedure, and test report
- You may find it easier to create a separate RTM for unit, usability, and system tests.
- Ensure requirements are written in a testable manner, are not vague, and capture the required functions needed to satisfy each area: safety, security, etc.
This again will become part of the overall final product due in Unit 5 and should be added to your Appendix A in the final project.
undefined
For this assignment, you will research the factors that contribute to an ideal test environment for your software and prepare a requirements traceability matrix (RTM). Locate a RTM template on the Internet to use as your starting point. RTM should have at least 3 columns: ID, Requirements, and Component. ID should be the unique ID of the requirement. Requirements should be the actual testable “shall” requirement. Component should be the component(s) of the software or system that has been allocated for this functionality (i.e., user interface, security, etc.).
In your key assignment document, provide the following:
- Create a section that describes an environment supportive of software testing. Describe all required resources including the skills and competencies of the testing staff.
- Begin development of your requirements traceablity matrix (RTM). Be sure to provide a link to the source of the template used. For this assignment, you are just populating the ID and description of all requirements subject to test. You will complete the rest of the RTM in Week 3.
The client has requested the requirements and design team to incorporate all changes or recommendations from previous reviews concerning the view of the software-testing process, the RTM and the unit/usability/system test plan, and the test method/procedure and test report.
The second request of the client is to provide an outline for the draft regression test plan, method/procedure and report, and requirements to be regression tested. Include this as a section to your key assignment document. After performing this consolidation, provide this document to your individual upload area.
0 comments