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. Iterative - incremental framework for project management.






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






3. Testing the whole system for functionality






4. Test the run - time performance of the system






5. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu






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






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






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






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






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






11. Figuring out what the requirements are






12. Constraints on the design due to external factors






13. Formal testing against end user specifications






14. 'single dot rule'






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






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






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






18. Techniques for composing objects to form larger structures






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






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






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






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






23. Verifies that system is protected against improper penetration






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






25. Representational State Transfer.






26. People who care about the outcome






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






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






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






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






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






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






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






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






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






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






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






38. Each possible path through the code is covered






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






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






41. Evaluates upper limits of operational parameters






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






43. (smell) code is repeated in multiple places






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






45. Single step in a lifecycle






46. Protecting the embodiment of an idea






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






48. Lack of errors in code - readability etc






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






50. The rights governing the ownership and disposition of technology