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. Protecting the embodiment of an idea






2. Lack of errors in code - readability etc






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






4. Constraints on the design due to external factors






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






6. Recognizable indicator that something may be wrong with code






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






8. Formal testing against end user specifications






9. The degree to which code is free of defects






10. 2nd step of requirements gathering






11. A few sentences summarizing a use case






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






13. Representational State Transfer.






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






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






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






17. Reusable - abstract 'blocks' of design






18. Techniques for composing objects to form larger structures






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






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






21. (smell) Smell deodorant






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






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






24. The things a system must do






25. 3rd step of requirements gathering






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






27. How well your fulfil your requirements






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






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






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






31. Iterative - incremental framework for project management.






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






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






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






35. A computer program that divides code up into functional components






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






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






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






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






40. Diagram used to show how information flows around the system






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






42. 'single dot rule'






43. Each line of code is covered once






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






45. Series of phases through which software is developed






46. Reusable - abstract 'blocks' of design






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






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






49. Comprehensive description of software's intended purpose






50. Figuring out what the requirements are