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. Absence of lifecycle






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






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






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






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






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






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






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






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






10. (smell) code is repeated in multiple places






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






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






13. 2nd step of requirements gathering






14. Derived methods should not assume more or deliver less






15. (smell) Smell deodorant






16. Each line of code is covered once






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






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






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






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






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






22. A way to automatically grade code based on heuristics






23. Reusable - abstract 'blocks' of design






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






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






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






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






28. Test the run - time performance of the system






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






30. The things a system must do






31. (smell) A class whose only purpose is to hold data






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






33. Testing the whole system for functionality






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






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






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






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






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






39. Degree to which the system meets the specified requirements and development standards






40. Reusable - abstract 'blocks' of design






41. Series of phases through which software is developed






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






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






44. Verifies that system is protected against improper penetration






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






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






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






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






49. A movement that promotes common formats for data.






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