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. Formal document outlining a task that needs to be performed on a system






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






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






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






6. Recognizable indicator that something may be wrong with code






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






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






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






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






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


12. Lack of errors in code - readability etc






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






14. 2nd step of requirements gathering






15. Verifies that system is protected against improper penetration






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






17. Reusable - abstract 'blocks' of design






18. Reusable - abstract 'blocks' of design






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






20. A powerful motivator for change






21. Iterative - incremental framework for project management.






22. The rights governing the ownership and disposition of technology






23. The things a system must do






24. Representational State Transfer.






25. Each possible path through the code is covered






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






27. Tasks that a system must be able to perform






28. How well your fulfil your requirements






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






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






31. Absence of lifecycle






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






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






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






35. Evaluates upper limits of operational parameters






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






37. Figuring out what the requirements are






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






39. Protecting the embodiment of an idea






40. Testing the whole system for functionality






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






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






43. A movement that promotes common formats for data.






44. Derived methods should not assume more or deliver less






45. 1st step of requirements gathering






46. (smell) code is repeated in multiple places






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






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






49. Techniques for composing objects to form larger structures






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






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