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. 4th step of requirements gathering






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






3. Absence of lifecycle






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






5. Testing the whole system for functionality






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






7. Reusable - abstract 'blocks' of design






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






9. Each possible path through the code is covered






10. Protecting the embodiment of an idea






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






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






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






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






15. Figuring out what the requirements are






16. A relationship between objects.






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






18. Developing a plan for a product - system or component. 'how' a system should perform a task






19. Iterative - incremental framework for project management.






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






21. Recognizable indicator that something may be wrong with code






22. Formal testing against end user specifications






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






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






25. A way to automatically grade code based on heuristics






26. (smell) code is repeated in multiple places






27. Comprehensive description of software's intended purpose






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






29. A few sentences summarizing a use case






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






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






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






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






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






35. A movement that promotes common formats for data.






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






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






38. A method that initializes a newly instantiated object






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






40. Reusable - abstract 'blocks' of design






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






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






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






44. Single step in a lifecycle






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






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






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






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






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






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