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. A powerful motivator for change






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






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






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






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






6. The rights governing the ownership and disposition of technology






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






8. 1st step of requirements gathering






9. Series of phases through which software is developed






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






11. The degree to which code is free of defects






12. A way to automatically grade code based on heuristics






13. A movement that promotes common formats for data.






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






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






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






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






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






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


20. (smell) Smell deodorant






21. Representational State Transfer.






22. 4th step of requirements gathering






23. Figuring out what the requirements are






24. A method that initializes a newly instantiated object






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






26. Verifies that system is protected against improper penetration






27. Reusable - abstract 'blocks' of design






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






29. (smell) code is repeated in multiple places






30. Derived methods should not assume more or deliver less






31. Formal testing against end user specifications






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






33. Recognizable indicator that something may be wrong with code






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


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






36. Each possible path through the code is covered






37. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.






38. The things a system must do






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






40. A few sentences summarizing a use case






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






42. People who care about the outcome






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






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






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






46. Evaluates upper limits of operational parameters






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






48. Techniques for composing objects to form larger structures






49. Lack of errors in code - readability etc






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