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. The things a system must do
Cowboy coding
data clumps
unit testing
Requirements
2. 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.
REST
jquery
First- class citizen
Database normalization
3. Reusable - abstract 'blocks' of design
Database normalization
Design pattern
Security testing
Anonymous function
4. A powerful motivator for change
inappropriate intimacy
system testing
conflict
Lexer
5. The rigorousness of the tests that are able to be placed on the code
Maturity
Casual use case
Integration testing
Capacity testing
6. 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
software quality
Constructor
Programming style
Closure
7. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Semantic Web
Large class
Software Quality
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
8. Constraints on the design due to external factors
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
SOP
software quality
Non - functional Requirements
9. Absence of lifecycle
Quality metrics
Acceptance testing
Anonymous function
Cowboy coding
10. (smell) If a set of variables are used together in multiple places
Dijkstra's law
feature- driven development
data clumps
Versioning
11. Derived methods should not assume more or deliver less
Data classes
trademark
comments
Liskov substitution principle
12. Word - logo or symbol used to distinguish one organization's wares and services from another's
Code Quality
trademark
Dijkstra's law
Closure
13. Lack of errors in code - readability etc
Code Quality
message chain
Capacity testing
statement
14. Reusable - abstract 'blocks' of design
Design Patterns
SRS Documentation
Code Quality
black box testing
15. 3rd step of requirements gathering
Algorithm
Specification
Anonymous function
code smell
16. Each line of code is covered once
brief use case
statement
feature- driven development
Security testing
17. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
Design
Closure
Validation
18. Each possible path through the code is covered
Stress testing
patent
Software Quality
path
19. Single step in a lifecycle
SOP
Requirements
intellectual property
Phase
20. A way to automatically grade code based on heuristics
Quality metrics
jquery
brief use case
SRS Documentation
21. Representational State Transfer.
REST
Functional Requirements
Algorithm
First- class citizen
22. 1st step of requirements gathering
shotgun surgery
Elicitation
Design patterns
data clumps
23. A relationship between objects.
copyright
data clumps
code smell
Association
24. (smell) A method using another class more than its own
Usability testing
Design patterns
Parser
feature envy
25. An operator used to denote anonymous functions or closures.
Data classes
Lambda
patent
sequence diagram
26. Evaluates upper limits of operational parameters
Stakeholders
conflict
Functional Requirements
Capacity testing
27. Diagram used to show how information flows around the system
Dijkstra's law
sequence diagram
Capacity testing
inappropriate intimacy
28. (smell) code is repeated in multiple places
Feasibility
a refactoring
duplicated code
Phase
29. 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
30. Techniques for composing objects to form larger structures
Stress testing
Design patterns
SOAP
code quality
31. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
patent
regression testing
inappropriate intimacy
REST
32. A movement that promotes common formats for data.
Specification
Design Patterns
Semantic Web
data clumps
33. (smell) method has too many statements - loops or variables
Quality metrics
a refactoring
long method
Versioning
34. Testing tactic that looks at all ways that data can flow through the code
white box testing
branch
REST
Design Patterns
35. 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
36. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Decorator pattern
SOP
feature envy
SOAP
37. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
branch
long parameter list
Design Patterns
38. The rights governing the ownership and disposition of technology
Analysis...
middle man
intellectual property
white box testing
39. 2nd step of requirements gathering
long parameter list
Stress testing
Analysis...
Phase
40. One or two paragraphs of text outlining a use case
Feasibility
Anonymous function
Casual use case
SOAP
41. Force software to fail in order to see how it recovers
Lazy initialization or Lazy loading (Design pattern)
Recovery testing
Database normalization
Casual use case
42. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Validation
Usability testing
Elicitation
Database normalization
43. Recognizable indicator that something may be wrong with code
Design Patterns
Anonymous function
sequence diagram
code smell
44. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Acceptance testing
Lexer
path
45. 'single dot rule'
Anonymous function
Large class
Law of demeter
Elicitation
46. Iterative - incremental framework for project management.
Data classes
Scrum (Agile software development)
Recovery testing
Liskov substitution principle
47. 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
black box testing
Delegation
Scrum (Agile software development)
Denormalization
48. (smell) Classes using things that should be private in other classes
inappropriate intimacy
Elicitation
SOP
white box testing
49. Developing a plan for a product - system or component. 'how' a system should perform a task
Design
intellectual property
SRS Documentation
Maturity level
50. Freezing the state of the source code at a particular point
Versioning
Integration testing
Code Quality
Programming style