hw3

pdf

School

San Jose State University *

*We aren’t endorsed by this school

Course

287

Subject

Electrical Engineering

Date

Jan 9, 2024

Type

pdf

Pages

Uploaded by CaptainOryx4068

Vishnu Vardhan Reddy Ireddy 016816176 Homework – 3 CMPE 287

Question #1: Software Integration Testing A. “ The top-down integration approach in software testing involves integrating modules starting from the top level of the control hierarchy and progressing downwards. The main control module is first tested with stubs (simplified versions) of its subordinate modules, which are gradually replaced with the actual modules. This allows for testing of major functionalities early in the development cycle. ” B. Top-Down Integration Approach : Integration Order: Breadth-First (Left Order) IS: Integrated System Mi’: software stub for Module Mi Step #1: IS = M1 + M2 (need: M3’, M13’, M4’, M5’) Step #2: IS = IS + M3 (need: M4’, M5’, M13’, M6’) Step #3: IS = IS + M13 (need: M4’, M5’, M6’, M7’) Step #4: IS = IS + M4 (need: M5’, M6’, M7’, M8’) Step #5: IS = IS + M5 (need: M6’, M7’, M8’, M9’, M14’) Step #6: IS = IS + M6 (need: M7’, M8’, M9’, M14’, M10’) Step #7: IS = IS + M7 (need: M8’, M9’, M14’, M10’, M11’, M12’) Step #8: IS = IS + M8 Step #9: IS = IS + M9 Step #10: IS = IS + M14 Step #11: IS = IS + M10 Step #12: IS = IS + M11 Step #13: IS = IS + M12 C. Step #1: Requires 3 stubs (M2’, M3’, M13’) Step #2: 2 more stubs are needed as M2 is integrated (M4’, M5’) Step #3: No new stubs are needed as M3 is integrated Step #4: 1 new stub as M13 is integrated (M7’) Step #5: 1 new stub as M4 is integrated (M8’) Step #6: 2 new stubs as M5 is integrated (M9’, M14’) Step #7: 1 new stub as M6 is integrated (M10’) Step #8: 2 new stubs as M7 is integrated (M11’, M12’) Steps #9 to #14: No new stubs as remaining modules (M8, M9, M14, M10, M11, M12) are leaf nodes. Total Test Stubs = 3 (initial) + 2 (step 2) + 1 (step 4) + 1 (step 5) + 2 (step 6) + 1 (step 7) + 2 (step 8) = 12 stubs

D. “ The bottom-up integration approach in software testing involves integrating modules from the lowest levels first, gradually moving upwards in the control hierarchy. In this method, high-level functionalities are tested after the lower-level modules have been integrated, often using test drivers to simulate higher-level modules not yet integrated. ” E. Bottom-Up Software Integration : Integration Order: Depth-First (Bottom-Up) IS: Integrated System Mi”: software driver for Module Mi Step #1: IS1 = M8 + M4 (need: M2”) Step #2: IS1 = IS1 + M9 (need: M5”, M2”) Step #3: IS1 = IS1 + M14 (need: M5”, M2”) Step #4: IS1 = IS1 + M5 (need: M2”) Step #5: IS1 = IS1 + M2 (need: M1”) Step #6: IS2 = M10 + M6 (need: M3”, M1”) Step #7: IS2 = IS2 + M6 (need: M3”, M1”) Step #8: IS3 = M11 + M7 (need: M13”, M1”) Step #9: IS3 = IS3 + M12 (need: M13”, M1”) Step #10: IS3 = IS3 + M7 (need: M13”, M1”) Step #11: IS3 = IS3 + M13 (need: M1”) Step #12: IS = IS1 + IS2 (need: M3”, M1”) Step #13: IS = IS + M3 (need: M1”) Step #14: IS = IS + M1 F. Step #1: 1 driver (M4's parent, M2) Step #2: 1 driver (M5's parent, M2) Step #3: Same driver as Step #2 (M5's parent, M2) Step #4: Same driver as previous steps (M5's parent, M2) Step #5: No driver needed as M2 is integrated Step #6: 1 driver (M6's parent, M3) Step #7: Same driver as Step #6 (M6's parent, M3) Step #8: 1 driver (M7's parent, M13) Step #9: Same driver as Step #8 (M7's parent, M13) Step #10: Same driver as previous steps (M7's parent, M13) Step #11: No driver needed as M13 is integrated Step #12: 1 driver (M3's parent, M1) Step #13: No driver needed as M3 is integrated Step #14: No driver needed as M1 is integrated Total Test Drivers = 1 (step 1) + 1 (step 2) + (step 6) + 1 (step 8) + 1 (step 12) = 5 drivers

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

