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. Diagram used to show how information flows around the system






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






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






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






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






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






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






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






9. Each line of code is covered once






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






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






12. Techniques for composing objects to form larger structures






13. Evaluates upper limits of operational parameters






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






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






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






17. (smell) code is repeated in multiple places






18. Constraints on the design due to external factors






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






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






21. 1st step of requirements gathering






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






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






24. Formal testing against end user specifications






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






26. Reusable - abstract 'blocks' of design






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






28. 2nd step of requirements gathering






29. Single step in a lifecycle






30. How well your fulfil your requirements






31. An operator used to denote anonymous functions or closures.






32. The degree to which code is free of defects






33. The things a system must do






34. Figuring out what the requirements are






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






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






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






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






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






40. Representational State Transfer.






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






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






43. Verifies that system is protected against improper penetration






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






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






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






47. 4th step of requirements gathering






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






49. People who care about the outcome






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







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