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. Testing tactic based on whether inputs and outputs match up for required functionality






2. 2nd step of requirements gathering






3. Derived methods should not assume more or deliver less






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






5. Recognizable indicator that something may be wrong with code






6. A relationship between objects.






7. Test the run - time performance of the system






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






9. Protecting the embodiment of an idea






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






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






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






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






14. A few sentences summarizing a use case






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






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






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






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






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






20. Single step in a lifecycle






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






22. Iterative - incremental framework for project management.






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






24. The degree to which code is free of defects






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






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






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






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






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






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






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






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






33. A powerful motivator for change






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






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






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






37. 3rd step of requirements gathering






38. The things a system must do






39. 'single dot rule'






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






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






42. Representational State Transfer.






43. Each line of code is covered once






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






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






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






47. Testing the whole system for functionality






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






49. A movement that promotes common formats for data.






50. Techniques for composing objects to form larger structures