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 subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.






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






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






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






5. Tasks that a system must be able to perform






6. A few sentences summarizing a use case






7. How well your fulfil your requirements






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






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






10. A method that initializes a newly instantiated object






11. People who care about the outcome






12. A relationship between objects.






13. Formal testing against end user specifications






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






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






16. Series of phases through which software is developed






17. Techniques for composing objects to form larger structures






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






19. A movement that promotes common formats for data.






20. Each line of code is covered once






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






22. Evaluates upper limits of operational parameters






23. Verifies that system is protected against improper penetration






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






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






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






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






28. Recognizable indicator that something may be wrong with code






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






30. Absence of lifecycle






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






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






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






34. 4th step of requirements gathering






35. The degree to which code is free of defects






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






37. (smell) code is repeated in multiple places






38. (smell) Smell deodorant






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






40. Reusable - abstract 'blocks' of design






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






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






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






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






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






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






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






48. 3rd step of requirements gathering






49. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






50. How developed code is (testing - documentation etc)