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. Object oriented programming; using objects to solve problems.






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






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






4. Series of phases through which software is developed






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






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






7. Comprehensive description of software's intended purpose






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






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






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






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






12. Representational State Transfer.






13. Protecting the embodiment of an idea






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






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


16. A way to automatically grade code based on heuristics






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






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






19. 2nd step of requirements gathering






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






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






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






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






24. Test the run - time performance of the system






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






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






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






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






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






30. Iterative - incremental framework for project management.






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






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






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






34. 4th step of requirements gathering






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






36. 1st step of requirements gathering






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






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






39. Formal testing against end user specifications






40. Testing the whole system for functionality






41. 'single dot rule'






42. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic






43. A powerful motivator for change






44. Recognizable indicator that something may be wrong with code






45. Diagram used to show how information flows around the system






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






47. Evaluates upper limits of operational parameters






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






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






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