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. Executes system in a manner that demands abnormal amounts of resources






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






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






4. 'single dot rule'






5. (smell) code is repeated in multiple places






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






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






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






9. A relationship between objects.






10. Representational State Transfer.






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






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






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






14. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data






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






16. Formal testing against end user specifications






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






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






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






20. Testing the whole system for functionality






21. A method that initializes a newly instantiated object






22. A way to automatically grade code based on heuristics






23. Each line of code is covered once






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






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






26. Comprehensive description of software's intended purpose






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






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






29. 3rd step of requirements gathering






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






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






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






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






34. Techniques for composing objects to form larger structures






35. Figuring out what the requirements are






36. Absence of lifecycle






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






38. A movement that promotes common formats for data.






39. Test the run - time performance of the system






40. The degree to which code is free of defects






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






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






43. Constraints on the design due to external factors






44. Derived methods should not assume more or deliver less






45. Reusable - abstract 'blocks' of design






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






47. (smell) Smell deodorant






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






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






50. Evaluates upper limits of operational parameters