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. Delaying the creation of an object - calculation of a value or another expensive process until first needed.






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






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






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






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






6. Testing the whole system for functionality






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






8. Lack of errors in code - readability etc






9. (smell) code is repeated in multiple places






10. Figuring out what the requirements are






11. 4th step of requirements gathering






12. Reusable - abstract 'blocks' of design






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






14. Protecting the embodiment of an idea






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






16. A movement that promotes common formats for data.






17. Recognizable indicator that something may be wrong with code






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






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


20. Series of phases through which software is developed






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






22. Comprehensive description of software's intended purpose






23. A few sentences summarizing a use case






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






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






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






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






28. How well your fulfil your requirements






29. Techniques for composing objects to form larger structures






30. 1st step of requirements gathering






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






32. Each line of code is covered once






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






34. Description of possible sequences of interactions between a user and the system.






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






36. 2nd step of requirements gathering






37. Iterative - incremental framework for project management.






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






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






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






41. Constraints on the design due to external factors






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






43. Derived methods should not assume more or deliver less






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






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






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






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






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






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






50. 'single dot rule'