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. An effective method expressed as a finite list of well- defined instructions for solving a problem.






2. (smell) Making one change requires changes in multiple places






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


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






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






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






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






8. 4th step of requirements gathering






9. 2nd step of requirements gathering






10. Lack of errors in code - readability etc






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






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






13. Verifies that system is protected against improper penetration






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






15. Tasks that a system must be able to perform






16. Derived methods should not assume more or deliver less






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






18. People who care about the outcome






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






20. A way to automatically grade code based on heuristics






21. Developing a plan for a product - system or component. 'how' a system should perform a task






22. 3rd step of requirements gathering






23. The degree to which code is free of defects






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






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






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






27. (smell) Smell deodorant






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






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






30. Each line of code is covered once






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






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






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






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






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






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






37. A relationship between objects.






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






39. The things a system must do






40. A method that initializes a newly instantiated object






41. 1st step of requirements gathering






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






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






44. Recognizable indicator that something may be wrong with code






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






46. Series of phases through which software is developed






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






48. The rights governing the ownership and disposition of technology






49. A movement that promotes common formats for data.






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