A Few Review Questions

1. A Few Review Questions Dan Fleck Spring 2009

2. System Test Case What is wrong with this system test case? (formatting is wrong, but what else is?)

3. System Test Case What is wrong with this system test case? (formatting is wrong, but what else is?)

4. Many project managers fail. What are some of the main reasons projects fail and how can you lower your risk of failure?

5. Problems with these requirements? • Users shall have an ATM Card • The game system shall provide a way to regenerate players and provide a scoring mechanism • The game system shall be fun to play • The game system may be accessible for the disabled

6. What is the difference between design and analysis phase? • Analysis describes WHAT the system must do, design describes HOW the system will do it. • Analysis describes the problem domain, design describes the solution domain

7. Define coupling (and I don’t mean the terrible show from 2000) • Define cohesion Cast of Coupling (2000)

8. You and Dracula are both afraid if stakeholders get upset. Why?

9. Define critical path and tell me when I should pack for the cruise

10. Carl and Bob are racing, but are friends and want to finish in a tie (at the same time), what is the schedule dependency that describes this (FS, FF, SF, SS) best?

11. Why is it necessary to quantify your plans? What is expectation management? Why is it important? Give an example from your life where it was not done and the results?

12. Define verification • Define validation • Define IV&V • If my software requirements say the background should be blue, but I like red better, will I fail in verification, validation or both?

13. What is dynamic verification? • What is an example of static verification? • Which is FindBugs?

14. What is a stopping rule for testing? Or what do I mean by that? • A stopping rule is a rule to determine when you can “stop” testing. Older testing techniques provided no quantifiable stopping rule. Newer techniques using coverage criteria do provide a stopping rule • Using the older techniques, when do you stop testing?

15. My goal was to get 30 questions for the review by the time Heros starts at 9pm. It is now 8:30pm and I have 18 slides. I started at 7pm. • What are some metrics I should calculate now to understand my Heros Watching Potential (HWP) ? • If I decide to watch it now, and finish the slides in the morning, how much earlier do I need to wake up tomorrow?

16. What are some advantages and disadvantages of metrics based on lines of code?

17. In the software fault, error and failure model, is a software fault still present if it does not generate a failure? • Yes… the failure may appear later or once new code is added, but the fault is there regardless.

18. Define white box and black box testing

19. Don’t forget… just knowing the answers to these questions is NOT enough. Look at the review guide online for the full list of things to know!!!!

20. Explain the steps in mutation testing • How do I kill a mutant? • Create a set of test cases that all pass • Induce small changes to the program: mutants • Find tests that cause the mutant programs to fail: killing mutants • Failure is defined as different outputfrom the original program • A mutant is a variation of my software created by changing lines of code. By introducing changes to the source code, I can detect if the testing done is thorough or not. • I kill a mutant by writing a test case that fails for the mutant code, but not for the original code

21. Diagrams • Still know how to draw these diagrams? I would. • Use case diagram • Class diagram • Sequence diagram • Level 0 Context diagram • Activity diagram (with/without swimlanes)

22. I hope you enjoyed the class. I did!