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. Techniques for composing objects to form larger structures






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






3. Formal testing against end user specifications






4. Recognizable indicator that something may be wrong with code






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






6. Reusable - abstract 'blocks' of design






7. Representational State Transfer.






8. 1st step of requirements gathering






9. Each line of code is covered once






10. 3rd step of requirements gathering






11. Tasks that a system must be able to perform






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






13. Reusable - abstract 'blocks' of design






14. A powerful motivator for change






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






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






17. Test the run - time performance of the system






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






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






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






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






22. A movement that promotes common formats for data.






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






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






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






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






27. A way to automatically grade code based on heuristics






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






29. Protecting the embodiment of an idea






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






31. (smell) code is repeated in multiple places






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






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






34. 'single dot rule'






35. Evaluates upper limits of operational parameters






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

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


37. Derived methods should not assume more or deliver less






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






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






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






41. A few sentences summarizing a use case






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






43. Test whether or not tasks can be accomplished efficiently by all levels of users






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






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






46. (smell) Smell deodorant






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






48. A method that initializes a newly instantiated object






49. Comprehensive description of software's intended purpose






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