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. Testing that verifies that individual units of source code are working






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






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






4. Each line of code is covered once






5. Evaluates upper limits of operational parameters






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






7. Lack of errors in code - readability etc






8. Testing can show the presence but not absence of errors


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






10. The things a system must do






11. Techniques for composing objects to form larger structures






12. Reusable - abstract 'blocks' of design






13. Tasks that a system must be able to perform






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






15. Derived methods should not assume more or deliver less






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






17. (smell) Smell deodorant






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






19. Absence of lifecycle






20. Formal testing against end user specifications






21. 1st step of requirements gathering






22. A few sentences summarizing a use case






23. A movement that promotes common formats for data.






24. Figuring out what the requirements are






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






26. A method that initializes a newly instantiated object






27. Recognizable indicator that something may be wrong with code






28. Protecting the embodiment of an idea






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






30. Test the run - time performance of the system






31. The rights governing the ownership and disposition of technology






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






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






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






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






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






37. Constraints on the design due to external factors






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






39. 3rd step of requirements gathering






40. Word - logo or symbol used to distinguish one organization's wares and services from another's






41. Series of phases through which software is developed






42. How well your fulfil your requirements






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






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






45. Iterative - incremental framework for project management.






46. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu






47. A way to automatically grade code based on heuristics






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






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






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