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. 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


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






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






4. Formal testing against end user specifications






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






6. A set of rules that define the combinations of symbols that are considered to be correctly structured in a specific programming language. Example: In many programming languages - statements are terminated by a semicolon.






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






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






9. Series of phases through which software is developed






10. (smell) Classes using things that should be private in other classes






11. Verifies that system is protected against improper penetration






12. Small - behaviour- preserving - source- to- source transformation






13. Lack of errors in code - readability etc






14. Description of possible sequences of interactions between a user and the system.






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






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






17. (smell) A method using another class more than its own






18. (smell)class with too many instance variables or too much code






19. The rights governing the ownership and disposition of technology






20. The things a system must do






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






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






23. Techniques for composing objects to form larger structures






24. Single step in a lifecycle






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






26. An effective method expressed as a finite list of well- defined instructions for solving a problem.






27. (smell) many parameters are being passed into a method






28. 'single dot rule'






29. 1st step of requirements gathering






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






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






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






33. People who care about the outcome






34. Freezing the state of the source code at a particular point






35. A way to automatically grade code based on heuristics






36. 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


37. Recognizable indicator that something may be wrong with code






38. A relationship between objects.






39. Contract between inventor - assignee and state giving a time and geographically limited monopoly






40. Reusable - abstract 'blocks' of design






41. The degree to which code is free of defects






42. Improve the internal design and implementation of code without affecting external behavior






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






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






45. 3rd step of requirements gathering






46. Test the run - time performance of the system






47. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






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






49. A few sentences summarizing a use case






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