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. One or two paragraphs of text outlining a use case






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






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






4. Word - logo or symbol used to distinguish one organization's wares and services from another's






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






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






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






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






9. (smell) Smell deodorant






10. Single step in a lifecycle






11. How well your fulfil your requirements






12. Recognizable indicator that something may be wrong with code






13. Lack of errors in code - readability etc






14. A powerful motivator for change






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






16. Test the run - time performance of the system






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






18. Reusable - abstract 'blocks' of design






19. Series of phases through which software is developed






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






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






22. A method that initializes a newly instantiated object






23. A set of rules that define the combinations of symbols that are considered to be correctly structured in a specific programming language. Example: In many programming languages - statements are terminated by a semicolon.






24. A way to automatically grade code based on heuristics






25. Iterative - incremental framework for project management.






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






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






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






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. Improve the internal design and implementation of code without affecting external behavior






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






32. Derived methods should not assume more or deliver less






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






34. Tasks that a system must be able to perform






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






36. Reusable - abstract 'blocks' of design






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






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






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






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






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






42. Verifies that system is protected against improper penetration






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






44. Evaluates upper limits of operational parameters






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






46. People who care about the outcome






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






48. Techniques for composing objects to form larger structures






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






50. Constraints on the design due to external factors