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. Comprehensive description of software's intended purpose






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


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






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






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






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






7. Protecting the embodiment of an idea






8. A method that initializes a newly instantiated object






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






10. Techniques for composing objects to form larger structures






11. 'single dot rule'






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






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






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






15. (smell) code is repeated in multiple places






16. Test the run - time performance of the system






17. 3rd step of requirements gathering






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






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






20. Verifies that system is protected against improper penetration






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






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






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






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






25. Recognizable indicator that something may be wrong with code






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






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






28. Constraints on the design due to external factors






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






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






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






32. Lack of errors in code - readability etc






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






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






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






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






37. People who care about the outcome






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






39. Reusable - abstract 'blocks' of design






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






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






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






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






44. Figuring out what the requirements are






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






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






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






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






49. A relationship between objects.






50. 4th step of requirements gathering