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. Series of phases through which software is developed






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






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






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






5. Lack of errors in code - readability etc






6. Evaluates upper limits of operational parameters






7. 4th step of requirements gathering






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






9. A relationship between objects.






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






11. (smell) A method using another class more than its own






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






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






14. Single step in a lifecycle






15. Representational State Transfer.






16. The degree to which code is free of defects






17. Figuring out what the requirements are






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






19. Protecting the embodiment of an idea






20. A method that initializes a newly instantiated object






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






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






23. People who care about the outcome






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






25. Iterative - incremental framework for project management.






26. Reusable - abstract 'blocks' of design






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






28. 3rd step of requirements gathering






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






30. Each possible path through the code is covered






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






32. Test the run - time performance of the system






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






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






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






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






37. Testing can show the presence but not absence of errors


38. The things a system must do






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






40. Testing the whole system for functionality






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






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






43. Tasks that a system must be able to perform






44. (smell) code is repeated in multiple places






45. Comprehensive description of software's intended purpose






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






47. 2nd step of requirements gathering






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






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






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