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. Testing tactic based on whether inputs and outputs match up for required functionality






2. Series of phases through which software is developed






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






4. Figuring out what the requirements are






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






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






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






8. Reusable - abstract 'blocks' of design






9. 'single dot rule'






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






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






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






13. (smell) method has too many statements - loops or variables






14. Reusable - abstract 'blocks' of design






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






16. Lack of errors in code - readability etc






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






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






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






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






21. Improve the internal design and implementation of code without affecting external behavior






22. Testing the whole system for functionality






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






24. (smell) Smell deodorant






25. Verifies that system is protected against improper penetration






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


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






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






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






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






31. A few sentences summarizing a use case






32. People who care about the outcome






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






34. Evaluates upper limits of operational parameters






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






36. 4th step of requirements gathering






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






38. Recognizable indicator that something may be wrong with code






39. 2nd step of requirements gathering






40. Iterative - incremental framework for project management.






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






42. Each possible path through the code is covered






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






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






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






46. The degree to which code is free of defects






47. Formal testing against end user specifications






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






49. 1st step of requirements gathering






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