You point out to Terrence that no product testing is listed on the WBS, and the process for handing the product over to the client is not specified. Terrence spends the afternoon thinking about your comments. The next day he comes to you with the following list:Testing and handover:System test planSystem test casesSystem test resultsAcceptance test planAcceptance test casesUser documentationSystem acceptance and handoverYou agree that this list covers the testing and handover activities for this particular software project, and you ask Terrence to include the list in his WBS. However, Terrence is not sure where to include these activities. What do you tell him?Question 2Select one:a."Testing and handover" becomes 4.6 under "System construction" and the rest are listed as 4.6.1 - 4.6.7b.System test plan, System test cases, and System test results become 2.1.6 - 2.1.8 and the rest of the sub-list becomes 5.0c.This list becomes 3.0 (with subordinate activities 3.1 - 3.7), and "Detail software design" and "System construction" become 4.0 and 5.0 respectively (with their relevant subordinate activities also being renamed) d."Testing and handover" becomes 5.0, and the rest are listed as 5.1 - 5.7

management 0.0 New software implementation 2.0 Project requirements 1.1 Planning 1.1.1 Define 1.2.1 Conduct scope kick-off meeting 1.1.2 Develop resource plan 1.2.2 Weekly 1.1.3 Develop comunication plan 1.1.4 Develop risk plan 1.1.5 Develop change control plan 1.1.6 Develop quality plan 1.1.7 Develop purchase plan 1.1.8 Develop cost plan 1.1.9 Develop project schedule 1.2 Meetings status meeting 1.2.3 Monthly tactical meeting 1.2.4 Project closing meeting 1.3 Administration 1.3.2 Programme office 1.3.1 Standards 1.3.1.1 Document performance standards 1.3.2.1 Develop programme office charter 1.3.2.2 Assign programme office resources 1341.2 Document reporting standards 1.3.1.3 Document naming conventions 1.3.1.4 Document housekeeping standards 2.1 Software requirements 2.1.1 Create draft software requirements 2.1.2 Review draft software requirements 2.1.3 Update draft software requirements 2.1.4 Review final software requirements 2.1.5 Software requirements approved 2.2 User documentation 2.1.1 Create draft user documentation 2.1.2 Review draft user documentation 2.1.3 Update draft user documentation 2.1.4 Review final user documentation 2.1.5 User documentation approved 2.3 Training programme materials 2.4 Hardware 3.0 Detail lia ely design 3.1 Create initial software design 3.2 Review initial software design 3.3 Update initial software design 3.4 Review final software design 3.5 Software design approved 4.0 System construction 4.1 Configure software 4.2 Customer user documentation 4.3 Customise training programme materials 44 Install hardware 45 Implementation and future support