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. Diagram outlining the tasks that are going to be performed by the user






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






3. Tasks that a system must be able to perform






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






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






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






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






8. Reusable - abstract 'blocks' of design






9. A movement that promotes common formats for data.






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






11. People who care about the outcome






12. 'single dot rule'






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


14. Figuring out what the requirements are






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. Test the run - time performance of the system






17. Absence of lifecycle






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






19. Each line of code is covered once






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






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






22. Iterative - incremental framework for project management.






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






24. Reusable - abstract 'blocks' of design






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






26. A powerful motivator for change






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






28. 4th step of requirements gathering






29. Verifies that system is protected against improper penetration






30. Formal testing against end user specifications






31. 1st step of requirements gathering






32. Techniques for composing objects to form larger structures






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






34. A few sentences summarizing a use case






35. A way to automatically grade code based on heuristics






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






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






38. 3rd step of requirements gathering






39. Each possible path through the code is covered






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






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






42. Series of phases through which software is developed






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






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






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






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






47. Evaluates upper limits of operational parameters






48. Testing tactic based on whether inputs and outputs match up for required functionality






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






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