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. Tasks that a system must be able to perform






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






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






4. Representational State Transfer.






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






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






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






8. Testing the whole system for functionality






9. Iterative - incremental framework for project management.






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






11. 'single dot rule'






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






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






14. 3rd step of requirements gathering






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






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






17. Formal testing against end user specifications






18. People who care about the outcome






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






20. A method that initializes a newly instantiated object






21. Comprehensive description of software's intended purpose






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






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






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






25. Techniques for composing objects to form larger structures






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






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






28. Recognizable indicator that something may be wrong with code






29. Constraints on the design due to external factors






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






31. Derived methods should not assume more or deliver less






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






33. A powerful motivator for change






34. Figuring out what the requirements are






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






36. 1st step of requirements gathering






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






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






39. A movement that promotes common formats for data.






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






41. Reusable - abstract 'blocks' of design






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


43. Evaluates upper limits of operational parameters






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






45. The rights governing the ownership and disposition of technology






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






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






48. 2nd step of requirements gathering






49. 4th step of requirements gathering






50. The degree to which code is free of defects