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. Word - logo or symbol used to distinguish one organization's wares and services from another's






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






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






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






5. Series of phases through which software is developed






6. One or two paragraphs of text outlining a use case






7. Constraints on the design due to external factors






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






9. Testing tactic based on whether inputs and outputs match up for required functionality






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






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






12. Derived methods should not assume more or deliver less






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






14. 3rd step of requirements gathering






15. The degree to which code is free of defects






16. Protecting the embodiment of an idea






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






18. A powerful motivator for change






19. 1st step of requirements gathering






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






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






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






23. A method that initializes a newly instantiated object






24. Lack of errors in code - readability etc






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






26. Test the run - time performance of the system






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






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






29. Figuring out what the requirements are






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






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






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


33. Reusable - abstract 'blocks' of design






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. Degree to which the system meets the specified requirements and development standards






36. Each line of code is covered once






37. Comprehensive description of software's intended purpose






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






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






40. A few sentences summarizing a use case






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






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






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






44. Each possible path through the code is covered






45. Verifies that system is protected against improper penetration






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






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






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






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






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