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. Single step in a lifecycle






2. Absence of lifecycle






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






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






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






6. The things a system must do






7. The rights governing the ownership and disposition of technology






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






9. Each possible path through the code is covered






10. Recognizable indicator that something may be wrong with code






11. Figuring out what the requirements are






12. 1st step of requirements gathering






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






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






15. A relationship between objects.






16. Contract between inventor - assignee and state giving a time and geographically limited monopoly






17. Evaluates upper limits of operational parameters






18. (smell) Smell deodorant






19. Testing where modules are combined and tested as a group






20. Tasks that a system must be able to perform






21. A movement that promotes common formats for data.






22. A powerful motivator for change






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






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






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






26. How well your fulfil your requirements






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






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






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






30. A few sentences summarizing a use case






31. A method that initializes a newly instantiated object






32. Lack of errors in code - readability etc






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






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






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






36. Series of phases through which software is developed






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






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






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






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






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






42. 'single dot rule'






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






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






45. Each line of code is covered once






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






47. People who care about the outcome






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


49. Representational State Transfer.






50. Protecting the embodiment of an idea