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 method that initializes a newly instantiated object






2. A relationship between objects.






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






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






5. Derived methods should not assume more or deliver less






6. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






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






8. The degree to which code is free of defects






9. Absence of lifecycle






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






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






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






13. Figuring out what the requirements are






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






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






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






17. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.






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


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






20. A way to automatically grade code based on heuristics






21. Reusable - abstract 'blocks' of design






22. One or two paragraphs of text outlining a use case






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






24. (smell) Smell deodorant






25. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.






26. Constraints on the design due to external factors






27. 2nd step of requirements gathering






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






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






30. Formal testing against end user specifications






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






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






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






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






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






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






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






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






39. Lack of errors in code - readability etc






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






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






42. 4th step of requirements gathering






43. Series of phases through which software is developed






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






45. Each line of code is covered once






46. Tasks that a system must be able to perform






47. 'single dot rule'






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






49. Reusable - abstract 'blocks' of design






50. Testing the whole system for functionality