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






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






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






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


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






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






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






8. Iterative - incremental framework for project management.






9. Absence of lifecycle






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






11. 4th step of requirements gathering






12. Constraints on the design due to external factors






13. Tasks that a system must be able to perform






14. Reusable - abstract 'blocks' of design






15. Figuring out what the requirements are






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






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






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






19. Test the run - time performance of the system






20. 2nd step of requirements gathering






21. Diagram used to show how information flows around the system






22. Single step in a lifecycle






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. Contract between inventor - assignee and state giving a time and geographically limited monopoly






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






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






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






28. Each possible path through the code is covered






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






30. A movement that promotes common formats for data.






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






32. (smell) Smell deodorant






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






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






35. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






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






37. 3rd step of requirements gathering






38. Each line of code is covered once






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






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






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






42. A relationship between objects.






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






44. Representational State Transfer.






45. (smell) code is repeated in multiple places






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






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






48. Lack of errors in code - readability etc






49. Verifies that system is protected against improper penetration






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