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. Test the run - time performance of the system






2. Derived methods should not assume more or deliver less






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






4. Protecting the embodiment of an idea






5. (smell) Smell deodorant






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






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






8. (smell) code is repeated in multiple places






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






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






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






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






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






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






15. Recognizable indicator that something may be wrong with code






16. Comprehensive description of software's intended purpose






17. The things a system must do






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






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






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






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






22. A way to automatically grade code based on heuristics






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






24. Evaluates upper limits of operational parameters






25. Each possible path through the code is covered






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






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






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






29. 1st step of requirements gathering






30. 2nd step of requirements gathering






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






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






33. A few sentences summarizing a use case






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






35. The rights governing the ownership and disposition of technology






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






37. The rigorousness of the tests that are able to be placed on the code






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






39. Iterative - incremental framework for project management.






40. Representational State Transfer.






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






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






43. Testing the whole system for functionality






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






45. A method that initializes a newly instantiated object






46. 4th step of requirements gathering






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






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






49. Formal testing against end user specifications






50. Verifies that system is protected against improper penetration