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. A method that initializes a newly instantiated object






3. Techniques for composing objects to form larger structures






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


5. 2nd step of requirements gathering






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






7. Test the run - time performance of the system






8. A movement that promotes common formats for data.






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






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






11. 1st step of requirements gathering






12. (smell) method has too many statements - loops or variables






13. A relationship between objects.






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






15. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.






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






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






18. Iterative - incremental framework for project management.






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






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






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






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






23. Tasks that a system must be able to perform






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






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






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






27. Series of phases through which software is developed






28. Recognizable indicator that something may be wrong with code






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






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






31. Representational State Transfer.






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






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






34. Reusable - abstract 'blocks' of design






35. Object oriented programming; using objects to solve problems.






36. Absence of lifecycle






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






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. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






40. (smell) code is repeated in multiple places






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






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






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






44. A powerful motivator for change






45. 4th step of requirements gathering






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






47. Figuring out what the requirements are






48. Evaluates upper limits of operational parameters






49. The degree to which code is free of defects






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