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. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data






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






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






4. A powerful motivator for change






5. People who care about the outcome






6. Reusable - abstract 'blocks' of design






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






8. Figuring out what the requirements are






9. The things a system must do






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. The degree to which code is free of defects






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






13. 1st step of requirements gathering






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






15. Single step in a lifecycle






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






17. A way to automatically grade code based on heuristics






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






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






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






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


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






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






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






25. Testing the whole system for functionality






26. Iterative - incremental framework for project management.






27. Verifies that system is protected against improper penetration






28. 3rd step of requirements gathering






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






30. Formal testing against end user specifications






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






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






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






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






35. Series of phases through which software is developed






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






37. Recognizable indicator that something may be wrong with code






38. 4th step of requirements gathering






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






40. (smell) code is repeated in multiple places






41. Constraints on the design due to external factors






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






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






44. Comprehensive description of software's intended purpose






45. (smell) client needs to use one object to get another and then use that one to get another






46. Testing tactic based on whether inputs and outputs match up for required functionality






47. How well your fulfil your requirements






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






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






50. Evaluates upper limits of operational parameters