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. Word - logo or symbol used to distinguish one organization's wares and services from another's
trademark
Non - functional Requirements
Algorithm
Fully- dressed use case
2. A design pattern that allows behaviour to be added to an existing object dynamically.
inappropriate intimacy
Decorator pattern
Security testing
WSDL
3. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
jquery
technical managerial approach
Lazy initialization or Lazy loading (Design pattern)
Programming style
4. 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.
Requirements
OOP
Programming syntax
black box testing
5. Reusable - abstract 'blocks' of design
branch
shotgun surgery
Design Patterns
software quality
6. Verifies that system is protected against improper penetration
Security testing
patent
SOP
a refactoring
7. (smell) Making one change requires changes in multiple places
statement
Design pattern
shotgun surgery
Design patterns
8. Tasks that a system must be able to perform
Functional Requirements
Recovery testing
Decorator pattern
REST
9. People who care about the outcome
Integration testing
Validation
Maturity level
Stakeholders
10. Reusable - abstract 'blocks' of design
branch
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Data classes
Design pattern
11. Lack of errors in code - readability etc
Code Quality
Dijkstra's law
Cowboy coding
architectural design
12. Evaluates upper limits of operational parameters
Capacity testing
Lambda
patent
Recovery testing
13. A computer program that divides code up into functional components
Casual use case
Acceptance testing
Parser
Maturity level
14. (smell) method has too many statements - loops or variables
long method
Software Quality
Functional Requirements
sequence diagram
15. Comprehensive description of software's intended purpose
white box testing
SRS Documentation
SOP
unit testing
16. Small - behaviour- preserving - source- to- source transformation
Lambda
Liskov substitution principle
Recovery testing
a refactoring
17. Constraints on the design due to external factors
Stakeholders
Non - functional Requirements
patent
Constructor
18. Diagram used to show how information flows around the system
sequence diagram
Maturity level
Constructor
Programming syntax
19. Iterative - incremental framework for project management.
Scrum (Agile software development)
technical managerial approach
code quality
branch
20. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Acceptance testing
Algorithm
Data classes
Functional Requirements
21. 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
software quality
Integration testing
Code Quality
Delegation
22. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
duplicated code
Anonymous function
Closure
Delegation
23. Force software to fail in order to see how it recovers
Recovery testing
software quality
system testing
unit testing
24. The degree to which code is free of defects
code quality
REST
SRS Documentation
Design patterns
25. 'single dot rule'
Non - functional Requirements
Law of demeter
Maturity level
Lambda
26. Testing tactic that looks at all ways that data can flow through the code
REST
white box testing
Lazy initialization or Lazy loading (Design pattern)
sequence diagram
27. 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.
Lambda
patent
First- class citizen
Lazy initialization or Lazy loading (Design pattern)
28. Test the run - time performance of the system
Recovery testing
Large class
Performance testing
Feasibility
29. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
long method
SOP
message chain
Specification
30. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
Decorator pattern
Performance testing
Lambda
31. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
SOP
brief use case
black box testing
32. (smell) Smell deodorant
a refactoring
Large class
comments
Lexer
33. How developed code is (testing - documentation etc)
Lambda
Maturity level
branch
Scrum (Agile software development)
34. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Large class
patent
system testing
long method
35. Testing the whole system for functionality
REST
model- driven development
system testing
Design
36. 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
37. (smell) code is repeated in multiple places
unit testing
Constructor
Design pattern
duplicated code
38. Series of phases through which software is developed
Programming syntax
Lambda
model- driven development
Lifecycle
39. The things a system must do
Database normalization
Decorator pattern
Requirements
Delegation
40. Protecting the embodiment of an idea
Semantic Web
long method
Requirements
copyright
41. 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
42. (smell) If a set of variables are used together in multiple places
data clumps
Elicitation
Constructor
Maturity level
43. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Decorator pattern
software quality
Database normalization
a refactoring
44. Executes system in a manner that demands abnormal amounts of resources
Design
Stress testing
Requirements
Cowboy coding
45. (smell) A method using another class more than its own
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
feature envy
path
Requirements
46. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
SRS Documentation
regression testing
Casual use case
Algorithm
47. Representational State Transfer.
REST
Lifecycle
long parameter list
WSDL
48. Formal testing against end user specifications
inappropriate intimacy
conflict
Acceptance testing
Non - functional Requirements
49. Diagram outlining the tasks that are going to be performed by the user
SOP
Feasibility
Use case diagram
WSDL
50. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
path
Programming style
Integration testing
Lambda