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) A method using another class more than its own






2. Formal testing against end user specifications






3. Absence of lifecycle






4. Each possible path through the code is covered






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






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






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






8. 2nd step of requirements gathering






9. Reusable - abstract 'blocks' of design






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






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






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






13. 1st step of requirements gathering






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






15. Figuring out what the requirements are






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






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






18. A way to automatically grade code based on heuristics






19. Tasks that a system must be able to perform






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






21. 'single dot rule'






22. The degree to which code is free of defects






23. Protecting the embodiment of an idea






24. The things a system must do






25. Recognizable indicator that something may be wrong with code






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. Testing tactic based on whether inputs and outputs match up for required functionality






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






29. Testing can show the presence but not absence of errors


30. Test the run - time performance of the system






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






32. A relationship between objects.






33. A movement that promotes common formats for data.






34. Constraints on the design due to external factors






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






36. Object oriented programming; using objects to solve problems.






37. Lack of errors in code - readability etc






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






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






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






41. Testing can show the presence but not absence of errors


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






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






44. (smell) Smell deodorant






45. Testing the whole system for functionality






46. Techniques for composing objects to form larger structures






47. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






48. Representational State Transfer.






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






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