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. Approach to team management that splits management up into two people with separate tasks






2. (smell) Smell deodorant






3. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






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






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






6. A computer program that divides code up into functional components






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






8. Test the run - time performance of the system






9. Evaluates upper limits of operational parameters






10. Each line of code is covered once






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






12. (smell) code is repeated in multiple places






13. Verifies that system is protected against improper penetration






14. Comprehensive description of software's intended purpose






15. Formal testing against end user specifications






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






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






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






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






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






21. Figuring out what the requirements are






22. People who care about the outcome






23. 'single dot rule'






24. The rights governing the ownership and disposition of technology






25. Tasks that a system must be able to perform






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






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






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






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






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






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






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






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






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






35. Lack of errors in code - readability etc






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






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


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






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






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






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






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






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






44. A movement that promotes common formats for data.






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






46. 1st step of requirements gathering






47. A method that initializes a newly instantiated object






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






49. Representational State Transfer.






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