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. 2nd step of requirements gathering






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






3. Each possible path through the code is covered






4. A way to automatically grade code based on heuristics






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






6. People who care about the outcome






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






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






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






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






11. Figuring out what the requirements are






12. Executes system in a manner that demands abnormal amounts of resources






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






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






15. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






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






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






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






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






20. A powerful motivator for change






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


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






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






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






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






26. Constraints on the design due to external factors






27. 3rd step of requirements gathering






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






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






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






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






32. Single step in a lifecycle






33. (smell) code is repeated in multiple places






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






35. Test the run - time performance of the system






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






37. Verifies that system is protected against improper penetration






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






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






40. Tasks that a system must be able to perform






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






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






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






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






45. A movement that promotes common formats for data.






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






47. (smell) Smell deodorant






48. Reusable - abstract 'blocks' of design






49. Testing the whole system for functionality






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