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. (smell) A method using another class more than its own






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






3. Protecting the embodiment of an idea






4. Derived methods should not assume more or deliver less






5. People who care about the outcome






6. How well your fulfil your requirements






7. Testing the whole system for functionality






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






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






10. (smell) code is repeated in multiple places






11. (smell) Smell deodorant






12. 4th step of requirements gathering






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






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






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






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






17. 2nd step of requirements gathering






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






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






20. Lack of errors in code - readability etc






21. A way to automatically grade code based on heuristics






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






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






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






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. Freezing the state of the source code at a particular point






27. The rights governing the ownership and disposition of technology






28. Force software to fail in order to see how it recovers






29. Techniques for composing objects to form larger structures






30. Each line of code is covered once






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






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






33. A movement that promotes common formats for data.






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






35. Verifies that system is protected against improper penetration






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






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






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






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






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






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


42. Single step in a lifecycle






43. A few sentences summarizing a use case






44. Iterative - incremental framework for project management.






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






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


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






48. Evaluates upper limits of operational parameters






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






50. Tasks that a system must be able to perform