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






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






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






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






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






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


7. (smell) Smell deodorant






8. The rights governing the ownership and disposition of technology






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






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






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






12. 3rd step of requirements gathering






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






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






15. A relationship between objects.






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






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






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






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






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






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






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






23. Representational State Transfer.






24. Iterative - incremental framework for project management.






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






26. Verifies that system is protected against improper penetration






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






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






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






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






31. Evaluates upper limits of operational parameters






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






33. A way to automatically grade code based on heuristics






34. Recognizable indicator that something may be wrong with code






35. Protecting the embodiment of an idea






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






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






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






39. Constraints on the design due to external factors






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






41. (smell) If a set of variables are used together in multiple places






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






43. Each line of code is covered once






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






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






46. A design pattern that allows behaviour to be added to an existing object dynamically.






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






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






49. Derived methods should not assume more or deliver less






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests