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. A method that initializes a newly instantiated object






2. The things a system must do






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






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






5. Test the run - time performance of the system






6. Representational State Transfer.






7. Derived methods should not assume more or deliver less






8. A powerful motivator for change






9. Single step in a lifecycle






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






11. Recognizable indicator that something may be wrong with code






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






13. (smell) Smell deodorant






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






15. 2nd step of requirements gathering






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






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






18. A movement that promotes common formats for data.






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






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






21. 4th step of requirements gathering






22. Tasks that a system must be able to perform






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






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






25. Formal testing against end user specifications






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






27. 'single dot rule'






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






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






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






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






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






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






34. Protecting the embodiment of an idea






35. Each line of code is covered once






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






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






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






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






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






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






42. A way to automatically grade code based on heuristics






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






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






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






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






47. (smell) code is repeated in multiple places






48. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






49. People who care about the outcome






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