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. Iterative - incremental framework for project management.






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






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






4. 4th step of requirements gathering






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. A way to automatically grade code based on heuristics






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






8. Absence of lifecycle






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






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






11. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.






12. Evaluates upper limits of operational parameters






13. Each line of code is covered once






14. Constraints on the design due to external factors






15. The rights governing the ownership and disposition of technology






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






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






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






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






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






21. Protecting the embodiment of an idea






22. (smell) client needs to use one object to get another and then use that one to get another






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






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






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






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






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






28. Reusable - abstract 'blocks' of design






29. Comprehensive description of software's intended purpose






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






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






32. Test the run - time performance of the system






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






34. The degree to which code is free of defects






35. 2nd step of requirements gathering






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






37. Recognizable indicator that something may be wrong with code






38. Series of phases through which software is developed






39. Word - logo or symbol used to distinguish one organization's wares and services from another's






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






41. Testing the whole system for functionality






42. Each possible path through the code is covered






43. A few sentences summarizing a use case






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






45. Testing tactic that looks at all ways that data can flow through the code






46. 'single dot rule'






47. People who care about the outcome






48. Derived methods should not assume more or deliver less






49. Reusable - abstract 'blocks' of design






50. Techniques for composing objects to form larger structures