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. Tasks that a system must be able to perform






2. Protecting the embodiment of an idea






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






4. Reusable - abstract 'blocks' of design






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






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






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






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






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






10. Figuring out what the requirements are






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






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






13. 2nd step of requirements gathering






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






15. Representational State Transfer.






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


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






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






19. People who care about the outcome






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






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






22. (smell) code is repeated in multiple places






23. How well your fulfil your requirements






24. A powerful motivator for change






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






26. A method that initializes a newly instantiated object






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






28. Absence of lifecycle






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






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






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






32. 3rd step of requirements gathering






33. Evaluates upper limits of operational parameters






34. Testing the whole system for functionality






35. Lack of errors in code - readability etc






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






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






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






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






40. Verifies that system is protected against improper penetration






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






42. Series of phases through which software is developed






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






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






45. A few sentences summarizing a use case






46. 4th step of requirements gathering






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






48. Force software to fail in order to see how it recovers






49. Comprehensive description of software's intended purpose






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