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 rights governing the ownership and disposition of technology






2. A method that initializes a newly instantiated object






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. Description of possible sequences of interactions between a user and the system.






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






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






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






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






9. Tasks that a system must be able to perform






10. Each line of code is covered once






11. Evaluates upper limits of operational parameters






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






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






14. Series of phases through which software is developed






15. (smell) code is repeated in multiple places






16. (smell) Smell deodorant






17. Testing tactic based on whether inputs and outputs match up for required functionality






18. 2nd step of requirements gathering






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






20. Figuring out what the requirements are






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






22. 3rd step of requirements gathering






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






24. 1st step of requirements gathering






25. Derived methods should not assume more or deliver less






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






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






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






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






30. A relationship between objects.






31. Representational State Transfer.






32. Absence of lifecycle






33. Constraints on the design due to external factors






34. 'single dot rule'






35. Verifies that system is protected against improper penetration






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






37. Formal testing against end user specifications






38. How well your fulfil your requirements






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






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






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






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






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






44. Single step in a lifecycle






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






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






47. The things a system must do






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






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






50. A way to automatically grade code based on heuristics