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. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






3. 2nd step of requirements gathering






4. Each line of code is covered once






5. A way to automatically grade code based on heuristics






6. Verifies that system is protected against improper penetration






7. Tasks that a system must be able to perform






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






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






10. A method that initializes a newly instantiated object






11. Series of phases through which software is developed






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






13. A powerful motivator for change






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






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






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






17. A few sentences summarizing a use case






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






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






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






21. Comprehensive description of software's intended purpose






22. The degree to which code is free of defects






23. Absence of lifecycle






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






25. Representational State Transfer.






26. Each possible path through the code is covered






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






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






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






30. (smell) Smell deodorant






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






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






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






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






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






36. A relationship between objects.






37. 4th step of requirements gathering






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






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






40. (smell) code is repeated in multiple places






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






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






43. 'single dot rule'






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






45. 1st step of requirements gathering






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






47. The rights governing the ownership and disposition of technology






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






49. Reusable - abstract 'blocks' of design






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







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