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






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






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






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






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






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






7. 4th step of requirements gathering






8. A way to automatically grade code based on heuristics






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






10. 1st step of requirements gathering






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






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






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






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






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






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






17. Lack of errors in code - readability etc






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






19. Each possible path through the code is covered






20. Iterative - incremental framework for project management.






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






22. Verifies that system is protected against improper penetration






23. Absence of lifecycle






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






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






26. (smell) client needs to use one object to get another and then use that one to get another






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






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






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






30. (smell) Smell deodorant






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






32. Reusable - abstract 'blocks' of design






33. Recognizable indicator that something may be wrong with code






34. The degree to which code is free of defects






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






36. Reusable - abstract 'blocks' of design






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






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






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






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






41. How well your fulfil your requirements






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






43. Each line of code is covered once






44. 2nd step of requirements gathering






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






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






47. Protecting the embodiment of an idea






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






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






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