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)class with too many instance variables or too much code






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






3. Constraints on the design due to external factors






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






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






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






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






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






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






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






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






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






13. 'single dot rule'






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






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






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






17. Reusable - abstract 'blocks' of design






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






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






20. A few sentences summarizing a use case






21. Absence of lifecycle






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






23. A movement that promotes common formats for data.






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






25. Verifies that system is protected against improper penetration






26. Protecting the embodiment of an idea






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






28. Recognizable indicator that something may be wrong with code






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






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






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






32. People who care about the outcome






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






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






35. AKA: Object - Entity - or Value - An entity that can be constructed at run - time - passed as a parameter - returned from a subroutine - or assigned into a variable.






36. 4th step of requirements gathering






37. The rights governing the ownership and disposition of technology






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






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






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






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






42. Each line of code is covered once






43. Series of phases through which software is developed






44. Lack of errors in code - readability etc






45. Reusable - abstract 'blocks' of design






46. Techniques for composing objects to form larger structures






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






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






49. 3rd step of requirements gathering






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