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. A powerful motivator for change






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






3. Recognizable indicator that something may be wrong with code






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






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






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






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






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






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






10. The rights governing the ownership and disposition of technology






11. Lack of errors in code - readability etc






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






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






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






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






16. People who care about the outcome






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


18. 'single dot rule'






19. Protecting the embodiment of an idea






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






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






22. Absence of lifecycle






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






24. A way to automatically grade code based on heuristics






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






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






27. (smell) Smell deodorant






28. A relationship between objects.






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






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






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






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






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






34. The degree to which code is free of defects






35. Approach to team management that splits management up into two people with separate tasks






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






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






38. 2nd step of requirements gathering






39. Formal testing against end user specifications






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






41. Representational State Transfer.






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






43. Reusable - abstract 'blocks' of design






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






45. A movement that promotes common formats for data.






46. 3rd step of requirements gathering






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






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






49. A method that initializes a newly instantiated object






50. 1st step of requirements gathering