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 condition is covered twice (true - false)






2. Comprehensive description of software's intended purpose






3. Evaluates upper limits of operational parameters






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






5. (smell) code is repeated in multiple places






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






7. Iterative - incremental framework for project management.






8. Testing that verifies that individual units of source code are working






9. Each line of code is covered once






10. The things a system must do






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






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






13. 3rd step of requirements gathering






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






15. Protecting the embodiment of an idea






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






17. A powerful motivator for change






18. A few sentences summarizing a use case






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






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






21. The rights governing the ownership and disposition of technology






22. A design pattern that allows behaviour to be added to an existing object dynamically.






23. Absence of lifecycle






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






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






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






27. The degree to which code is free of defects






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






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






30. A way to automatically grade code based on heuristics






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






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






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






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


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






36. Single step in a lifecycle






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






38. Reusable - abstract 'blocks' of design






39. Constraints on the design due to external factors






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






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






42. Testing the whole system for functionality






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






44. People who care about the outcome






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






46. How well your fulfil your requirements






47. Verifies that system is protected against improper penetration






48. A movement that promotes common formats for data.






49. Figuring out what the requirements are






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