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. Comprehensive description of software's intended purpose






2. How well your fulfil your requirements






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






4. (smell) code is repeated in multiple places






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






6. A few sentences summarizing a use case






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






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






9. Representational State Transfer.






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






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






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






13. Series of phases through which software is developed






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






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






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






17. Protecting the embodiment of an idea






18. Constraints on the design due to external factors






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






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






21. Figuring out what the requirements are






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






23. Test the run - time performance of the system






24. Each line of code is covered once






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






26. Verifies that system is protected against improper penetration






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






28. 3rd step of requirements gathering






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






30. A method that initializes a newly instantiated object






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






32. Lack of errors in code - readability etc






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






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






35. 2nd step of requirements gathering






36. Evaluates upper limits of operational parameters






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






38. Single step in a lifecycle






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






40. 4th step of requirements gathering






41. Absence of lifecycle






42. Testing the whole system for functionality






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






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






45. 'single dot rule'






46. Testing where modules are combined and tested as a group






47. A powerful motivator for change






48. A way to automatically grade code based on heuristics






49. Derived methods should not assume more or deliver less






50. Techniques for composing objects to form larger structures