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. Each possible path through the code is covered






3. 4th step of requirements gathering






4. (smell) Smell deodorant






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






6. Test cases made -> code compiles -> make code pass






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






8. Derived methods should not assume more or deliver less






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






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






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






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






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






14. Evaluates upper limits of operational parameters






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






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






17. Testing the whole system for functionality






18. The rights governing the ownership and disposition of technology






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






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






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






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. Single step in a lifecycle






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






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






26. Absence of lifecycle






27. 1st step of requirements gathering






28. Reusable - abstract 'blocks' of design






29. Test the run - time performance of the system






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






31. (smell) If a set of variables are used together in multiple places






32. People who care about the outcome






33. Iterative - incremental framework for project management.






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






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






36. 2nd step of requirements gathering






37. Series of phases through which software is developed






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






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






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






41. Constraints on the design due to external factors






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






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






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






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






46. 'single dot rule'






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






48. A powerful motivator for change






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






50. A relationship between objects.