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. Description of possible sequences of interactions between a user and the system.






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






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






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






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






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






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






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






9. Lack of errors in code - readability etc






10. Each line of code is covered once






11. 4th step of requirements gathering






12. 'single dot rule'






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






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






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






16. 3rd step of requirements gathering






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






18. Each possible path through the code is covered






19. Derived methods should not assume more or deliver less






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






21. A method that initializes a newly instantiated object






22. A few sentences summarizing a use case






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






24. Tasks that a system must be able to perform






25. Comprehensive description of software's intended purpose






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






27. The things a system must do






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






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






30. Reusable - abstract 'blocks' of design






31. (smell) Smell deodorant






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






33. Constraints on the design due to external factors






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






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






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






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






38. Reusable - abstract 'blocks' of design






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






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


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






42. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






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






44. (smell) code is repeated in multiple places






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






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) method has too many statements - loops or variables






48. A way to automatically grade code based on heuristics






49. A powerful motivator for change






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