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. (smell) code is repeated in multiple places






2. Reusable - abstract 'blocks' of design






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






4. Each possible path through the code is covered






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






6. Figuring out what the requirements are






7. Recognizable indicator that something may be wrong with code






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






9. Formal testing against end user specifications






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






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






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






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






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






15. Series of phases through which software is developed






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


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






18. The degree to which code is free of defects






19. The things a system must do






20. 3rd step of requirements gathering






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






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






23. 1st step of requirements gathering






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






25. 'single dot rule'






26. 4th step of requirements gathering






27. Representational State Transfer.






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






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






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






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






32. How well your fulfil your requirements






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






34. A relationship between objects.






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






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






37. Test the run - time performance of the system






38. Constraints on the design due to external factors






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






40. Single step in a lifecycle






41. Word - logo or symbol used to distinguish one organization's wares and services from another's






42. Absence of lifecycle






43. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.






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






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






46. Derived methods should not assume more or deliver less






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






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






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






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