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. Single step in a lifecycle






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






3. 'single dot rule'






4. Tasks that a system must be able to perform






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






6. A movement that promotes common formats for data.






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






8. Formal testing against end user specifications






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






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






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






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






13. Testing the whole system for functionality






14. 2nd step of requirements gathering






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






16. Verifies that system is protected against improper penetration






17. A powerful motivator for change






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






19. Test the run - time performance of the system






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






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






22. A few sentences summarizing a use case






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






24. Figuring out what the requirements are






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






26. Developing a plan for a product - system or component. 'how' a system should perform a task






27. Evaluates upper limits of operational parameters






28. People who care about the outcome






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






30. 3rd step of requirements gathering






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






32. Each possible path through the code is covered






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






34. Representational State Transfer.






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






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






37. Techniques for composing objects to form larger structures






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






39. How well your fulfil your requirements






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






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






42. 4th step of requirements gathering






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






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






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






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


47. Each line of code is covered once






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






49. Reusable - abstract 'blocks' of design






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