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






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






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






4. (smell) code is repeated in multiple places






5. A movement that promotes common formats for data.






6. Absence of lifecycle






7. Iterative - incremental framework for project management.






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






9. Representational State Transfer.






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






11. Derived methods should not assume more or deliver less






12. 3rd step of requirements gathering






13. A relationship between objects.






14. Protecting the embodiment of an idea






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






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






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






18. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.






19. 4th step of requirements gathering






20. The degree to which code is free of defects






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






22. The things a system must do






23. People who care about the outcome






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






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






26. Recognizable indicator that something may be wrong with code






27. A method that initializes a newly instantiated object






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






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


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






31. Verifies that system is protected against improper penetration






32. 'single dot rule'






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






34. Comprehensive description of software's intended purpose






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






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






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






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






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






41. Reusable - abstract 'blocks' of design






42. A way to automatically grade code based on heuristics






43. Formal testing against end user specifications






44. Constraints on the design due to external factors






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






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






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






48. A powerful motivator for change






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






50. Testing the whole system for functionality