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. (smell) A method using another class more than its own






2. Figuring out what the requirements are






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






4. Test the run - time performance of the system






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






6. Each line of code is covered once






7. A method that initializes a newly instantiated object






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






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






10. Recognizable indicator that something may be wrong with code






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






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






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






14. Comprehensive description of software's intended purpose






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






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






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






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


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






20. Representational State Transfer.






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






22. Absence of lifecycle






23. A few sentences summarizing a use case






24. Techniques for composing objects to form larger structures






25. 1st step of requirements gathering






26. Verifies that system is protected against improper penetration






27. A relationship between objects.






28. (smell) Smell deodorant






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






30. Each possible path through the code is covered






31. How well your fulfil your requirements






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






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






34. 4th step of requirements gathering






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






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






37. The degree to which code is free of defects






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






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






40. Derived methods should not assume more or deliver less






41. 2nd step of requirements gathering






42. Single step in a lifecycle






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






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






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






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






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






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






49. Lack of errors in code - readability etc






50. Protecting the embodiment of an idea