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. (smell)class with too many instance variables or too much code






2. How well your fulfil your requirements






3. Testing the whole system for functionality






4. Constraints on the design due to external factors






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






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






7. Tasks that a system must be able to perform






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






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






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






11. Single step in a lifecycle






12. Series of phases through which software is developed






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


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






15. 'single dot rule'






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






17. Reusable - abstract 'blocks' of design






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






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






20. Absence of lifecycle






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






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






23. Delaying the creation of an object - calculation of a value or another expensive process until first needed.






24. (smell) Smell deodorant






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






26. Iterative - incremental framework for project management.






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






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






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






30. Evaluates upper limits of operational parameters






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






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






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






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






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






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






37. People who care about the outcome






38. Test the run - time performance of the system






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






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






41. Comprehensive description of software's intended purpose






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






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


44. Each line of code is covered once






45. 3rd step of requirements gathering






46. Formal testing against end user specifications






47. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.






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






49. Each possible path through the code is covered






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