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. Reusable - abstract 'blocks' of design






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






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






5. A movement that promotes common formats for data.






6. Lack of errors in code - readability etc






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






8. 1st step of requirements gathering






9. Constraints on the design due to external factors






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






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






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


13. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






14. Recognizable indicator that something may be wrong with code






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






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






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






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






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. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)






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






22. How well your fulfil your requirements






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






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






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






26. (smell) code is repeated in multiple places






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






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


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






30. 'single dot rule'






31. Derived methods should not assume more or deliver less






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






33. Tasks that a system must be able to perform






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






35. Techniques for composing objects to form larger structures






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






37. Series of phases through which software is developed






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






39. The rights governing the ownership and disposition of technology






40. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data






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






42. Iterative - incremental framework for project management.






43. Protecting the embodiment of an idea






44. The degree to which code is free of defects






45. 2nd step of requirements gathering






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






47. Figuring out what the requirements are






48. Reusable - abstract 'blocks' of design






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






50. A few sentences summarizing a use case