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. Figuring out what the requirements are
Lazy initialization or Lazy loading (Design pattern)
inappropriate intimacy
Elicitation
Performance testing
2. Testing that verifies that individual units of source code are working
Closure
conflict
Design patterns
unit testing
3. 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.
Capacity testing
model- driven development
Dijkstra's law
Programming syntax
4. The rigorousness of the tests that are able to be placed on the code
trademark
Capacity testing
Maturity
Integration testing
5. Reusable - abstract 'blocks' of design
Constructor
Phase
Design Patterns
architectural design
6. (smell) Making one change requires changes in multiple places
WSDL
inappropriate intimacy
regression testing
shotgun surgery
7. Testing the whole system for functionality
system testing
trademark
Dijkstra's law
intellectual property
8. (smell) A class whose only purpose is to hold data
Programming syntax
Data classes
code smell
SOAP
9. How well your fulfil your requirements
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Refactoring
Software Quality
middle man
10. 4th step of requirements gathering
Validation
Lambda
copyright
Programming syntax
11. Test cases made -> code compiles -> make code pass
Analysis...
Stress testing
comments
Test- driven development
12. Derived methods should not assume more or deliver less
Delegation
Lazy initialization or Lazy loading (Design pattern)
model- driven development
Liskov substitution principle
13. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
SOAP
Functional Requirements
Programming style
system testing
14. Models ->code work is done to keep models in sync with code
WSDL
Lifecycle
Recovery testing
model- driven development
15. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Use case diagram
Anonymous function
Elicitation
white box testing
16. Single step in a lifecycle
inappropriate intimacy
REST
Phase
black box testing
17. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Lifecycle
long method
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Test- driven development
18. 1st step of requirements gathering
Elicitation
REST
system testing
Lexer
19. Freezing the state of the source code at a particular point
Stakeholders
Versioning
Feasibility
Parser
20. Tasks that a system must be able to perform
white box testing
Lexer
Functional Requirements
software quality
21. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
REST
message chain
code quality
Lazy initialization or Lazy loading (Design pattern)
22. Force software to fail in order to see how it recovers
Maturity
SOP
Liskov substitution principle
Recovery testing
23. Verifies that system is protected against improper penetration
Security testing
Database normalization
feature envy
system testing
24. A way to automatically grade code based on heuristics
Quality metrics
unit testing
data clumps
path
25. A relationship between objects.
Association
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Security testing
Analysis...
26. (smell) Classes using things that should be private in other classes
Parser
WSDL
inappropriate intimacy
Feasibility
27. Test the run - time performance of the system
Specification
Performance testing
Algorithm
Maturity
28. A method that initializes a newly instantiated object
Lazy initialization or Lazy loading (Design pattern)
Closure
conflict
Constructor
29. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
system testing
Stakeholders
long parameter list
30. 3rd step of requirements gathering
unit testing
statement
Specification
Lazy initialization or Lazy loading (Design pattern)
31. Testing tactic based on whether inputs and outputs match up for required functionality
feature envy
Requirements
black box testing
model- driven development
32. (smell) If a set of variables are used together in multiple places
data clumps
long parameter list
Software Quality
Lambda
33. Formal testing against end user specifications
Delegation
Acceptance testing
Anonymous function
Specification
34. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
feature- driven development
Code Quality
Lexer
35. Test whether or not tasks can be accomplished efficiently by all levels of users
Association
Programming syntax
Functional Requirements
Usability testing
36. Each team member given set of features to work on
feature- driven development
technical managerial approach
Association
white box testing
37. Reusable - abstract 'blocks' of design
intellectual property
Design pattern
a refactoring
Use case diagram
38. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
architectural design
Integration testing
SOP
39. 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
duplicated code
data clumps
architectural design
Delegation
40. An operator used to denote anonymous functions or closures.
Lifecycle
Lambda
patent
Law of demeter
41. 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.
First- class citizen
Validation
Recovery testing
WSDL
42. The things a system must do
model- driven development
Use case diagram
SRS Documentation
Requirements
43. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
comments
duplicated code
Denormalization
Database normalization
44. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
jquery
Maturity level
Delegation
45. Recognizable indicator that something may be wrong with code
architectural design
code smell
Design pattern
Lexer
46. (smell) client needs to use one object to get another and then use that one to get another
message chain
Lazy initialization or Lazy loading (Design pattern)
Closure
a refactoring
47. Approach to team management that splits management up into two people with separate tasks
Design Patterns
code smell
technical managerial approach
Algorithm
48. Executes system in a manner that demands abnormal amounts of resources
Functional Requirements
Stress testing
Design Patterns
Maturity
49. One or two paragraphs of text outlining a use case
Decorator pattern
Casual use case
long parameter list
Parser
50. Techniques for composing objects to form larger structures
Design patterns
Functional Requirements
Liskov substitution principle
Lambda