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. 1st step of requirements gathering






2. Each possible path through the code is covered






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






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






5. (smell) method has too many statements - loops or variables






6. 2nd step of requirements gathering






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






8. Reusable - abstract 'blocks' of design






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






10. 3rd step of requirements gathering






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






12. The rights governing the ownership and disposition of technology






13. Lack of errors in code - readability etc






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






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






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






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






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






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






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






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






22. (smell) code is repeated in multiple places






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






24. Comprehensive description of software's intended purpose






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






26. People who care about the outcome






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






28. Reusable - abstract 'blocks' of design






29. Techniques for composing objects to form larger structures






30. A relationship between objects.






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






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






33. Testing can show the presence but not absence of errors

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


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. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.






36. Each line of code is covered once






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






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. 4th step of requirements gathering






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






41. Series of phases through which software is developed






42. Tasks that a system must be able to perform






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






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






45. Single step in a lifecycle






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






47. A way to automatically grade code based on heuristics






48. Test the run - time performance of the system






49. The degree to which code is free of defects






50. Testing the whole system for functionality