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. An operator used to denote anonymous functions or closures.






2. Formal testing against end user specifications






3. How well your fulfil your requirements






4. The things a system must do






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


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






7. A movement that promotes common formats for data.






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






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






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






11. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






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






13. Each possible path through the code is covered






14. Absence of lifecycle






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






16. The degree to which code is free of defects






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






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






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






20. Lack of errors in code - readability etc






21. Iterative - incremental framework for project management.






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






23. Recognizable indicator that something may be wrong with code






24. A relationship between objects.






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






26. 3rd step of requirements gathering






27. (smell) code is repeated in multiple places






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






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






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






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






32. A few sentences summarizing a use case






33. Testing the whole system for functionality






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






35. A method that initializes a newly instantiated object






36. Each line of code is covered once






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






38. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu






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


40. Series of phases through which software is developed






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






42. The rights governing the ownership and disposition of technology






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






44. People who care about the outcome






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






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






47. A powerful motivator for change






48. Techniques for composing objects to form larger structures






49. 'single dot rule'






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