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. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






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






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






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






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






6. Techniques for composing objects to form larger structures






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






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






9. Iterative - incremental framework for project management.






10. Tasks that a system must be able to perform






11. Figuring out what the requirements are






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






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






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






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






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






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






18. (smell) code is repeated in multiple places






19. Comprehensive description of software's intended purpose






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






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






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






23. Testing the whole system for functionality






24. 'single dot rule'






25. Series of phases through which software is developed






26. A powerful motivator for change






27. Reusable - abstract 'blocks' of design






28. The degree to which code is free of defects






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






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






31. A few sentences summarizing a use case






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






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






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






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






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






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






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






39. Verifies that system is protected against improper penetration






40. Ways to express the system's subsystems and their relationship






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






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


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






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






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






46. How well your fulfil your requirements






47. A way to automatically grade code based on heuristics






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






49. Reusable - abstract 'blocks' of design






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