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. Tasks that a system must be able to perform






2. Lack of errors in code - readability etc






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






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






5. Protecting the embodiment of an idea






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






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






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






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






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






11. Test the run - time performance of the system






12. The things a system must do






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






14. People who care about the outcome






15. 2nd step of requirements gathering






16. Figuring out what the requirements are






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






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






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






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






21. Absence of lifecycle






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






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






24. Representational State Transfer.






25. (smell) Smell deodorant






26. A few sentences summarizing a use case






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






28. Techniques for composing objects to form larger structures






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






30. A relationship between objects.






31. Iterative - incremental framework for project management.






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






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






34. A method that initializes a newly instantiated object






35. Each possible path through the code is covered






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






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






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






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


40. Constraints on the design due to external factors






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






42. Single step in a lifecycle






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






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






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






46. 3rd step of requirements gathering






47. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






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






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






50. 1st step of requirements gathering