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. Single step in a lifecycle






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






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






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






5. Reusable - abstract 'blocks' of design






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






7. A method that initializes a newly instantiated object






8. 'single dot rule'






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






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






11. A way to automatically grade code based on heuristics






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






13. Evaluates upper limits of operational parameters






14. 2nd step of requirements gathering






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






16. 4th step of requirements gathering






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






18. A powerful motivator for change






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






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






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






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






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






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


25. (smell) Smell deodorant






26. Figuring out what the requirements are






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






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






29. A movement that promotes common formats for data.






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






31. A few sentences summarizing a use case






32. The degree to which code is free of defects






33. A set of rules that define the combinations of symbols that are considered to be correctly structured in a specific programming language. Example: In many programming languages - statements are terminated by a semicolon.






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






35. Comprehensive description of software's intended purpose






36. Iterative - incremental framework for project management.






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






38. Techniques for composing objects to form larger structures






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






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






41. Derived methods should not assume more or deliver less






42. Constraints on the design due to external factors






43. 1st step of requirements gathering






44. Each line of code is covered once






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






46. Protecting the embodiment of an idea






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






48. The things a system must do






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






50. Absence of lifecycle