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. Testing the whole system for functionality
Cowboy coding
system testing
Parser
message chain
2. 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.
Programming syntax
Phase
Lambda
jquery
3. Protecting the embodiment of an idea
Elicitation
copyright
Cowboy coding
a refactoring
4. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
unit testing
Cowboy coding
jquery
Semantic Web
5. 3rd step of requirements gathering
Feasibility
Specification
a refactoring
software quality
6. Improve the internal design and implementation of code without affecting external behavior
copyright
Design
Dijkstra's law
Refactoring
7. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
code quality
Maturity
Lazy initialization or Lazy loading (Design pattern)
software quality
8. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Data classes
Requirements
Lazy initialization or Lazy loading (Design pattern)
Lexer
9. Diagram used to show how information flows around the system
Acceptance testing
sequence diagram
Non - functional Requirements
patent
10. Ways to express the system's subsystems and their relationship
Semantic Web
feature envy
architectural design
Analysis...
11. 'single dot rule'
Versioning
Law of demeter
Lexer
Usability testing
12. Each line of code is covered once
SOP
statement
sequence diagram
First- class citizen
13. One or two paragraphs of text outlining a use case
Data classes
Dijkstra's law
code smell
Casual use case
14. Object oriented programming; using objects to solve problems.
OOP
code quality
Fully- dressed use case
SRS Documentation
15. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
feature envy
Maturity level
software quality
regression testing
16. (smell) If a set of variables are used together in multiple places
Delegation
SRS Documentation
data clumps
Acceptance testing
17. Reusable - abstract 'blocks' of design
OOP
model- driven development
Design pattern
Denormalization
18. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Test- driven development
patent
Feasibility
Recovery testing
19. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
patent
Anonymous function
comments
a refactoring
20. Derived methods should not assume more or deliver less
Liskov substitution principle
sequence diagram
path
Stress testing
21. Figuring out what the requirements are
feature- driven development
Use case diagram
Elicitation
shotgun surgery
22. Representational State Transfer.
Database normalization
REST
Analysis...
middle man
23. (smell) many parameters are being passed into a method
Association
Lazy initialization or Lazy loading (Design pattern)
long parameter list
software quality
24. (smell) code is repeated in multiple places
Design pattern
Feasibility
Decorator pattern
duplicated code
25. 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
Closure
Law of demeter
Validation
Lexer
26. Evaluates upper limits of operational parameters
Validation
Capacity testing
Maturity level
Anonymous function
27. (smell) method has too many statements - loops or variables
long method
jquery
Versioning
Closure
28. Test the run - time performance of the system
Performance testing
trademark
Code Quality
middle man
29. A method that initializes a newly instantiated object
Lazy initialization or Lazy loading (Design pattern)
Code Quality
conflict
Constructor
30. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Programming syntax
Validation
Database normalization
Functional Requirements
31. Degree to which the system meets the specified requirements and development standards
sequence diagram
Decorator pattern
software quality
Design
32. Tasks that a system must be able to perform
SRS Documentation
SOAP
path
Functional Requirements
33. Formal document outlining a task that needs to be performed on a system
Parser
Fully- dressed use case
Maturity
conflict
34. 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
feature envy
Delegation
Data classes
35. (smell) Smell deodorant
sequence diagram
comments
Stakeholders
architectural design
36. An effective method expressed as a finite list of well- defined instructions for solving a problem.
SOP
conflict
Algorithm
SOAP
37. The things a system must do
regression testing
Elicitation
shotgun surgery
Requirements
38. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Integration testing
statement
Analysis...
WSDL
39. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
REST
Programming style
Analysis...
40. Freezing the state of the source code at a particular point
Versioning
Specification
Law of demeter
SOP
41. Constraints on the design due to external factors
Elicitation
Lazy initialization or Lazy loading (Design pattern)
Non - functional Requirements
Validation
42. (smell) A method using another class more than its own
Phase
middle man
Lifecycle
feature envy
43. An operator used to denote anonymous functions or closures.
Security testing
Algorithm
Lambda
code quality
44. Absence of lifecycle
Programming style
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Cowboy coding
Design
45. Reusable - abstract 'blocks' of design
Lambda
Specification
Design Patterns
Use case diagram
46. 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
path
Delegation
Anonymous function
Stress testing
47. Verifies that system is protected against improper penetration
Non - functional Requirements
long parameter list
intellectual property
Security testing
48. Testing tactic based on whether inputs and outputs match up for required functionality
code quality
REST
system testing
black box testing
49. The rigorousness of the tests that are able to be placed on the code
copyright
Casual use case
Maturity
data clumps
50. Each team member given set of features to work on
feature- driven development
copyright
regression testing
Cowboy coding