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. Models ->code work is done to keep models in sync with code






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






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






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






6. Description of possible sequences of interactions between a user and the system.






7. Figuring out what the requirements are






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






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






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






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






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






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






14. 3rd step of requirements gathering






15. A way to automatically grade code based on heuristics






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






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






18. Series of phases through which software is developed






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






20. (smell) Smell deodorant






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






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






23. The rights governing the ownership and disposition of technology






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






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. 4th step of requirements gathering






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






28. Constraints on the design due to external factors






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






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






31. Derived methods should not assume more or deliver less






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






33. Evaluates upper limits of operational parameters






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






35. Testing the whole system for functionality






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






37. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






38. Formal testing against end user specifications






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






40. Each line of code is covered once






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






42. A method that initializes a newly instantiated object






43. Protecting the embodiment of an idea






44. Absence of lifecycle






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






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






47. Test the run - time performance of the system






48. Recognizable indicator that something may be wrong with code






49. 2nd step of requirements gathering






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