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. Each team member given set of features to work on






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






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






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






5. 'single dot rule'






6. The things a system must do






7. Absence of lifecycle






8. Testing the whole system for functionality






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






10. (smell) code is repeated in multiple places






11. Tasks that a system must be able to perform






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






13. Single step in a lifecycle






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






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






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






17. A powerful motivator for change






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






19. Testing can show the presence but not absence of errors


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






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






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






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






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






25. 3rd step of requirements gathering






26. Each possible path through the code is covered






27. Constraints on the design due to external factors






28. Each line of code is covered once






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






30. The rights governing the ownership and disposition of technology






31. A way to automatically grade code based on heuristics






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






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






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






35. (smell) If a set of variables are used together in multiple places






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






37. How well your fulfil your requirements






38. Testing can show the presence but not absence of errors


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






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






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






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






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






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






45. Recognizable indicator that something may be wrong with code






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






47. Representational State Transfer.






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






49. Series of phases through which software is developed






50. Verifies that system is protected against improper penetration