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. Lack of errors in code - readability etc






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






3. Reusable - abstract 'blocks' of design






4. A movement that promotes common formats for data.






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






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






7. (smell) Smell deodorant






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






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






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






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






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






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






14. A relationship between objects.






15. The degree to which code is free of defects






16. People who care about the outcome






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






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






19. Protecting the embodiment of an idea






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






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






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






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






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






25. Verifies that system is protected against improper penetration






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






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






28. Series of phases through which software is developed






29. Test the run - time performance of the system






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






31. Degree to which the system meets the specified requirements and development standards






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






33. Iterative - incremental framework for project management.






34. Constraints on the design due to external factors






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






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






37. Tasks that a system must be able to perform






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






39. Formal testing against end user specifications






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






41. (smell) code is repeated in multiple places






42. A powerful motivator for change






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






44. 'single dot rule'






45. Reusable - abstract 'blocks' of design






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






47. Techniques for composing objects to form larger structures






48. Each possible path through the code is covered






49. Recognizable indicator that something may be wrong with code






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