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. Diagram used to show how information flows around the system






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






3. Techniques for composing objects to form larger structures






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






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






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






7. Verifies that system is protected against improper penetration






8. A few sentences summarizing a use case






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






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






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






12. A way to automatically grade code based on heuristics






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






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






15. Test the run - time performance of the system






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






17. Testing the whole system for functionality






18. 1st step of requirements gathering






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






20. 3rd step of requirements gathering






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


22. Reusable - abstract 'blocks' of design






23. Formal testing against end user specifications






24. The things a system must do






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






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






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






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






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






30. Tasks that a system must be able to perform






31. Absence of lifecycle






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






33. How well your fulfil your requirements






34. The rights governing the ownership and disposition of technology






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






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






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






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






39. Single step in a lifecycle






40. (smell) Smell deodorant






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






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






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






44. Each possible path through the code is covered






45. Comprehensive description of software's intended purpose






46. (smell) code is repeated in multiple places






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






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






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






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