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. Testing the whole system for functionality






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






3. Reusable - abstract 'blocks' of design






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






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






6. An effective method expressed as a finite list of well- defined instructions for solving a problem.






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






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






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






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






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






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






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






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






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






16. A method that initializes a newly instantiated object






17. Single step in a lifecycle






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






19. A set of rules that define the combinations of symbols that are considered to be correctly structured in a specific programming language. Example: In many programming languages - statements are terminated by a semicolon.






20. Comprehensive description of software's intended purpose






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






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






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






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






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






26. Each line of code is covered once






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






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






29. Figuring out what the requirements are






30. The rights governing the ownership and disposition of technology






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






32. Series of phases through which software is developed






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






34. 'single dot rule'






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






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






37. (smell) Smell deodorant






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






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






40. Tasks that a system must be able to perform






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






42. Reusable - abstract 'blocks' of design






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






44. A relationship between objects.






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






46. Each possible path through the code is covered






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






48. Recognizable indicator that something may be wrong with code






49. Derived methods should not assume more or deliver less






50. Constraints on the design due to external factors