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 that verifies that individual units of source code are working






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






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






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






5. The things a system must do






6. A way to automatically grade code based on heuristics






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






8. Reusable - abstract 'blocks' of design






9. 'single dot rule'






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






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






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






13. Constraints on the design due to external factors






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






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






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






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






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






19. 3rd step of requirements gathering






20. People who care about the outcome






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






22. (smell) code is repeated in multiple places






23. Techniques for composing objects to form larger structures






24. A powerful motivator for change






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






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






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






28. The degree to which code is free of defects






29. Verifies that system is protected against improper penetration






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






31. How well your fulfil your requirements






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






33. A relationship between objects.






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






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






36. Reusable - abstract 'blocks' of design






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






38. Iterative - incremental framework for project management.






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






40. A few sentences summarizing a use case






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






42. Series of phases through which software is developed






43. Recognizable indicator that something may be wrong with code






44. Formal testing against end user specifications






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






46. Each possible path through the code is covered






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






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






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






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