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. Comprehensive description of software's intended purpose






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






3. The rights governing the ownership and disposition of technology






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






5. Verifies that system is protected against improper penetration






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






7. Each possible path through the code is covered






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






9. A method that initializes a newly instantiated object






10. Representational State Transfer.






11. (smell) Smell deodorant






12. Recognizable indicator that something may be wrong with code






13. Constraints on the design due to external factors






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






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






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






17. A movement that promotes common formats for data.






18. A way to automatically grade code based on heuristics






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






20. Derived methods should not assume more or deliver less






21. Reusable - abstract 'blocks' of design






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






23. Tasks that a system must be able to perform






24. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






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






26. Reusable - abstract 'blocks' of design






27. A relationship between objects.






28. Lack of errors in code - readability etc






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






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






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






32. People who care about the outcome






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






34. Protecting the embodiment of an idea






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






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






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. (smell) client needs to use one object to get another and then use that one to get another






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






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






41. The things a system must do






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






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






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






45. Iterative - incremental framework for project management.






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






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






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






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






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