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. (smell) method has too many statements - loops or variables






3. A powerful motivator for change






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






5. Figuring out what the requirements are






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






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






8. A movement that promotes common formats for data.






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






10. The degree to which code is free of defects






11. 'single dot rule'






12. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data






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






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. (smell) many parameters are being passed into a method






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






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






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






19. Representational State Transfer.






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






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






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






23. Series of phases through which software is developed






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






25. Testing the whole system for functionality






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






27. 1st step of requirements gathering






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






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






30. Reusable - abstract 'blocks' of design






31. A few sentences summarizing a use case






32. Test cases made -> code compiles -> make code pass






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






34. Formal testing against end user specifications






35. Derived methods should not assume more or deliver less






36. 3rd step of requirements gathering






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






38. Techniques for composing objects to form larger structures






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






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






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






42. A method that initializes a newly instantiated object






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






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






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






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






47. A relationship between objects.






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






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






50. Tasks that a system must be able to perform