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. Each team member given set of features to work on






2. (smell) If a set of variables are used together in multiple places






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






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






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






6. (smell) Smell deodorant






7. Verifies that system is protected against improper penetration






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






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






10. A few sentences summarizing a use case






11. Formal testing against end user specifications






12. AKA: Object - Entity - or Value - An entity that can be constructed at run - time - passed as a parameter - returned from a subroutine - or assigned into a variable.






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






14. A movement that promotes common formats for data.






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






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






17. Each possible path through the code is covered






18. Evaluates upper limits of operational parameters






19. Iterative - incremental framework for project management.






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






21. Recognizable indicator that something may be wrong with code






22. 4th step of requirements gathering






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


24. How well your fulfil your requirements






25. Representational State Transfer.






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






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






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






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






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


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






32. Derived methods should not assume more or deliver less






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






34. A way to automatically grade code based on heuristics






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






36. Series of phases through which software is developed






37. 2nd step of requirements gathering






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






39. A powerful motivator for change






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






41. Techniques for composing objects to form larger structures






42. The degree to which code is free of defects






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






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






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






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






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






48. 'single dot rule'






49. Contract between inventor - assignee and state giving a time and geographically limited monopoly






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