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






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






3. A relationship between objects.






4. Verifies that system is protected against improper penetration






5. Testing the whole system for functionality






6. 3rd step of requirements gathering






7. The things a system must do






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






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






10. Evaluates upper limits of operational parameters






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






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






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






14. The degree to which code is free of defects






15. Techniques for composing objects to form larger structures






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


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






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






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






20. Lack of errors in code - readability etc






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






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






23. Reusable - abstract 'blocks' of design






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






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






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






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






28. Recognizable indicator that something may be wrong with code






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






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






31. Tasks that a system must be able to perform






32. Constraints on the design due to external factors






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


34. Each line of code is covered once






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






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






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






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






39. A powerful motivator for change






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






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






42. 1st step of requirements gathering






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






44. Comprehensive description of software's intended purpose






45. Iterative - incremental framework for project management.






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






47. Single step in a lifecycle






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






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






50. Formal testing against end user specifications