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. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.






2. A few sentences summarizing a use case






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






4. Single step in a lifecycle






5. Constraints on the design due to external factors






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






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






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






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






10. (smell) One class delegates all of its requests to another class






11. 'single dot rule'






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






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


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






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






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






17. Tasks that a system must be able to perform






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






19. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered






20. Representational State Transfer.






21. 3rd step of requirements gathering






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






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






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






25. Series of phases through which software is developed






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






27. A relationship between objects.






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






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






30. The things a system must do






31. A powerful motivator for change






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






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






34. A method that initializes a newly instantiated object






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






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






37. The degree to which code is free of defects






38. Iterative - incremental framework for project management.






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






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






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






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






43. Formal testing against end user specifications






44. Comprehensive description of software's intended purpose






45. Each possible path through the code is covered






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






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






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






49. Evaluates upper limits of operational parameters






50. Protecting the embodiment of an idea