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. Formal document outlining a task that needs to be performed on a system






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






3. A relationship between objects.






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






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






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






7. Recognizable indicator that something may be wrong with code






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






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






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






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


12. A method that initializes a newly instantiated object






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






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






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






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






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






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






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






20. The things a system must do






21. A way to automatically grade code based on heuristics






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






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






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






25. Reusable - abstract 'blocks' of design






26. A powerful motivator for change






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






28. Comprehensive description of software's intended purpose






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






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






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






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






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






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






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






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






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






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






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






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






41. 3rd step of requirements gathering






42. Evaluates upper limits of operational parameters






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






44. Formal testing against end user specifications






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






46. People who care about the outcome






47. Tasks that a system must be able to perform






48. (smell) client needs to use one object to get another and then use that one to get another






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






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