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. 'single dot rule'






2. Recognizable indicator that something may be wrong with code






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






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






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






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






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






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






9. The degree to which code is free of defects






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






11. Testing the whole system for functionality






12. Evaluates upper limits of operational parameters






13. People who care about the outcome






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


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






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






17. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu






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






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






20. Absence of lifecycle






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






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






23. Verifies that system is protected against improper penetration






24. A few sentences summarizing a use case






25. (smell) code is repeated in multiple places






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






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






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






29. Series of phases through which software is developed






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






31. 4th step of requirements gathering






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






33. A method that initializes a newly instantiated object






34. How well your fulfil your requirements






35. Formal testing against end user specifications






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






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






38. Comprehensive description of software's intended purpose






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






40. Reusable - abstract 'blocks' of design






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






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






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






44. Test the run - time performance of the system






45. Derived methods should not assume more or deliver less






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






47. Each possible path through the code is covered






48. Lack of errors in code - readability etc






49. 2nd step of requirements gathering






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