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. The things a system must do






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






3. Reusable - abstract 'blocks' of design






4. A powerful motivator for change






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






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






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






8. Constraints on the design due to external factors






9. Absence of lifecycle






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






11. Derived methods should not assume more or deliver less






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






13. Lack of errors in code - readability etc






14. Reusable - abstract 'blocks' of design






15. 3rd step of requirements gathering






16. Each line of code is covered once






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






18. Each possible path through the code is covered






19. Single step in a lifecycle






20. A way to automatically grade code based on heuristics






21. Representational State Transfer.






22. 1st step of requirements gathering






23. A relationship between objects.






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






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






26. Evaluates upper limits of operational parameters






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






28. (smell) code is repeated in multiple places






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


30. Techniques for composing objects to form larger structures






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






32. A movement that promotes common formats for data.






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






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






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


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






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






38. The rights governing the ownership and disposition of technology






39. 2nd step of requirements gathering






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






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






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






43. Recognizable indicator that something may be wrong with code






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






45. 'single dot rule'






46. Iterative - incremental framework for project management.






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






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






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






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