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. Approach to team management that splits management up into two people with separate tasks






2. A way to automatically grade code based on heuristics






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






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






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. Object oriented programming; using objects to solve problems.






7. How well your fulfil your requirements






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






9. Single step in a lifecycle






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






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






12. Figuring out what the requirements are






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






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






15. A few sentences summarizing a use case






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






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






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






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






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






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






22. A movement that promotes common formats for data.






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






24. The things a system must do






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






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






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






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






29. Verifies that system is protected against improper penetration






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






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






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






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






34. 4th step of requirements gathering






35. Protecting the embodiment of an idea






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






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






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






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






40. Derived methods should not assume more or deliver less






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






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






43. 2nd step of requirements gathering






44. Comprehensive description of software's intended purpose






45. Tasks that a system must be able to perform






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






47. The rights governing the ownership and disposition of technology






48. The degree to which code is free of defects






49. A method that initializes a newly instantiated object






50. 3rd step of requirements gathering







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests