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 rigorousness of the tests that are able to be placed on the code






2. Absence of lifecycle






3. Each possible path through the code is covered






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






5. Testing that verifies that individual units of source code are working






6. Protecting the embodiment of an idea






7. A way to automatically grade code based on heuristics






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






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






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






11. Single step in a lifecycle






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






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






14. Comprehensive description of software's intended purpose






15. People who care about the outcome






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






17. Tasks that a system must be able to perform






18. Lack of errors in code - readability etc






19. 'single dot rule'






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






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






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






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






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






25. The degree to which code is free of defects






26. The rights governing the ownership and disposition of technology






27. A few sentences summarizing a use case






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






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






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






31. Testing the whole system for functionality






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






33. Constraints on the design due to external factors






34. Executes system in a manner that demands abnormal amounts of resources






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






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






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






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






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






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






41. Techniques for composing objects to form larger structures






42. A powerful motivator for change






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






44. A design pattern that allows behaviour to be added to an existing object dynamically.






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






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






47. Test the run - time performance of the system






48. Reusable - abstract 'blocks' of design






49. Series of phases through which software is developed






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