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. Reusable - abstract 'blocks' of design






2. (smell) Smell deodorant






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






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






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






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






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






8. Test the run - time performance of the system






9. 1st step of requirements gathering






10. Techniques for composing objects to form larger structures






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






12. A way to automatically grade code based on heuristics






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






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






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






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






17. Testing the whole system for functionality






18. Comprehensive description of software's intended purpose






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






20. Constraints on the design due to external factors






21. Recognizable indicator that something may be wrong with code






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






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






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






25. A relationship between objects.






26. Formal testing against end user specifications






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






28. 3rd step of requirements gathering






29. People who care about the outcome






30. Evaluates upper limits of operational parameters






31. Small - behaviour- preserving - source- to- source transformation






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






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






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






35. A method that initializes a newly instantiated object






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






37. How well your fulfil your requirements






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






39. Tasks that a system must be able to perform






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






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






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






43. Each line of code is covered once






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






45. A few sentences summarizing a use case






46. The degree to which code is free of defects






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






48. Lack of errors in code - readability etc






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






50. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.