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. Testing tactic that looks at all ways that data can flow through the code






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






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






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






5. Iterative - incremental framework for project management.






6. Derived methods should not assume more or deliver less






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






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






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






10. Protecting the embodiment of an idea






11. A few sentences summarizing a use case






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






13. (smell) code is repeated in multiple places






14. How well your fulfil your requirements






15. Evaluates upper limits of operational parameters






16. Test the run - time performance of the system






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






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






19. 3rd step of requirements gathering






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






21. A method that initializes a newly instantiated object






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






23. Techniques for composing objects to form larger structures






24. Testing the whole system for functionality






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






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


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






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






29. Series of phases through which software is developed






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






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






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






33. Formal testing against end user specifications






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






35. 1st step of requirements gathering






36. The things a system must do






37. Each possible path through the code is covered






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






39. 2nd step of requirements gathering






40. Object oriented programming; using objects to solve problems.






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






42. Lack of errors in code - readability etc






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






44. 4th step of requirements gathering






45. Each line of code is covered once






46. Reusable - abstract 'blocks' of design






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






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






49. Single step in a lifecycle






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