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 design pattern that allows behaviour to be added to an existing object dynamically.






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






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






4. Testing the whole system for functionality






5. Verifies that system is protected against improper penetration






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






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






8. Reusable - abstract 'blocks' of design






9. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






10. The rights governing the ownership and disposition of technology






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






12. Absence of lifecycle






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






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






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






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






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






18. 'single dot rule'






19. Formal testing against end user specifications






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






21. (smell) code is repeated in multiple places






22. Reusable - abstract 'blocks' of design






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






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






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






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






27. The things a system must do






28. 2nd step of requirements gathering






29. Derived methods should not assume more or deliver less






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






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






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






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






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






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






36. Protecting the embodiment of an idea






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






38. Series of phases through which software is developed






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






40. Test the run - time performance of the system






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






42. Iterative - incremental framework for project management.






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






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


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






46. Single step in a lifecycle






47. 3rd step of requirements gathering






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






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






50. 4th step of requirements gathering