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. The degree to which code is free of defects






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






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






4. A method that initializes a newly instantiated object






5. Techniques for composing objects to form larger structures






6. A movement that promotes common formats for data.






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






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






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






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






11. Test the run - time performance of the system






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






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


14. 4th step of requirements gathering






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






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






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






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






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






20. Derived methods should not assume more or deliver less






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






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






23. Figuring out what the requirements are






24. Reusable - abstract 'blocks' of design






25. 'single dot rule'






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






27. Freezing the state of the source code at a particular point






28. Lack of errors in code - readability etc






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






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






31. Each line of code is covered once






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






33. Series of phases through which software is developed






34. Tasks that a system must be able to perform






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






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






37. The things a system must do






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






39. Evaluates upper limits of operational parameters






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






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






42. Representational State Transfer.






43. Description of possible sequences of interactions between a user and the system.






44. How well your fulfil your requirements






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






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






47. Word - logo or symbol used to distinguish one organization's wares and services from another's






48. Verifies that system is protected against improper penetration






49. Iterative - incremental framework for project management.






50. (smell) Smell deodorant