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. Testing that verifies that individual units of source code are working






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






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. Testing tactic based on whether inputs and outputs match up for required functionality






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






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






7. 4th step of requirements gathering






8. Protecting the embodiment of an idea






9. A powerful motivator for change






10. A method that initializes a newly instantiated object






11. (smell) Smell deodorant






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






13. Single step in a lifecycle






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


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






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






17. Verifies that system is protected against improper penetration






18. Recognizable indicator that something may be wrong with code






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






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






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






22. Iterative - incremental framework for project management.






23. The things a system must do






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






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






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


27. Reusable - abstract 'blocks' of design






28. Constraints on the design due to external factors






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






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






31. Evaluates upper limits of operational parameters






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






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






34. Absence of lifecycle






35. Comprehensive description of software's intended purpose






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






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






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






39. (smell) A method using another class more than its own






40. The degree to which code is free of defects






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






42. Testing the whole system for functionality






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






44. Figuring out what the requirements are






45. Representational State Transfer.






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






47. Each line of code is covered once






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






49. Series of phases through which software is developed






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