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. Each team member given set of features to work on






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






3. Reusable - abstract 'blocks' of design






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






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






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






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






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






9. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






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






11. Iterative - incremental framework for project management.






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






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






14. Test the run - time performance of the system






15. A powerful motivator for change






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






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






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






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






20. 1st step of requirements gathering






21. (smell) code is repeated in multiple places






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






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






24. The rights governing the ownership and disposition of technology






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






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






27. Series of phases through which software is developed






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






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






30. A method that initializes a newly instantiated object






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






32. 2nd step of requirements gathering






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






34. (smell) Smell deodorant






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






36. Representational State Transfer.






37. Lack of errors in code - readability etc






38. Testing the whole system for functionality






39. Comprehensive description of software's intended purpose






40. 4th step of requirements gathering






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






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






43. Absence of lifecycle






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


45. Recognizable indicator that something may be wrong with code






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






47. Single step in a lifecycle






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






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






50. A few sentences summarizing a use case