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. A way to automatically grade code based on heuristics






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






3. Reusable - abstract 'blocks' of design






4. The degree to which code is free of defects






5. Reusable - abstract 'blocks' of design






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






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






8. Test the run - time performance of the system






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






10. Testing the whole system for functionality






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






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






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






14. A powerful motivator for change






15. Tasks that a system must be able to perform






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






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






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






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






20. Single step in a lifecycle






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






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






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






24. Comprehensive description of software's intended purpose






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






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


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






28. Protecting the embodiment of an idea






29. Evaluates upper limits of operational parameters






30. The rights governing the ownership and disposition of technology






31. 2nd step of requirements gathering






32. The things a system must do






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






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






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






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






37. A movement that promotes common formats for data.






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






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






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






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






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






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






44. Formal testing against end user specifications






45. Techniques for composing objects to form larger structures






46. 'single dot rule'






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






48. How well your fulfil your requirements






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






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