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. A design pattern that allows behaviour to be added to an existing object dynamically.
black box testing
Decorator pattern
data clumps
brief use case
2. 2nd step of requirements gathering
SOP
Analysis...
Maturity level
Acceptance testing
3. One or two paragraphs of text outlining a use case
Casual use case
Lazy initialization or Lazy loading (Design pattern)
message chain
Quality metrics
4. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Semantic Web
Denormalization
statement
shotgun surgery
5. 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
6. Techniques for composing objects to form larger structures
Elicitation
brief use case
Design patterns
middle man
7. Models ->code work is done to keep models in sync with code
Refactoring
model- driven development
comments
Constructor
8. A relationship between objects.
Lifecycle
OOP
code quality
Association
9. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Data classes
Denormalization
Lexer
Semantic Web
10. 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
sequence diagram
Decorator pattern
SOP
Closure
11. (smell) code is repeated in multiple places
duplicated code
Programming syntax
Dijkstra's law
Cowboy coding
12. Degree to which the system meets the specified requirements and development standards
Use case diagram
Stakeholders
software quality
Parser
13. Each possible path through the code is covered
branch
path
Usability testing
a refactoring
14. (smell) One class delegates all of its requests to another class
middle man
code quality
Data classes
Software Quality
15. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
sequence diagram
Law of demeter
Anonymous function
regression testing
16. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Casual use case
software quality
Functional Requirements
Database normalization
17. Single step in a lifecycle
Phase
Recovery testing
WSDL
long method
18. Derived methods should not assume more or deliver less
Liskov substitution principle
patent
feature- driven development
comments
19. Diagram outlining the tasks that are going to be performed by the user
Lambda
Data classes
Software Quality
Use case diagram
20. (smell) many parameters are being passed into a method
long parameter list
Fully- dressed use case
SRS Documentation
regression testing
21. Representational State Transfer.
model- driven development
Usability testing
REST
sequence diagram
22. (smell) If a set of variables are used together in multiple places
Lexer
message chain
Programming style
data clumps
23. Reusable - abstract 'blocks' of design
Code Quality
Design pattern
Stress testing
Dijkstra's law
24. A method that initializes a newly instantiated object
Scrum (Agile software development)
software quality
Constructor
Elicitation
25. Iterative - incremental framework for project management.
Scrum (Agile software development)
Elicitation
Code Quality
Liskov substitution principle
26. (smell) client needs to use one object to get another and then use that one to get another
message chain
trademark
Anonymous function
Non - functional Requirements
27. Testing where modules are combined and tested as a group
Integration testing
Closure
Feasibility
Stakeholders
28. The rigorousness of the tests that are able to be placed on the code
Maturity
Liskov substitution principle
model- driven development
Stakeholders
29. Word - logo or symbol used to distinguish one organization's wares and services from another's
shotgun surgery
message chain
trademark
Stakeholders
30. Description of possible sequences of interactions between a user and the system.
use case
Use case diagram
sequence diagram
Association
31. Each team member given set of features to work on
Quality metrics
feature- driven development
Acceptance testing
patent
32. Test cases made -> code compiles -> make code pass
Fully- dressed use case
Algorithm
Test- driven development
Database normalization
33. Verifies that system is protected against improper penetration
Software Quality
Lexer
Non - functional Requirements
Security testing
34. Recognizable indicator that something may be wrong with code
First- class citizen
code smell
conflict
Algorithm
35. Lack of errors in code - readability etc
Large class
copyright
Code Quality
statement
36. Testing tactic based on whether inputs and outputs match up for required functionality
Dijkstra's law
SOAP
black box testing
Stakeholders
37. (smell) Smell deodorant
Casual use case
brief use case
Programming style
comments
38. (smell) A class whose only purpose is to hold data
conflict
patent
code smell
Data classes
39. Absence of lifecycle
Cowboy coding
white box testing
Maturity level
inappropriate intimacy
40. How well your fulfil your requirements
Software Quality
model- driven development
Elicitation
Performance testing
41. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Design pattern
model- driven development
Dijkstra's law
42. An operator used to denote anonymous functions or closures.
Large class
code smell
Design
Lambda
43. Reusable - abstract 'blocks' of design
Lexer
Law of demeter
Design Patterns
SOP
44. The things a system must do
data clumps
Requirements
feature envy
software quality
45. Testing tactic that looks at all ways that data can flow through the code
Dijkstra's law
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
OOP
white box testing
46. (smell) A method using another class more than its own
Analysis...
Closure
Fully- dressed use case
feature envy
47. Formal document outlining a task that needs to be performed on a system
SOAP
Feasibility
Quality metrics
Fully- dressed use case
48. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Quality metrics
middle man
Security testing
49. 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.
Algorithm
unit testing
First- class citizen
Lexer
50. Freezing the state of the source code at a particular point
Liskov substitution principle
Association
Parser
Versioning