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. (smell)class with too many instance variables or too much code






2. Evaluates upper limits of operational parameters






3. A powerful motivator for change






4. 4th step of requirements gathering






5. Absence of lifecycle






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






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






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






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






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






11. Derived methods should not assume more or deliver less






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






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






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






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






16. Verifies that system is protected against improper penetration






17. Reusable - abstract 'blocks' of design






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






19. Formal testing against end user specifications






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






21. Comprehensive description of software's intended purpose






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


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






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






25. 3rd step of requirements gathering






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






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






28. The rights governing the ownership and disposition of technology






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






30. A method that initializes a newly instantiated object






31. Protecting the embodiment of an idea






32. Test the run - time performance of the system






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






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






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






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






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






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






39. 2nd step of requirements gathering






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






41. People who care about the outcome






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






43. (smell) Smell deodorant






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






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






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






47. Testing the whole system for functionality






48. A movement that promotes common formats for data.






49. The things a system must do






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