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. An operator used to denote anonymous functions or closures.






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






3. 2nd step of requirements gathering






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






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






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






7. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






8. The degree to which code is free of defects






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






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






11. Single step in a lifecycle






12. A method that initializes a newly instantiated object






13. Reusable - abstract 'blocks' of design






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






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






16. Absence of lifecycle






17. The rights governing the ownership and disposition of technology






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






19. A way to automatically grade code based on heuristics






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






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






22. A powerful motivator for change






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






24. (smell) Smell deodorant






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






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






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


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






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






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






31. 3rd step of requirements gathering






32. Each line of code is covered once






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






34. Formal testing against end user specifications






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






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






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






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






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






40. Derived methods should not assume more or deliver less






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






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






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






44. Series of phases through which software is developed






45. Iterative - incremental framework for project management.






46. Testing tactic based on whether inputs and outputs match up for required functionality






47. Tasks that a system must be able to perform






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






49. Figuring out what the requirements are






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