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. Verifies that system is protected against improper penetration






2. (smell) A class whose only purpose is to hold data






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






4. Absence of lifecycle






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






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






7. 1st step of requirements gathering






8. How well your fulfil your requirements






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






10. (smell) code is repeated in multiple places






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






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






13. A movement that promotes common formats for data.






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






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






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






17. 'single dot rule'






18. Reusable - abstract 'blocks' of design






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






20. (smell) Making one change requires changes in multiple places






21. Each possible path through the code is covered






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






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






24. Evaluates upper limits of operational parameters






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






26. Lack of errors in code - readability etc






27. People who care about the outcome






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






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






30. Representational State Transfer.






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






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






33. Tasks that a system must be able to perform






34. A way to automatically grade code based on heuristics






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






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






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






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






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






40. A method that initializes a newly instantiated object






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






42. Techniques for composing objects to form larger structures






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






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






45. Figuring out what the requirements are






46. 3rd step of requirements gathering






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






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






49. A powerful motivator for change






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