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. A powerful motivator for change






2. 'single dot rule'






3. Absence of lifecycle






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






5. Formal testing against end user specifications






6. Reusable - abstract 'blocks' of design






7. A method that initializes a newly instantiated object






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






9. 4th step of requirements gathering






10. 2nd step of requirements gathering






11. Protecting the embodiment of an idea






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






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






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






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






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






17. Series of phases through which software is developed






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






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


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






21. People who care about the outcome






22. The rights governing the ownership and disposition of technology






23. Evaluates upper limits of operational parameters






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






25. Lack of errors in code - readability etc






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






27. Derived methods should not assume more or deliver less






28. The things a system must do






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






30. 1st step of requirements gathering






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






32. (smell) method has too many statements - loops or variables






33. Each possible path through the code is covered






34. Delaying the creation of an object - calculation of a value or another expensive process until first needed.






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






36. A relationship between objects.






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






38. Techniques for composing objects to form larger structures






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






40. (smell) code is repeated in multiple places






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






42. Test the run - time performance of the system






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






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






45. 3rd step of requirements gathering






46. Reusable - abstract 'blocks' of design






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






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






49. Tasks that a system must be able to perform






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