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. Force software to fail in order to see how it recovers






2. People who care about the outcome






3. A way to automatically grade code based on heuristics






4. Each line of code is covered once






5. A movement that promotes common formats for data.






6. Formal testing against end user specifications






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






8. A relationship between objects.






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


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






11. Recognizable indicator that something may be wrong with code






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






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






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






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






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






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






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






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






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






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






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






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






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


25. 'single dot rule'






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






27. Iterative - incremental framework for project management.






28. The things a system must do






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






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






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






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






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






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






35. Tasks that a system must be able to perform






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






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






38. 1st step of requirements gathering






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






40. A powerful motivator for change






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






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






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






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






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






46. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






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






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






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






50. Derived methods should not assume more or deliver less