SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Software Engineering Vocab
Start Test
Study First
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. Force software to fail in order to see how it recovers
Recovery testing
message chain
OOP
Design Patterns
2. People who care about the outcome
path
SOAP
Stakeholders
feature- driven development
3. A way to automatically grade code based on heuristics
Functional Requirements
Quality metrics
shotgun surgery
Versioning
4. Each line of code is covered once
trademark
Maturity
model- driven development
statement
5. A movement that promotes common formats for data.
Versioning
Maturity
Constructor
Semantic Web
6. Formal testing against end user specifications
inappropriate intimacy
jquery
Acceptance testing
Semantic Web
7. (smell) One class delegates all of its requests to another class
middle man
long parameter list
Analysis...
Refactoring
8. A relationship between objects.
Lifecycle
Association
Programming style
Quality metrics
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. 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.
long parameter list
First- class citizen
path
Non - functional Requirements
11. Recognizable indicator that something may be wrong with code
First- class citizen
intellectual property
Algorithm
code smell
12. One or two paragraphs of text outlining a use case
Casual use case
inappropriate intimacy
Design pattern
Software Quality
13. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Lifecycle
technical managerial approach
Elicitation
WSDL
14. Formal document outlining a task that needs to be performed on a system
OOP
Fully- dressed use case
unit testing
Validation
15. Test whether or not tasks can be accomplished efficiently by all levels of users
long parameter list
Versioning
Use case diagram
Usability testing
16. Word - logo or symbol used to distinguish one organization's wares and services from another's
statement
technical managerial approach
Validation
trademark
17. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Recovery testing
brief use case
jquery
Association
18. (smell) If a set of variables are used together in multiple places
Cowboy coding
Large class
Liskov substitution principle
data clumps
19. 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
Usability testing
Closure
Test- driven development
Lazy initialization or Lazy loading (Design pattern)
20. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Versioning
Algorithm
Usability testing
feature- driven development
21. An operator used to denote anonymous functions or closures.
Closure
unit testing
Lambda
Programming syntax
22. Testing where modules are combined and tested as a group
Analysis...
Lambda
Versioning
Integration testing
23. Diagram used to show how information flows around the system
sequence diagram
Law of demeter
long parameter list
Design
24. 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
25. 'single dot rule'
patent
Law of demeter
SRS Documentation
Programming style
26. (smell) A method using another class more than its own
regression testing
Capacity testing
Anonymous function
feature envy
27. Iterative - incremental framework for project management.
Scrum (Agile software development)
Closure
copyright
long method
28. The things a system must do
Non - functional Requirements
middle man
Requirements
a refactoring
29. (smell) A class whose only purpose is to hold data
Integration testing
Data classes
Anonymous function
patent
30. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Scrum (Agile software development)
Dijkstra's law
Anonymous function
SOAP
31. Degree to which the system meets the specified requirements and development standards
software quality
Semantic Web
patent
code smell
32. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Design pattern
Requirements
Software Quality
33. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Acceptance testing
Casual use case
Lexer
Validation
34. Testing that verifies that individual units of source code are working
Stress testing
Programming syntax
unit testing
SRS Documentation
35. Tasks that a system must be able to perform
trademark
Functional Requirements
Stress testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
36. Testing tactic based on whether inputs and outputs match up for required functionality
data clumps
black box testing
Elicitation
Requirements
37. Small - behaviour- preserving - source- to- source transformation
conflict
a refactoring
code quality
duplicated code
38. 1st step of requirements gathering
Elicitation
long method
jquery
intellectual property
39. Testing tactic that looks at all ways that data can flow through the code
regression testing
Delegation
white box testing
Algorithm
40. A powerful motivator for change
Design Patterns
conflict
Delegation
Decorator pattern
41. Diagram outlining the tasks that are going to be performed by the user
Use case diagram
trademark
architectural design
Casual use case
42. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
WSDL
system testing
SRS Documentation
43. 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
Acceptance testing
Cowboy coding
shotgun surgery
Delegation
44. Ways to express the system's subsystems and their relationship
Code Quality
Lifecycle
Decorator pattern
architectural design
45. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
comments
long method
Denormalization
Programming syntax
46. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Database normalization
SOP
Elicitation
WSDL
47. (smell) Classes using things that should be private in other classes
inappropriate intimacy
Lazy initialization or Lazy loading (Design pattern)
Lexer
Acceptance testing
48. The rigorousness of the tests that are able to be placed on the code
Requirements
Maturity
Scrum (Agile software development)
Dijkstra's law
49. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
SOAP
Requirements
Validation
Database normalization
50. Derived methods should not assume more or deliver less
Non - functional Requirements
Liskov substitution principle
Decorator pattern
Design patterns