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. Each condition is covered twice (true - false)






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






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






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






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






7. Each possible path through the code is covered






8. 1st step of requirements gathering






9. Reusable - abstract 'blocks' of design






10. A relationship between objects.






11. Protecting the embodiment of an idea






12. A way to automatically grade code based on heuristics






13. Figuring out what the requirements are






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






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






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






17. Series of phases through which software is developed






18. (smell) many parameters are being passed into a method






19. Derived methods should not assume more or deliver less






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






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






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






23. A powerful motivator for change






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






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






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






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






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






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






30. (smell) client needs to use one object to get another and then use that one to get another






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






32. An operator used to denote anonymous functions or closures.






33. A computer program that divides code up into functional components






34. (smell) Smell deodorant






35. A movement that promotes common formats for data.






36. Verifies that system is protected against improper penetration






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


38. Lack of errors in code - readability etc






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






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






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






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






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






44. Testing the whole system for functionality






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






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






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






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


49. (smell) code is repeated in multiple places






50. A method that initializes a newly instantiated object