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. How well your fulfil your requirements






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


3. Figuring out what the requirements are






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






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






6. Lack of errors in code - readability etc






7. Evaluates upper limits of operational parameters






8. Constraints on the design due to external factors






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






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






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






12. Tasks that a system must be able to perform






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






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






15. A method that initializes a newly instantiated object






16. Iterative - incremental framework for project management.






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






18. The rights governing the ownership and disposition of technology






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






20. The things a system must do






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






22. Recognizable indicator that something may be wrong with code






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






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


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






26. The degree to which code is free of defects






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






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






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






30. A relationship between objects.






31. Absence of lifecycle






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






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






34. Comprehensive description of software's intended purpose






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






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






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






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






39. Each line of code is covered once






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






41. (smell) Smell deodorant






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






43. Formal testing against end user specifications






44. An effective method expressed as a finite list of well- defined instructions for solving a problem.






45. Series of phases through which software is developed






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






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






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






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






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