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. Testing that verifies that individual units of source code are working






3. 1st step of requirements gathering






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






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






6. (smell) code is repeated in multiple places






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






8. Comprehensive description of software's intended purpose






9. Absence of lifecycle






10. 2nd step of requirements gathering






11. Techniques for composing objects to form larger structures






12. Reusable - abstract 'blocks' of design






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






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






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






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






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






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






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






20. Each possible path through the code is covered






21. Constraints on the design due to external factors






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


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






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






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






26. A few sentences summarizing a use case






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






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






29. Iterative - incremental framework for project management.






30. A way to automatically grade code based on heuristics






31. Small - behaviour- preserving - source- to- source transformation






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






33. Each line of code is covered once






34. Representational State Transfer.






35. A method that initializes a newly instantiated object






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






37. 3rd step of requirements gathering






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


39. Recognizable indicator that something may be wrong with code






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






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






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. Figuring out what the requirements are






44. The degree to which code is free of defects






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






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






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






48. People who care about the outcome






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






50. Tasks that a system must be able to perform