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. The rights governing the ownership and disposition of technology






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






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






4. The degree to which code is free of defects






5. (smell) code is repeated in multiple places






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


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






8. A way to automatically grade code based on heuristics






9. Test the run - time performance of the system






10. A powerful motivator for change






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






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. How well your fulfil your requirements






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






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






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






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






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






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






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






21. (smell)class with too many instance variables or too much code






22. Constraints on the design due to external factors






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






24. 4th step of requirements gathering






25. Evaluates upper limits of operational parameters






26. Recognizable indicator that something may be wrong with code






27. Each line of code is covered once






28. 'single dot rule'






29. The things a system must do






30. 3rd step of requirements gathering






31. Figuring out what the requirements are






32. Iterative - incremental framework for project management.






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






34. A few sentences summarizing a use case






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






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






37. A method that initializes a newly instantiated object






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


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






40. Comprehensive description of software's intended purpose






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






42. (smell) Smell deodorant






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






44. A relationship between objects.






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






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






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






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






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






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