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. Testing tactic based on whether inputs and outputs match up for required functionality






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






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






4. (smell) code is repeated in multiple places






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






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






7. Lack of errors in code - readability etc






8. 3rd step of requirements gathering






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






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






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






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






13. A few sentences summarizing a use case






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






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






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






17. Representational State Transfer.






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






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






20. Tasks that a system must be able to perform






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






22. A powerful motivator for change






23. Single step in a lifecycle






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






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






26. Verifies that system is protected against improper penetration






27. The degree to which code is free of defects






28. Series of phases through which software is developed






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






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






31. Constraints on the design due to external factors






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






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






34. Absence of lifecycle






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






36. 2nd step of requirements gathering






37. Reusable - abstract 'blocks' of design






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






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






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






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






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






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






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






45. Testing the whole system for functionality






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






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






48. 1st step of requirements gathering






49. 4th step of requirements gathering






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