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. Single step in a lifecycle






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






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






4. The degree to which code is free of defects






5. A movement that promotes common formats for data.






6. Protecting the embodiment of an idea






7. A powerful motivator for change






8. Testing the whole system for functionality






9. Lack of errors in code - readability etc






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






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






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






13. Reusable - abstract 'blocks' of design






14. Representational State Transfer.






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






16. 4th step of requirements gathering






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






18. Tasks that a system must be able to perform






19. A relationship between objects.






20. A way to automatically grade code based on heuristics






21. The things a system must do






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






23. Constraints on the design due to external factors






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






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






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






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






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






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


30. Test the run - time performance of the system






31. How well your fulfil your requirements






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






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






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






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


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






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






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






39. People who care about the outcome






40. Reusable - abstract 'blocks' of design






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






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






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






44. (smell) Smell deodorant






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






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






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






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






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






50. Figuring out what the requirements are