#2 Testing plan. Unit testing: consider every possible part of this system (scheduling, invoicing, reporting) and create some sample test plans for each. You should have between 3-5 actions per system module. Integration testing: If this new system is expected to interface with other systems (Parts Inventory system), then a plan should be put in place to test whether the data is being transmitted/read accurately. Students should have 2-3 actions for the integration testing. System testing: create a plan to ensure that the entire system is working seamlessly. There should be several scenarios written from start to finish and system should be able to read/write information throughout the entire scheduling, obtaining parts, rescheduling, and invoicing process. Provide 2-3 scenarios for the system testing