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. (smell) A method using another class more than its own






2. A movement that promotes common formats for data.






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






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






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






6. Representational State Transfer.






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






8. Verifies that system is protected against improper penetration






9. (smell) Smell deodorant






10. How well your fulfil your requirements






11. Testing the whole system for functionality






12. Figuring out what the requirements are






13. Constraints on the design due to external factors






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






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






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






17. Lack of errors in code - readability etc






18. 3rd step of requirements gathering






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






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






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






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






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






24. A relationship between objects.






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






26. Comprehensive description of software's intended purpose






27. Reusable - abstract 'blocks' of design






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






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






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






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






32. The degree to which code is free of defects






33. Recognizable indicator that something may be wrong with code






34. Iterative - incremental framework for project management.






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






36. 2nd step of requirements gathering






37. The rights governing the ownership and disposition of technology






38. Absence of lifecycle






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






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






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






42. Series of phases through which software is developed






43. A way to automatically grade code based on heuristics






44. Protecting the embodiment of an idea






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






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






47. Test the run - time performance of the system






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






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






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