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 process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Capacity testing
Database normalization
Scrum (Agile software development)
duplicated code
2. Representational State Transfer.
REST
Versioning
Large class
First- class citizen
3. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
system testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Anonymous function
patent
4. Testing tactic that looks at all ways that data can flow through the code
SRS Documentation
code smell
white box testing
Security testing
5. (smell) Making one change requires changes in multiple places
WSDL
shotgun surgery
Requirements
system testing
6. Series of phases through which software is developed
Semantic Web
Lifecycle
Maturity level
copyright
7. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
comments
path
feature- driven development
8. Test whether or not tasks can be accomplished efficiently by all levels of users
Non - functional Requirements
Usability testing
Code Quality
Data classes
9. Recognizable indicator that something may be wrong with code
code smell
Maturity level
Feasibility
Data classes
10. Protecting the embodiment of an idea
Law of demeter
white box testing
Refactoring
copyright
11. (smell) Classes using things that should be private in other classes
Database normalization
Design Patterns
inappropriate intimacy
Association
12. Reusable - abstract 'blocks' of design
Functional Requirements
Semantic Web
Design Patterns
Database normalization
13. A computer program that divides code up into functional components
OOP
comments
Quality metrics
Parser
14. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Lambda
sequence diagram
message chain
regression testing
15. Diagram used to show how information flows around the system
sequence diagram
model- driven development
a refactoring
branch
16. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Denormalization
trademark
Refactoring
Algorithm
17. Constraints on the design due to external factors
Casual use case
Elicitation
Non - functional Requirements
technical managerial approach
18. (smell) If a set of variables are used together in multiple places
data clumps
unit testing
Dijkstra's law
WSDL
19. 4th step of requirements gathering
Non - functional Requirements
architectural design
Code Quality
Validation
20. The rights governing the ownership and disposition of technology
unit testing
sequence diagram
intellectual property
shotgun surgery
21. 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
22. Single step in a lifecycle
Lifecycle
Phase
Quality metrics
a refactoring
23. Each line of code is covered once
statement
unit testing
REST
Analysis...
24. 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.
feature- driven development
use case
Delegation
Programming syntax
25. Testing tactic based on whether inputs and outputs match up for required functionality
shotgun surgery
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Closure
black box testing
26. Comprehensive description of software's intended purpose
trademark
Versioning
SRS Documentation
Anonymous function
27. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
branch
code quality
middle man
Anonymous function
28. 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
First- class citizen
Functional Requirements
Closure
inappropriate intimacy
29. The degree to which code is free of defects
long parameter list
a refactoring
statement
code quality
30. Small - behaviour- preserving - source- to- source transformation
a refactoring
SRS Documentation
Parser
Stress testing
31. Force software to fail in order to see how it recovers
Feasibility
Recovery testing
Security testing
Elicitation
32. Test cases made -> code compiles -> make code pass
Closure
Lambda
Test- driven development
unit testing
33. 1st step of requirements gathering
Analysis...
trademark
Elicitation
Phase
34. Developing a plan for a product - system or component. 'how' a system should perform a task
sequence diagram
Design
inappropriate intimacy
Closure
35. Verifies that system is protected against improper penetration
use case
Elicitation
model- driven development
Security testing
36. Testing where modules are combined and tested as a group
Lazy initialization or Lazy loading (Design pattern)
Design pattern
Use case diagram
Integration testing
37. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
model- driven development
intellectual property
WSDL
REST
38. Approach to team management that splits management up into two people with separate tasks
Programming syntax
technical managerial approach
Large class
Maturity
39. (smell) client needs to use one object to get another and then use that one to get another
Code Quality
message chain
Acceptance testing
Maturity
40. Models ->code work is done to keep models in sync with code
Closure
model- driven development
Lexer
Performance testing
41. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Fully- dressed use case
Stress testing
jquery
SOP
42. Formal testing against end user specifications
SOP
Delegation
Design
Acceptance testing
43. Derived methods should not assume more or deliver less
Recovery testing
Stakeholders
Acceptance testing
Liskov substitution principle
44. (smell) A class whose only purpose is to hold data
Data classes
middle man
Association
Design pattern
45. 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
46. Diagram outlining the tasks that are going to be performed by the user
Large class
Use case diagram
white box testing
Delegation
47. Description of possible sequences of interactions between a user and the system.
white box testing
a refactoring
patent
use case
48. Freezing the state of the source code at a particular point
Versioning
Scrum (Agile software development)
Design Patterns
feature- driven development
49. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Stakeholders
SOAP
intellectual property
SOP
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.
Specification
Large class
SRS Documentation
Programming style