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. Diagram outlining the tasks that are going to be performed by the user






2. (smell) many parameters are being passed into a method






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






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






5. Each line of code is covered once






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






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






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






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






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






11. Test the run - time performance of the system






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






13. Reusable - abstract 'blocks' of design






14. A few sentences summarizing a use case






15. 'single dot rule'






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. Improve the internal design and implementation of code without affecting external behavior






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






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






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






21. A method that initializes a newly instantiated object






22. Verifies that system is protected against improper penetration






23. A way to automatically grade code based on heuristics






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






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






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






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






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






29. Techniques for composing objects to form larger structures






30. Lack of errors in code - readability etc






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






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






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






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






35. 1st step of requirements gathering






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






37. (smell) code is repeated in multiple places






38. Single step in a lifecycle






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






40. Absence of lifecycle






41. Protecting the embodiment of an idea






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






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






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






45. (smell) Classes using things that should be private in other classes






46. Testing the whole system for functionality






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






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






49. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






50. Reusable - abstract 'blocks' of design