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. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






2. Each line of code is covered once






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






4. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






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






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






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


8. Figuring out what the requirements are






9. (smell) Smell deodorant






10. The degree to which code is free of defects






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






12. Testing the whole system for functionality






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






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






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






16. 'single dot rule'






17. A movement that promotes common formats for data.






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






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






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






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






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






23. The rights governing the ownership and disposition of technology






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






25. Evaluates upper limits of operational parameters






26. How well your fulfil your requirements






27. People who care about the outcome






28. Test the run - time performance of the system






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






30. 4th step of requirements gathering






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






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






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






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






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






36. Comprehensive description of software's intended purpose






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






38. Tasks that a system must be able to perform






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






40. Reusable - abstract 'blocks' of design






41. Lack of errors in code - readability etc






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






43. (smell) code is repeated in multiple places






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






45. Single step in a lifecycle






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






47. 3rd step of requirements gathering






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






49. 1st step of requirements gathering






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