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






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






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






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






5. Each condition is covered twice (true - false)






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






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






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






9. A method that initializes a newly instantiated object






10. A way to automatically grade code based on heuristics






11. Single step in a lifecycle






12. People who care about the outcome






13. 4th step of requirements gathering






14. Tasks that a system must be able to perform






15. Figuring out what the requirements are






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. 3rd step of requirements gathering






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






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






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






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






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






23. A powerful motivator for change






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






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






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






27. Representational State Transfer.






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






29. A design pattern that allows behaviour to be added to an existing object dynamically.






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






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






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






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






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






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






36. Each possible path through the code is covered






37. (smell) code is repeated in multiple places






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






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






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






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






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






43. Reusable - abstract 'blocks' of design






44. Lack of errors in code - readability etc






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






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






47. Testing the whole system for functionality






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






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






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