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. A design pattern that allows behaviour to be added to an existing object dynamically.






2. (smell) Making one change requires changes in multiple places






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






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






5. The degree to which code is free of defects






6. A way to automatically grade code based on heuristics






7. A few sentences summarizing a use case






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






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


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






11. Recognizable indicator that something may be wrong with code






12. A movement that promotes common formats for data.






13. Ways to express the system's subsystems and their relationship






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






15. 4th step of requirements gathering






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






17. Reusable - abstract 'blocks' of design






18. Techniques for composing objects to form larger structures






19. Tasks that a system must be able to perform






20. Protecting the embodiment of an idea






21. How well your fulfil your requirements






22. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






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






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






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






26. Reusable - abstract 'blocks' of design






27. Testing tactic based on whether inputs and outputs match up for required functionality






28. 3rd step of requirements gathering






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






30. Verifies that system is protected against improper penetration






31. A computer program that divides code up into functional components






32. Figuring out what the requirements are






33. A powerful motivator for change






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






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






36. Absence of lifecycle






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






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






39. (smell) code is repeated in multiple places






40. Each line of code is covered once






41. Testing the whole system for functionality






42. Single step in a lifecycle






43. 2nd step of requirements gathering






44. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






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






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






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






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






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






50. Derived methods should not assume more or deliver less