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. The degree to which code is free of defects






2. The rights governing the ownership and disposition of technology






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






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






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






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






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






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






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






10. Lack of errors in code - readability etc






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






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






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






14. 4th step of requirements gathering






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






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






17. A way to automatically grade code based on heuristics






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






19. Techniques for composing objects to form larger structures






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






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






22. Single step in a lifecycle






23. (smell) code is repeated in multiple places






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






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






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






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






28. (smell) Smell deodorant






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






30. Test the run - time performance of the system






31. (smell) Making one change requires changes in multiple places






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






33. Reusable - abstract 'blocks' of design






34. 'single dot rule'






35. Formal testing against end user specifications






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






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






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






39. 2nd step of requirements gathering






40. Constraints on the design due to external factors






41. 1st step of requirements gathering






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






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






44. Iterative - incremental framework for project management.






45. Representational State Transfer.






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






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






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






49. The things a system must do






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