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 that verifies that individual units of source code are working






2. Degree to which the system meets the specified requirements and development standards






3. Verifies that system is protected against improper penetration






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






5. (smell) code is repeated in multiple places






6. A few sentences summarizing a use case






7. Single step in a lifecycle






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






9. Protecting the embodiment of an idea






10. A relationship between objects.






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






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






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






14. Constraints on the design due to external factors






15. 4th step of requirements gathering






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






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






18. (smell) One class delegates all of its requests to another class






19. Comprehensive description of software's intended purpose






20. 'single dot rule'






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






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






23. Reusable - abstract 'blocks' of design






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






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






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






27. Derived methods should not assume more or deliver less






28. Evaluates upper limits of operational parameters






29. Techniques for composing objects to form larger structures






30. Test the run - time performance of the system






31. 3rd step of requirements gathering






32. The things a system must do






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






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






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






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






37. People who care about the outcome






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






39. (smell) Smell deodorant






40. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.






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






42. 2nd step of requirements gathering






43. Lack of errors in code - readability etc






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






45. Testing the whole system for functionality






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






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






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


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






50. Figuring out what the requirements are