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. Test cases made -> code compiles -> make code pass






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






3. A powerful motivator for change






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






5. 4th step of requirements gathering






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






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


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






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






10. A way to automatically grade code based on heuristics






11. A method that initializes a newly instantiated object






12. Testing the whole system for functionality






13. Single step in a lifecycle






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






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






16. Each line of code is covered once






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






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






19. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






20. Evaluates upper limits of operational parameters






21. Formal testing against end user specifications






22. Tasks that a system must be able to perform






23. A movement that promotes common formats for data.






24. The things a system must do






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






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






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






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






29. The degree to which code is free of defects






30. 1st step of requirements gathering






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






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






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






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






35. Constraints on the design due to external factors






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






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






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






39. Reusable - abstract 'blocks' of design






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






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






42. A few sentences summarizing a use case






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






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






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






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






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






48. People who care about the outcome






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






50. Reusable - abstract 'blocks' of design







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