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. Series of phases through which software is developed






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






3. People who care about the outcome






4. Each possible path through the code is covered






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






6. The degree to which code is free of defects






7. A method that initializes a newly instantiated object






8. Test the run - time performance of the system






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






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






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






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






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






14. Single step in a lifecycle






15. Lack of errors in code - readability etc






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






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






18. A computer program that divides code up into functional components






19. A relationship between objects.






20. Iterative - incremental framework for project management.






21. Protecting the embodiment of an idea






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






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






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






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






26. 4th step of requirements gathering






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






28. 'single dot rule'






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






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






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

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


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






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






34. (smell) Smell deodorant






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






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






37. Formal testing against end user specifications






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






39. Representational State Transfer.






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






41. The rights governing the ownership and disposition of technology






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






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






44. Derived methods should not assume more or deliver less






45. 2nd step of requirements gathering






46. Reusable - abstract 'blocks' of design






47. (smell) code is repeated in multiple places






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






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






50. Figuring out what the requirements are