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. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






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






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






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






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






6. Constraints on the design due to external factors






7. Recognizable indicator that something may be wrong with code






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






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






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






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






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






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






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






15. Derived methods should not assume more or deliver less






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






17. (smell) Classes using things that should be private in other classes






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






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






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






21. 1st step of requirements gathering






22. A way to automatically grade code based on heuristics






23. Iterative - incremental framework for project management.






24. Series of phases through which software is developed






25. A relationship between objects.






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






27. People who care about the outcome






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






29. 'single dot rule'






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






31. Techniques for composing objects to form larger structures






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






33. A movement that promotes common formats for data.






34. 3rd step of requirements gathering






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






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






37. A computer program that divides code up into functional components






38. The rights governing the ownership and disposition of technology






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






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






41. A few sentences summarizing a use case






42. Each possible path through the code is covered






43. Figuring out what the requirements are






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






45. Object oriented programming; using objects to solve problems.






46. (smell) Smell deodorant






47. Lack of errors in code - readability etc






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






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






50. Reusable - abstract 'blocks' of design