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. Protecting the embodiment of an idea






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






3. Testing the whole system for functionality






4. A relationship between objects.






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






6. The things a system must do






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






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






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






10. 4th step of requirements gathering






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






12. Series of phases through which software is developed






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






14. A method that initializes a newly instantiated object






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






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






17. 'single dot rule'






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






19. Formal testing against end user specifications






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






21. Comprehensive description of software's intended purpose






22. Recognizable indicator that something may be wrong with code






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






24. Constraints on the design due to external factors






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






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






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






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






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






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






31. 1st step of requirements gathering






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






33. Each possible path through the code is covered






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






35. Derived methods should not assume more or deliver less






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






37. Figuring out what the requirements are






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






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






40. Single step in a lifecycle






41. Lack of errors in code - readability etc






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






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






44. Techniques for composing objects to form larger structures






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






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






47. The degree to which code is free of defects






48. Each line of code is covered once






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






50. A few sentences summarizing a use case