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. (smell) Making one change requires changes in multiple places






2. Reusable - abstract 'blocks' of design






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






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






5. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






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


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






8. Series of phases through which software is developed






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






10. Recognizable indicator that something may be wrong with code






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






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






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


14. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.






15. Formal testing against end user specifications






16. Single step in a lifecycle






17. Iterative - incremental framework for project management.






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






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






20. Protecting the embodiment of an idea






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






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






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






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






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






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






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






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






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






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






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






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






33. (smell) Smell deodorant






34. 'single dot rule'






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






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






37. The rights governing the ownership and disposition of technology






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






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






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






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






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






43. A movement that promotes common formats for data.






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






45. Reusable - abstract 'blocks' of design






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






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






48. Testing the whole system for functionality






49. The things a system must do






50. Representational State Transfer.







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