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 powerful motivator for change
duplicated code
Large class
Security testing
conflict
2. Small - behaviour- preserving - source- to- source transformation
SRS Documentation
a refactoring
trademark
brief use case
3. Representational State Transfer.
Database normalization
long method
code quality
REST
4. A relationship between objects.
Association
Lazy initialization or Lazy loading (Design pattern)
data clumps
WSDL
5. Improve the internal design and implementation of code without affecting external behavior
Specification
Refactoring
Lexer
Parser
6. Figuring out what the requirements are
Stakeholders
Elicitation
jquery
brief use case
7. The rights governing the ownership and disposition of technology
Security testing
intellectual property
message chain
shotgun surgery
8. Lack of errors in code - readability etc
Casual use case
Code Quality
branch
shotgun surgery
9. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
copyright
Cowboy coding
Design patterns
10. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
technical managerial approach
Analysis...
long parameter list
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
11. (smell)class with too many instance variables or too much code
Cowboy coding
Specification
Programming syntax
Large class
12. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Law of demeter
Functional Requirements
branch
Denormalization
13. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
regression testing
Recovery testing
jquery
14. Evaluates upper limits of operational parameters
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Elicitation
Capacity testing
Phase
15. The things a system must do
Lambda
Acceptance testing
Programming style
Requirements
16. People who care about the outcome
Stress testing
Stakeholders
Security testing
brief use case
17. 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
18. Reusable - abstract 'blocks' of design
Maturity
unit testing
Capacity testing
Design Patterns
19. Reusable - abstract 'blocks' of design
Law of demeter
long method
Design pattern
Requirements
20. Ways to express the system's subsystems and their relationship
architectural design
SRS Documentation
SOP
brief use case
21. (smell) A class whose only purpose is to hold data
feature- driven development
Data classes
Scrum (Agile software development)
Acceptance testing
22. Testing that verifies that individual units of source code are working
Cowboy coding
unit testing
Parser
technical managerial approach
23. Comprehensive description of software's intended purpose
SRS Documentation
Delegation
Software Quality
Design patterns
24. Formal document outlining a task that needs to be performed on a system
software quality
Fully- dressed use case
Design
Decorator pattern
25. One or two paragraphs of text outlining a use case
Casual use case
use case
Code Quality
message chain
26. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Programming syntax
jquery
a refactoring
Anonymous function
27. Single step in a lifecycle
Elicitation
Elicitation
Security testing
Phase
28. 3rd step of requirements gathering
Programming syntax
Specification
Dijkstra's law
Lambda
29. Executes system in a manner that demands abnormal amounts of resources
feature- driven development
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Stress testing
regression testing
30. Testing tactic that looks at all ways that data can flow through the code
Closure
Design Patterns
technical managerial approach
white box testing
31. A few sentences summarizing a use case
Specification
Dijkstra's law
Database normalization
brief use case
32. (smell) Classes using things that should be private in other classes
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
inappropriate intimacy
long parameter list
Law of demeter
33. (smell) code is repeated in multiple places
feature- driven development
Test- driven development
duplicated code
intellectual property
34. Recognizable indicator that something may be wrong with code
code smell
First- class citizen
inappropriate intimacy
statement
35. Diagram outlining the tasks that are going to be performed by the user
Dijkstra's law
Use case diagram
Law of demeter
feature- driven development
36. Each team member given set of features to work on
WSDL
feature- driven development
shotgun surgery
message chain
37. Diagram used to show how information flows around the system
sequence diagram
SOAP
Programming style
Delegation
38. Models ->code work is done to keep models in sync with code
conflict
Refactoring
model- driven development
architectural design
39. Word - logo or symbol used to distinguish one organization's wares and services from another's
middle man
Feasibility
Large class
trademark
40. Protecting the embodiment of an idea
Liskov substitution principle
Requirements
copyright
SRS Documentation
41. The rigorousness of the tests that are able to be placed on the code
message chain
Maturity
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Closure
42. Derived methods should not assume more or deliver less
black box testing
Use case diagram
Liskov substitution principle
message chain
43. 4th step of requirements gathering
Requirements
data clumps
Validation
First- class citizen
44. Verifies that system is protected against improper penetration
Security testing
Requirements
OOP
Acceptance testing
45. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Analysis...
SOAP
intellectual property
Validation
46. 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
47. An effective method expressed as a finite list of well- defined instructions for solving a problem.
duplicated code
Analysis...
Algorithm
feature envy
48. (smell) Making one change requires changes in multiple places
shotgun surgery
Analysis...
Acceptance testing
Lazy initialization or Lazy loading (Design pattern)
49. (smell) Smell deodorant
comments
Fully- dressed use case
Specification
First- class citizen
50. Constraints on the design due to external factors
Design patterns
Design Patterns
long method
Non - functional Requirements