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. People who care about the outcome






2. Absence of lifecycle






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






4. Each line of code is covered once






5. 3rd step of requirements gathering






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






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






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






9. Test the run - time performance of the system






10. Figuring out what the requirements are






11. (smell) A method using another class more than its own






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


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






14. Formal testing against end user specifications






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






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


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






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






19. Reusable - abstract 'blocks' of design






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






21. A movement that promotes common formats for data.






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






23. 2nd step of requirements gathering






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






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






26. The rights governing the ownership and disposition of technology






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






28. 4th step of requirements gathering






29. Comprehensive description of software's intended purpose






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






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






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






33. Techniques for composing objects to form larger structures






34. Lack of errors in code - readability etc






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






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






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






38. Protecting the embodiment of an idea






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






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






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






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






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






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






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






46. Verifies that system is protected against improper penetration






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






48. Reusable - abstract 'blocks' of design






49. Evaluates upper limits of operational parameters






50. A method that initializes a newly instantiated object