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. (smell) A class whose only purpose is to hold data






2. Verifies that system is protected against improper penetration






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






4. How well your fulfil your requirements






5. Derived methods should not assume more or deliver less






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






7. Reusable - abstract 'blocks' of design






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






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






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






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






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






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






14. Comprehensive description of software's intended purpose






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






16. Lack of errors in code - readability etc






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






18. 3rd step of requirements gathering






19. Representational State Transfer.






20. Each line of code is covered once






21. The things a system must do






22. People who care about the outcome






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






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






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






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






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






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






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






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






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






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






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






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






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






36. A powerful motivator for change






37. A way to automatically grade code based on heuristics






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






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






40. 4th step of requirements gathering






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






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






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






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






45. One or two paragraphs of text outlining a use case






46. Single step in a lifecycle






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






48. Testing the whole system for functionality






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






50. Evaluates upper limits of operational parameters