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. The things a system must do






2. The rights governing the ownership and disposition of technology






3. Reusable - abstract 'blocks' of design






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






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






6. A relationship between objects.






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






8. Recognizable indicator that something may be wrong with code






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






10. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






11. 4th step of requirements gathering






12. Derived methods should not assume more or deliver less






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






14. Protecting the embodiment of an idea






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






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






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






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






19. (smell) code is repeated in multiple places






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






21. Test the run - time performance of the system






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






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






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






25. Representational State Transfer.






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






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






28. People who care about the outcome






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






30. Testing that verifies that individual units of source code are working






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






32. A powerful motivator for change






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






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






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






36. Lack of errors in code - readability etc






37. Absence of lifecycle






38. Reusable - abstract 'blocks' of design






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






40. Verifies that system is protected against improper penetration






41. Series of phases through which software is developed






42. A few sentences summarizing a use case






43. A method that initializes a newly instantiated object






44. Comprehensive description of software's intended purpose






45. 3rd step of requirements gathering






46. A way to automatically grade code based on heuristics






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






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






49. (smell) Smell deodorant






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