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






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






3. Reusable - abstract 'blocks' of design






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






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






6. Reusable - abstract 'blocks' of design






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






8. How well your fulfil your requirements






9. People who care about the outcome






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






11. Protecting the embodiment of an idea






12. Iterative - incremental framework for project management.






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






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






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






16. 3rd step of requirements gathering






17. A movement that promotes common formats for data.






18. 'single dot rule'






19. (smell) Smell deodorant






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






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






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






23. The rights governing the ownership and disposition of technology






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






25. Testing can show the presence but not absence of errors


26. Comprehensive description of software's intended purpose






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






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






29. Techniques for composing objects to form larger structures






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






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






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






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






34. Constraints on the design due to external factors






35. Tasks that a system must be able to perform






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






37. 1st step of requirements gathering






38. A relationship between objects.






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






40. Recognizable indicator that something may be wrong with code






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






42. (smell) code is repeated in multiple places






43. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






44. 4th step of requirements gathering






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






46. 2nd step of requirements gathering






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






48. The things a system must do






49. A way to automatically grade code based on heuristics






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