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. Testing the whole system for functionality






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






3. Protecting the embodiment of an idea






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






5. 3rd step of requirements gathering






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






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






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






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






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






11. 'single dot rule'






12. Each line of code is covered once






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






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






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






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






17. Reusable - abstract 'blocks' of design






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






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






20. Derived methods should not assume more or deliver less






21. Figuring out what the requirements are






22. Representational State Transfer.






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






24. (smell) code is repeated in multiple places






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






26. Evaluates upper limits of operational parameters






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






28. Test the run - time performance of the system






29. A method that initializes a newly instantiated object






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






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






32. Tasks that a system must be able to perform






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






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






35. (smell) Smell deodorant






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






37. The things a system must do






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






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






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






41. Constraints on the design due to external factors






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






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






44. Absence of lifecycle






45. Reusable - abstract 'blocks' of design






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






47. Verifies that system is protected against improper penetration






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






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






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