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. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






2. 1st step of requirements gathering






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






4. An effective method expressed as a finite list of well- defined instructions for solving a problem.






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






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






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






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






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






10. (smell) code is repeated in multiple places






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






12. Derived methods should not assume more or deliver less






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






14. A movement that promotes common formats for data.






15. Constraints on the design due to external factors






16. The things a system must do






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






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






19. Representational State Transfer.






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






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






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






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






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






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






26. Techniques for composing objects to form larger structures






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






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






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






30. Lack of errors in code - readability etc






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






32. A powerful motivator for change






33. Verifies that system is protected against improper penetration






34. Reusable - abstract 'blocks' of design






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






36. Each possible path through the code is covered






37. Tasks that a system must be able to perform






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


39. 3rd step of requirements gathering






40. How well your fulfil your requirements






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






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






43. Single step in a lifecycle






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






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






46. A relationship between objects.






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






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






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






50. Absence of lifecycle