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 where modules are combined and tested as a group






2. Series of phases through which software is developed






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






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






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






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






7. Test the run - time performance of the system






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






9. Recognizable indicator that something may be wrong with code






10. Each possible path through the code is covered






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






12. A relationship between objects.






13. Representational State Transfer.






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






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






16. Formal testing against end user specifications






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






18. Derived methods should not assume more or deliver less






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






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






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






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






23. 2nd step of requirements gathering






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






25. How well your fulfil your requirements






26. Verifies that system is protected against improper penetration






27. Each line of code is covered once






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






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






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






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






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






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






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






35. Absence of lifecycle






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






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






38. Testing the whole system for functionality






39. The degree to which code is free of defects






40. Iterative - incremental framework for project management.






41. Evaluates upper limits of operational parameters






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






43. A few sentences summarizing a use case






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






45. Tasks that a system must be able to perform






46. A way to automatically grade code based on heuristics






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






48. Single step in a lifecycle






49. A method that initializes a newly instantiated object






50. Techniques for composing objects to form larger structures