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. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






2. Each line of code is covered once






3. (smell) Smell deodorant






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






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






6. Constraints on the design due to external factors






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






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






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






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






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






12. A method that initializes a newly instantiated object






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






14. The degree to which code is free of defects






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






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






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






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






19. Techniques for composing objects to form larger structures






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






21. 3rd step of requirements gathering






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






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






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






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






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






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






28. Recognizable indicator that something may be wrong with code






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






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






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






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






33. Comprehensive description of software's intended purpose






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






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






36. A way to automatically grade code based on heuristics






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






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






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






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






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






42. Reusable - abstract 'blocks' of design






43. The rights governing the ownership and disposition of technology






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






45. (smell) code is repeated in multiple places






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






47. A few sentences summarizing a use case






48. Protecting the embodiment of an idea






49. The things a system must do






50. Testing the whole system for functionality