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. Force software to fail in order to see how it recovers






2. Each possible path through the code is covered






3. (smell) Smell deodorant






4. How well your fulfil your requirements






5. People who care about the outcome






6. 2nd step of requirements gathering






7. Representational State Transfer.






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






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






10. (smell) code is repeated in multiple places






11. Comprehensive description of software's intended purpose






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


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






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






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






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






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






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






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






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






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






22. 1st step of requirements gathering






23. A way to automatically grade code based on heuristics






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






25. Tasks that a system must be able to perform






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






27. 'single dot rule'






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






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






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






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






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






33. Iterative - incremental framework for project management.






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






35. The rights governing the ownership and disposition of technology






36. Recognizable indicator that something may be wrong with code






37. Figuring out what the requirements are






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






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






40. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






41. Absence of lifecycle






42. Reusable - abstract 'blocks' of design






43. Derived methods should not assume more or deliver less






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






45. A powerful motivator for change






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






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






48. Evaluates upper limits of operational parameters






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






50. Single step in a lifecycle