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. Recognizable indicator that something may be wrong with code






2. 1st step of requirements gathering






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






4. Each line of code is covered once






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






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






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






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






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






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






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






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






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






14. Single step in a lifecycle






15. Series of phases through which software is developed






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






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






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






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






20. Evaluates upper limits of operational parameters






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






22. Each possible path through the code is covered






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






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






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


26. A few sentences summarizing a use case






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






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






29. Techniques for composing objects to form larger structures






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






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






32. People who care about the outcome






33. Absence of lifecycle






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






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






36. (smell) Smell deodorant






37. How well your fulfil your requirements






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






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






40. Reusable - abstract 'blocks' of design






41. The rights governing the ownership and disposition of technology






42. Testing tactic that looks at all ways that data can flow through the code






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






44. 4th step of requirements gathering






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






46. Representational State Transfer.






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


48. A relationship between objects.






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






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