Question #2: Branch-Based Software Testing A. Class test order is 1. C1, C11 2. C7, C0 3. C2, C6 4. C3, C8, C13, C9 5. C4, C10, C12 6. C5, C14

B. Firewall for C1: Firewall for C7:

C. “ Classes in the firewall which are not directly affected by C1, but must be re-integrated are C2, C3, C4, C8, C12, C13, C14 ” “ Classes in the firewall which are not directly affected by C7, but must be re-integrated are C0, C3, C5, C9, C10, C12, C13, C14 ” D. Class re-test order for C1 class firewall: 1. C1 2. C0, C5 3. C2, C8 4. C3, C13 5. C4, C12 6. C14 Class re-test order for C7 class firewall: 1. C7 2. C2, C6 3. C0, C3, C13, C9 4. C4, C12, C8, C10 5. C5, C14

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

Question #3 Testing a selected AI mobile App A. a. Context model: “ context -> Illumination, Background, Angle ” “ Illumination -> Bright, Dark ” “ Background -> Same, Different ” “ Angle -> Side, Top ” b. Input Classification model: “ input -> Food, Non-Food ” “ Food -> Occurrence, Type, State ” “ Occurrence -> Multiple Items, Single Item ” “ Type -> Animal-Based, Plant-Based ” “ State -> Cooked, Uncooked ” “ Non-Food -> Food, Non-Food ” c. Output Classification model: “ output -> Food Detection -> Food, Non-Food ” “ Food -> Food Classification -> Accurate, Inaccurate ”

d. 3D decision table B. Test complexity: “ The test suite's complexity is reflected in its comprehensive coverage of various input and context combinations, challenging the AI models' robustness. Given the variety of inputs (food type, state, packing) and contexts (illumination, background, angle), the test complexity is high. ”

C. Bugs in the AI testing tool: 1. “ Title: Unable to create a model tree with single leaf node at level one in large trees ” Steps to reproduce: - “ create a function and start building an input tree ” - “ add multiple nodes to the parent node ” - “ now add multiple nodes to one of the child node and try to save it ” - “ it gives out an error saying ‘child nodes’ cannot be empty for a node ” Expected Result: “ We should be able to create test cases with that tree too because not all the use cases for testing will be the same ” Actual Result: Error creating the model Visual Proof: Severity: Low Priority: Medium

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

2. Title: “ Function already exist error while editing a function ” Steps to reproduce: - “ create a function if not already done and create all the models and save it ” - “ now edit any of the models and try to save it ” Expected Result: “ We should be able to update the existing function when given an option called edit or else we need to have an option called ‘Clone’ for such functionality ” Actual Result: “ We are unable to edit the existing function but able to save it under a new name which increases the resource cost as the storage increases ” Visual Proof: Severity: Low Priority: Low

3. Title: “ Column names are not properly designed ” Steps to reproduce: - “ create the models having only single node in tree and then children for it ” - “ save them and go to test suite ” - “ we can see the column names won’t be in a proper understandable format ” Expected Result: “ Column names are proper and understandable ” Actual Result: “ Column names are being appended improperly with the parent node names ” Visual Proof: Severity: Low Priority: Low