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. Evaluates upper limits of operational parameters






2. People who care about the outcome






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






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






5. Recognizable indicator that something may be wrong with code






6. Protecting the embodiment of an idea






7. Representational State Transfer.






8. (smell) Smell deodorant






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






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






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






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






13. 1st step of requirements gathering






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






15. A relationship between objects.






16. How well your fulfil your requirements






17. A few sentences summarizing a use case






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






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






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


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






22. The rights governing the ownership and disposition of technology






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






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






25. A movement that promotes common formats for data.






26. Tasks that a system must be able to perform






27. Comprehensive description of software's intended purpose






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






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






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






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






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






33. The things a system must do






34. A way to automatically grade code based on heuristics






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






36. Description of possible sequences of interactions between a user and the system.






37. (smell) If a set of variables are used together in multiple places






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






39. 3rd step of requirements gathering






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






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






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






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






44. Reusable - abstract 'blocks' of design






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






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






47. Absence of lifecycle






48. (smell) code is repeated in multiple places






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






50. Each line of code is covered once