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


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






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






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






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






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






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






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






10. (smell) Smell deodorant






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






12. Lack of errors in code - readability etc






13. (smell) code is repeated in multiple places






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






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






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






17. Models ->code work is done to keep models in sync with code






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






19. Iterative - incremental framework for project management.






20. 3rd step of requirements gathering






21. The degree to which code is free of defects






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






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






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






25. The rights governing the ownership and disposition of technology






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






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






28. A movement that promotes common formats for data.






29. Series of phases through which software is developed






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






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


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






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






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






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






36. Each possible path through the code is covered






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






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






39. Testing the whole system for functionality






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






41. A relationship between objects.






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






43. Each team member given set of features to work on






44. Comprehensive description of software's intended purpose






45. 2nd step of requirements gathering






46. Formal testing against end user specifications






47. Reusable - abstract 'blocks' of design






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






49. Single step in a lifecycle






50. A method that initializes a newly instantiated object