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. Freezing the state of the source code at a particular point






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






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






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






5. Derived methods should not assume more or deliver less






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






7. Lack of errors in code - readability etc






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






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






10. The degree to which code is free of defects






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






12. Formal testing against end user specifications






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






14. Testing the whole system for functionality






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






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






17. Evaluates upper limits of operational parameters






18. Representational State Transfer.






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






20. The rights governing the ownership and disposition of technology






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






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






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






24. 'single dot rule'






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






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






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






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






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






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


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






32. Reusable - abstract 'blocks' of design






33. Recognizable indicator that something may be wrong with code






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






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






36. Absence of lifecycle






37. A way to automatically grade code based on heuristics






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






39. Test the run - time performance of the system






40. Tasks that a system must be able to perform






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






42. 4th step of requirements gathering






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






44. 1st step of requirements gathering






45. A powerful motivator for change






46. Each possible path through the code is covered






47. 3rd step of requirements gathering






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






49. (smell) code is repeated in multiple places






50. A movement that promotes common formats for data.







Sorry!:) No result found.

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