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 process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






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


3. Each line of code is covered once






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






5. 2nd step of requirements gathering






6. Figuring out what the requirements are






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






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






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






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






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






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






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






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






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






16. (smell) code is repeated in multiple places






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






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






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






20. Tasks that a system must be able to perform






21. 4th step of requirements gathering






22. Techniques for composing objects to form larger structures






23. Series of phases through which software is developed






24. A powerful motivator for change






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


26. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.






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






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






29. Formal testing against end user specifications






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






31. Iterative - incremental framework for project management.






32. Protecting the embodiment of an idea






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






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






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






36. The rights governing the ownership and disposition of technology






37. Testing the whole system for functionality






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






39. Absence of lifecycle






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






41. Verifies that system is protected against improper penetration






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. Word - logo or symbol used to distinguish one organization's wares and services from another's






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






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






46. Each possible path through the code is covered






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






48. 'single dot rule'






49. 3rd step of requirements gathering






50. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.