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. 4th step of requirements gathering






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






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






4. Protecting the embodiment of an idea






5. A movement that promotes common formats for data.






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






7. The things a system must do






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






9. Testing the whole system for functionality






10. The rights governing the ownership and disposition of technology






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






12. Techniques for composing objects to form larger structures






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






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






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






16. A method that initializes a newly instantiated object






17. Each line of code is covered once






18. People who care about the outcome






19. (smell) code is repeated in multiple places






20. Reusable - abstract 'blocks' of design






21. Iterative - incremental framework for project management.






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






23. Derived methods should not assume more or deliver less






24. Models ->code work is done to keep models in sync with code






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






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






27. Test the run - time performance of the system






28. Recognizable indicator that something may be wrong with code






29. Testing where modules are combined and tested as a group






30. Tasks that a system must be able to perform






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






32. Absence of lifecycle






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






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






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






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






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






38. The degree to which code is free of defects






39. 3rd step of requirements gathering






40. Representational State Transfer.






41. Comprehensive description of software's intended purpose






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






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






44. 'single dot rule'






45. Each possible path through the code is covered






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






47. A way to automatically grade code based on heuristics






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






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






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