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. An effective method expressed as a finite list of well- defined instructions for solving a problem.






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


3. Constraints on the design due to external factors






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






5. Lack of errors in code - readability etc






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






7. Reusable - abstract 'blocks' of design






8. Test the run - time performance of the system






9. Models ->code work is done to keep models in sync with code






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






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






12. Absence of lifecycle






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






14. A powerful motivator for change






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






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






17. A way to automatically grade code based on heuristics






18. Representational State Transfer.






19. A few sentences summarizing a use case






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






21. A method that initializes a newly instantiated object






22. (smell) client needs to use one object to get another and then use that one to get another






23. Each condition is covered twice (true - false)






24. 1st step of requirements gathering






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






26. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu






27. Word - logo or symbol used to distinguish one organization's wares and services from another's






28. Comprehensive description of software's intended purpose






29. 'single dot rule'






30. (smell) Smell deodorant






31. Reusable - abstract 'blocks' of design






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






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






34. Derived methods should not assume more or deliver less






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






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






37. Diagram used to show how information flows around the system






38. Techniques for composing objects to form larger structures






39. How developed code is (testing - documentation etc)






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






41. Formal testing against end user specifications






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






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






44. People who care about the outcome






45. Recognizable indicator that something may be wrong with code






46. Verifies that system is protected against improper penetration






47. The degree to which code is free of defects






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






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






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