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. Single step in a lifecycle






2. Reusable - abstract 'blocks' of design






3. Test the run - time performance of the system






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






5. Formal testing against end user specifications






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






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






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






9. How well your fulfil your requirements






10. The things a system must do






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






12. Techniques for composing objects to form larger structures






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






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






15. The degree to which code is free of defects






16. 4th step of requirements gathering






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






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






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






20. Approach to team management that splits management up into two people with separate tasks






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






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






23. (smell) Smell deodorant






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






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






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






27. Absence of lifecycle






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






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






30. 2nd step of requirements gathering






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






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






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






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






35. 'single dot rule'






36. Figuring out what the requirements are






37. Testing the whole system for functionality






38. Reusable - abstract 'blocks' of design






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






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






41. People who care about the outcome






42. A way to automatically grade code based on heuristics






43. Evaluates upper limits of operational parameters






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






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






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






47. 1st step of requirements gathering






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






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






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