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






2. Each possible path through the code is covered






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






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






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






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






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






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






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






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






11. Figuring out what the requirements are






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






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






14. 'single dot rule'






15. Series of phases through which software is developed






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






17. A movement that promotes common formats for data.






18. Ways to express the system's subsystems and their relationship






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






20. A method that initializes a newly instantiated object






21. Iterative - incremental framework for project management.






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






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






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






25. Verifies that system is protected against improper penetration






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






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


28. Lack of errors in code - readability etc






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






30. Derived methods should not assume more or deliver less






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






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






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






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






35. Representational State Transfer.






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






37. Tasks that a system must be able to perform






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






39. Comprehensive description of software's intended purpose






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






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






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






43. Recognizable indicator that something may be wrong with code






44. Testing the whole system for functionality






45. The degree to which code is free of defects






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






47. (smell) Smell deodorant






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






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






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