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. Models ->code work is done to keep models in sync with code






2. A movement that promotes common formats for data.






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






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






5. Testing the whole system for functionality






6. Iterative - incremental framework for project management.






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






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






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


10. Representational State Transfer.






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






12. A method that initializes a newly instantiated object






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






14. Test the run - time performance of the system






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






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






17. Evaluates upper limits of operational parameters






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






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






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






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






22. Tasks that a system must be able to perform






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






24. How well your fulfil your requirements






25. 4th step of requirements gathering






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






27. Derived methods should not assume more or deliver less






28. Reusable - abstract 'blocks' of design






29. Each line of code is covered once






30. The rights governing the ownership and disposition of technology






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






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






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






34. (smell) Smell deodorant






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






36. 3rd step of requirements gathering






37. Single step in a lifecycle






38. People who care about the outcome






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






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






41. A few sentences summarizing a use case






42. Reusable - abstract 'blocks' of design






43. Techniques for composing objects to form larger structures






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






45. Formal testing against end user specifications






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






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






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






49. Protecting the embodiment of an idea






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