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 design pattern that allows behaviour to be added to an existing object dynamically.






2. 2nd step of requirements gathering






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






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






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


6. Techniques for composing objects to form larger structures






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






8. A relationship between objects.






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






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






11. (smell) code is repeated in multiple places






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






13. Each possible path through the code is covered






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






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






16. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






17. Single step in a lifecycle






18. Derived methods should not assume more or deliver less






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






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






21. Representational State Transfer.






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






23. Reusable - abstract 'blocks' of design






24. A method that initializes a newly instantiated object






25. Iterative - incremental framework for project management.






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






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






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






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






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






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






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






33. Verifies that system is protected against improper penetration






34. Recognizable indicator that something may be wrong with code






35. Lack of errors in code - readability etc






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






37. (smell) Smell deodorant






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






39. Absence of lifecycle






40. How well your fulfil your requirements






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






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






43. Reusable - abstract 'blocks' of design






44. The things a system must do






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






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






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






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






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






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