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 where modules are combined and tested as a group






2. Constraints on the design due to external factors






3. Single step in a lifecycle






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






5. 2nd step of requirements gathering






6. Verifies that system is protected against improper penetration






7. A way to automatically grade code based on heuristics






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






9. A relationship between objects.






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






11. Delaying the creation of an object - calculation of a value or another expensive process until first needed.






12. A method that initializes a newly instantiated object






13. A movement that promotes common formats for data.






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






15. Absence of lifecycle






16. Each team member given set of features to work on






17. (smell) code is repeated in multiple places






18. How well your fulfil your requirements






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






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






21. Reusable - abstract 'blocks' of design






22. Testing the whole system for functionality






23. A few sentences summarizing a use case






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






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






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






27. Recognizable indicator that something may be wrong with code






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






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






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






31. (smell) Smell deodorant






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






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






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






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






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






37. Iterative - incremental framework for project management.






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






39. The degree to which code is free of defects






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






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






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






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






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






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






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






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






48. 1st step of requirements gathering






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






50. Comprehensive description of software's intended purpose







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests