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. Degree to which the system meets the specified requirements and development standards






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






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






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






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






6. Recognizable indicator that something may be wrong with code






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






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






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






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






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






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






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


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






15. 'single dot rule'






16. How well your fulfil your requirements






17. Test the run - time performance of the system






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






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






20. The things a system must do






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






22. Formal testing against end user specifications






23. Absence of lifecycle






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






25. The degree to which code is free of defects






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






27. 4th step of requirements gathering






28. Lack of errors in code - readability etc






29. Tasks that a system must be able to perform






30. Protecting the embodiment of an idea






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






32. Comprehensive description of software's intended purpose






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






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






35. A relationship between objects.






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






37. Iterative - incremental framework for project management.






38. (smell) code is repeated in multiple places






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






40. Figuring out what the requirements are






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






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






43. People who care about the outcome






44. A few sentences summarizing a use case






45. Techniques for composing objects to form larger structures






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






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






48. Verifies that system is protected against improper penetration






49. Series of phases through which software is developed






50. Single step in a lifecycle