Test your basic knowledge |

Software Engineering Vocab

Subjects : engineering, it-skills
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. (smell) many parameters are being passed into a method






2. Evaluates upper limits of operational parameters






3. A powerful motivator for change






4. 1st step of requirements gathering






5. Series of phases through which software is developed






6. The rigorousness of the tests that are able to be placed on the code






7. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






8. Testing where modules are combined and tested as a group






9. Approach to team management that splits management up into two people with separate tasks






10. Testing that verifies that individual units of source code are working






11. Single step in a lifecycle






12. Each possible path through the code is covered






13. Testing can show the presence but not absence of errors

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


14. Testing the whole system for functionality






15. (smell) A class whose only purpose is to hold data






16. Testing can show the presence but not absence of errors

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


17. Force software to fail in order to see how it recovers






18. Testing tactic that looks at all ways that data can flow through the code






19. (smell) code is repeated in multiple places






20. Executes system in a manner that demands abnormal amounts of resources






21. Techniques for composing objects to form larger structures






22. (smell) If a set of variables are used together in multiple places






23. (smell) method has too many statements - loops or variables






24. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






25. People who care about the outcome






26. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.






27. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.






28. Diagram outlining the tasks that are going to be performed by the user






29. A relationship between objects.






30. The rights governing the ownership and disposition of technology






31. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






32. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






33. Reusable - abstract 'blocks' of design






34. Lack of errors in code - readability etc






35. Verifies that system is protected against improper penetration






36. Comprehensive description of software's intended purpose






37. Test whether or not tasks can be accomplished efficiently by all levels of users






38. Object oriented programming; using objects to solve problems.






39. (smell) Smell deodorant






40. Figuring out what the requirements are






41. One or two paragraphs of text outlining a use case






42. Test cases made -> code compiles -> make code pass






43. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.






44. AKA: Object - Entity - or Value - An entity that can be constructed at run - time - passed as a parameter - returned from a subroutine - or assigned into a variable.






45. Derived methods should not assume more or deliver less






46. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






47. An operator used to denote anonymous functions or closures.






48. Developing a plan for a product - system or component. 'how' a system should perform a task






49. A design pattern that allows behaviour to be added to an existing object dynamically.






50. Formal document outlining a task that needs to be performed on a system