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. Contract between inventor - assignee and state giving a time and geographically limited monopoly






2. 3rd step of requirements gathering






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






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






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






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






7. Iterative - incremental framework for project management.






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






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






10. A relationship between objects.






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






12. Verifies that system is protected against improper penetration






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






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






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






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






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






18. Derived methods should not assume more or deliver less






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






20. Each possible path through the code is covered






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






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






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






24. Reusable - abstract 'blocks' of design






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






26. The things a system must do






27. Recognizable indicator that something may be wrong with code






28. Formal testing against end user specifications






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






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






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






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






33. The degree to which code is free of defects






34. 2nd step of requirements gathering






35. (smell) Smell deodorant






36. Testing the whole system for functionality






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






38. Each line of code is covered once






39. Constraints on the design due to external factors






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






41. Techniques for composing objects to form larger structures






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






43. Absence of lifecycle






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






45. A way to automatically grade code based on heuristics






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






47. How well your fulfil your requirements






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






49. Figuring out what the requirements are






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests