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. A few sentences summarizing a use case






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






3. (smell) Smell deodorant






4. 4th step of requirements gathering






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






6. A way to automatically grade code based on heuristics






7. 3rd step of requirements gathering






8. Tasks that a system must be able to perform






9. 2nd step of requirements gathering






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


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






12. 1st step of requirements gathering






13. Single step in a lifecycle






14. Test the run - time performance of the system






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






16. Reusable - abstract 'blocks' of design






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






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






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






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






21. How well your fulfil your requirements






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






23. Figuring out what the requirements are






24. Comprehensive description of software's intended purpose






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






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






27. Lack of errors in code - readability etc






28. A relationship between objects.






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






30. Derived methods should not assume more or deliver less






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






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






33. A movement that promotes common formats for data.






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






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






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






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






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






39. Developing a plan for a product - system or component. 'how' a system should perform a task






40. Iterative - incremental framework for project management.






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






42. Reusable - abstract 'blocks' of design






43. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






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






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






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






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






48. Evaluates upper limits of operational parameters






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






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