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. AKA: Object - Entity - or Value - An entity that can be constructed at run - time - passed as a parameter - returned from a subroutine - or assigned into a variable.






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






3. Formal testing against end user specifications






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






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






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






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






8. Evaluates upper limits of operational parameters






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






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






11. A few sentences summarizing a use case






12. A relationship between objects.






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






14. Representational State Transfer.






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






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






17. The things a system must do






18. 4th step of requirements gathering






19. 1st step of requirements gathering






20. Figuring out what the requirements are






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






22. Lack of errors in code - readability etc






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






24. Each line of code is covered once






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






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






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






28. Reusable - abstract 'blocks' of design






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






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






31. 'single dot rule'






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






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






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






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






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






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






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






39. (smell) code is repeated in multiple places






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






41. A powerful motivator for change






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






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






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


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






46. Derived methods should not assume more or deliver less






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






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






49. Absence of lifecycle






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