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. Test cases made -> code compiles -> make code pass






2. Recognizable indicator that something may be wrong with code






3. 1st step of requirements gathering






4. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures






5. Testing the whole system for functionality






6. Formal testing against end user specifications






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






8. A powerful motivator for change






9. Representational State Transfer.






10. A way to automatically grade code based on heuristics






11. (smell) A class whose only purpose is to hold data






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






13. The rights governing the ownership and disposition of technology






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






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






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






17. Evaluates upper limits of operational parameters






18. Tasks that a system must be able to perform






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






20. Test the run - time performance of the system






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






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






23. The things a system must do






24. 3rd step of requirements gathering






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






26. 2nd step of requirements gathering






27. Each line of code is covered once






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






29. Constraints on the design due to external factors






30. A movement that promotes common formats for data.






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






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






33. 4th step of requirements gathering






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






35. Each possible path through the code is covered






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






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






38. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)






39. Protecting the embodiment of an idea






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






41. Reusable - abstract 'blocks' of design






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






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






44. The degree to which code is free of defects






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






46. A relationship between objects.






47. People who care about the outcome






48. How well your fulfil your requirements






49. Iterative - incremental framework for project management.






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