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.
Decorator pattern
unit testing
long method
Security testing
2. (smell) Making one change requires changes in multiple places
Design Patterns
long method
data clumps
shotgun surgery
3. Testing where modules are combined and tested as a group
Integration testing
duplicated code
Phase
Dijkstra's law
4. (smell) A class whose only purpose is to hold data
Usability testing
Specification
Data classes
Dijkstra's law
5. The degree to which code is free of defects
Fully- dressed use case
Phase
Use case diagram
code quality
6. A way to automatically grade code based on heuristics
Code Quality
Use case diagram
Quality metrics
statement
7. A few sentences summarizing a use case
Lambda
Acceptance testing
Design pattern
brief use case
8. 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
Delegation
Quality metrics
white box testing
black box testing
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. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
Maturity
Elicitation
Large class
11. Recognizable indicator that something may be wrong with code
code smell
Programming syntax
Use case diagram
Delegation
12. A movement that promotes common formats for data.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
OOP
Semantic Web
Database normalization
13. Ways to express the system's subsystems and their relationship
Dijkstra's law
Lazy initialization or Lazy loading (Design pattern)
architectural design
SOAP
14. 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.
Stakeholders
technical managerial approach
long method
First- class citizen
15. 4th step of requirements gathering
code smell
Design patterns
Validation
Cowboy coding
16. Testing that verifies that individual units of source code are working
unit testing
conflict
Lambda
data clumps
17. Reusable - abstract 'blocks' of design
patent
Design pattern
Programming syntax
path
18. Techniques for composing objects to form larger structures
Algorithm
Design patterns
white box testing
sequence diagram
19. Tasks that a system must be able to perform
Performance testing
Elicitation
Delegation
Functional Requirements
20. Protecting the embodiment of an idea
copyright
Liskov substitution principle
conflict
Lifecycle
21. How well your fulfil your requirements
Software Quality
First- class citizen
Lifecycle
duplicated code
22. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Specification
Programming style
Cowboy coding
Stakeholders
23. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
path
jquery
Dijkstra's law
long parameter list
24. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Test- driven development
Delegation
Maturity
Database normalization
25. (smell) Classes using things that should be private in other classes
feature envy
Phase
Security testing
inappropriate intimacy
26. Reusable - abstract 'blocks' of design
black box testing
Design Patterns
shotgun surgery
model- driven development
27. Testing tactic based on whether inputs and outputs match up for required functionality
black box testing
Software Quality
Test- driven development
Cowboy coding
28. 3rd step of requirements gathering
white box testing
Lexer
Design Patterns
Specification
29. Force software to fail in order to see how it recovers
Dijkstra's law
Acceptance testing
Recovery testing
Programming style
30. Verifies that system is protected against improper penetration
Software Quality
middle man
Security testing
OOP
31. A computer program that divides code up into functional components
Parser
Design Patterns
Data classes
Integration testing
32. Figuring out what the requirements are
white box testing
regression testing
Elicitation
technical managerial approach
33. A powerful motivator for change
conflict
regression testing
Non - functional Requirements
Software Quality
34. (smell) method has too many statements - loops or variables
Association
long method
Maturity
Dijkstra's law
35. 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.
Analysis...
Design patterns
Programming syntax
Association
36. Absence of lifecycle
Cowboy coding
Usability testing
Design
message chain
37. The rigorousness of the tests that are able to be placed on the code
Maturity
Algorithm
code quality
Scrum (Agile software development)
38. (smell) A method using another class more than its own
technical managerial approach
feature envy
software quality
Lifecycle
39. (smell) code is repeated in multiple places
Requirements
Test- driven development
Lexer
duplicated code
40. Each line of code is covered once
Acceptance testing
feature- driven development
Lazy initialization or Lazy loading (Design pattern)
statement
41. Testing the whole system for functionality
sequence diagram
model- driven development
system testing
brief use case
42. Single step in a lifecycle
model- driven development
Closure
Phase
duplicated code
43. 2nd step of requirements gathering
regression testing
sequence diagram
model- driven development
Analysis...
44. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Analysis...
SOP
REST
Feasibility
45. (smell) many parameters are being passed into a method
use case
Elicitation
long parameter list
Maturity level
46. Freezing the state of the source code at a particular point
Elicitation
middle man
Versioning
Database normalization
47. Testing tactic that looks at all ways that data can flow through the code
Capacity testing
SRS Documentation
Requirements
white box testing
48. Test cases made -> code compiles -> make code pass
Test- driven development
conflict
copyright
REST
49. Small - behaviour- preserving - source- to- source transformation
data clumps
Phase
Liskov substitution principle
a refactoring
50. Derived methods should not assume more or deliver less
Lambda
Liskov substitution principle
Large class
Capacity testing