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. Tasks that a system must be able to perform






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






3. 3rd step of requirements gathering






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






5. 1st step of requirements gathering






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






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






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






9. Improve the internal design and implementation of code without affecting external behavior






10. Constraints on the design due to external factors






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






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






13. Formal testing against end user specifications






14. The degree to which code is free of defects






15. Comprehensive description of software's intended purpose






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






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






18. Protecting the embodiment of an idea






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






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






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






22. Executes system in a manner that demands abnormal amounts of resources






23. A movement that promotes common formats for data.






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






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






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






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






28. 4th step of requirements gathering






29. Verifies that system is protected against improper penetration






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






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






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






33. Testing the whole system for functionality






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


35. Reusable - abstract 'blocks' of design






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






37. A few sentences summarizing a use case






38. Single step in a lifecycle






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






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






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






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






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






44. How well your fulfil your requirements






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






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






47. Evaluates upper limits of operational parameters






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






49. Recognizable indicator that something may be wrong with code






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