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. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






2. A relationship between objects.






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






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






5. 'single dot rule'






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






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






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






9. Tasks that a system must be able to perform






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






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






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






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






14. A way to automatically grade code based on heuristics






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






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






17. Formal document outlining a task that needs to be performed on a system






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






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






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






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






22. Comprehensive description of software's intended purpose






23. A few sentences summarizing a use case






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






25. Techniques for composing objects to form larger structures






26. Series of phases through which software is developed






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






28. The degree to which code is free of defects






29. Constraints on the design due to external factors






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






31. 1st step of requirements gathering






32. Figuring out what the requirements are






33. The rights governing the ownership and disposition of technology






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






35. The things a system must do






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






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






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






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






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






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






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


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






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






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






46. Single step in a lifecycle






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






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






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






50. Each line of code is covered once