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. Test the run - time performance of the system
Validation
Performance testing
patent
Refactoring
2. Derived methods should not assume more or deliver less
jquery
Liskov substitution principle
path
Usability testing
3. Testing that verifies that individual units of source code are working
unit testing
a refactoring
First- class citizen
path
4. Protecting the embodiment of an idea
copyright
white box testing
Performance testing
Decorator pattern
5. (smell) Smell deodorant
comments
copyright
First- class citizen
black box testing
6. (smell) method has too many statements - loops or variables
long method
Anonymous function
Dijkstra's law
patent
7. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Use case diagram
Specification
Programming style
Lazy initialization or Lazy loading (Design pattern)
8. (smell) code is repeated in multiple places
intellectual property
Stakeholders
WSDL
duplicated code
9. (smell) A class whose only purpose is to hold data
Liskov substitution principle
Data classes
unit testing
long parameter list
10. One or two paragraphs of text outlining a use case
Casual use case
conflict
Capacity testing
Dijkstra's law
11. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
conflict
Database normalization
code smell
12. Test whether or not tasks can be accomplished efficiently by all levels of users
feature envy
Decorator pattern
patent
Usability testing
13. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
WSDL
intellectual property
Elicitation
Denormalization
14. (smell) One class delegates all of its requests to another class
statement
black box testing
middle man
Dijkstra's law
15. Recognizable indicator that something may be wrong with code
code smell
a refactoring
Design pattern
use case
16. Comprehensive description of software's intended purpose
Stress testing
code smell
SRS Documentation
Lexer
17. The things a system must do
Fully- dressed use case
Recovery testing
Requirements
Anonymous function
18. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
code smell
brief use case
Lazy initialization or Lazy loading (Design pattern)
Cowboy coding
19. (smell)class with too many instance variables or too much code
Software Quality
Stress testing
Large class
Delegation
20. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
Acceptance testing
Recovery testing
copyright
21. Diagram used to show how information flows around the system
use case
sequence diagram
Database normalization
path
22. A way to automatically grade code based on heuristics
patent
Quality metrics
Large class
middle man
23. Each team member given set of features to work on
Semantic Web
Constructor
unit testing
feature- driven development
24. Evaluates upper limits of operational parameters
Database normalization
feature- driven development
Stress testing
Capacity testing
25. Each possible path through the code is covered
path
Design pattern
intellectual property
Anonymous function
26. Force software to fail in order to see how it recovers
Non - functional Requirements
Code Quality
data clumps
Recovery testing
27. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Requirements
Test- driven development
patent
Software Quality
28. 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
Performance testing
branch
Software Quality
29. 1st step of requirements gathering
REST
Phase
Elicitation
Design patterns
30. 2nd step of requirements gathering
Data classes
Refactoring
Phase
Analysis...
31. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Parser
SOAP
copyright
Anonymous function
32. An effective method expressed as a finite list of well- defined instructions for solving a problem.
copyright
Algorithm
Maturity
intellectual property
33. A few sentences summarizing a use case
Anonymous function
Elicitation
white box testing
brief use case
34. A design pattern that allows behaviour to be added to an existing object dynamically.
Liskov substitution principle
Refactoring
Decorator pattern
trademark
35. The rights governing the ownership and disposition of technology
Parser
Phase
intellectual property
SRS Documentation
36. Ways to express the system's subsystems and their relationship
Association
duplicated code
architectural design
Phase
37. The rigorousness of the tests that are able to be placed on the code
Large class
Maturity
intellectual property
duplicated code
38. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
middle man
statement
REST
Anonymous function
39. Iterative - incremental framework for project management.
Scrum (Agile software development)
system testing
unit testing
Lambda
40. Representational State Transfer.
Liskov substitution principle
Stress testing
model- driven development
REST
41. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.
Semantic Web
Stakeholders
Functional Requirements
Feasibility
42. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
comments
Design patterns
Design pattern
43. Testing the whole system for functionality
WSDL
system testing
Elicitation
Lexer
44. A computer program that divides code up into functional components
Integration testing
path
Denormalization
Parser
45. A method that initializes a newly instantiated object
SOP
Feasibility
Constructor
Capacity testing
46. 4th step of requirements gathering
Validation
Anonymous function
Usability testing
sequence diagram
47. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
data clumps
unit testing
jquery
Anonymous function
48. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
SOP
path
Security testing
Elicitation
49. Formal testing against end user specifications
Lifecycle
regression testing
Acceptance testing
Semantic Web
50. Verifies that system is protected against improper penetration
Programming syntax
Elicitation
Security testing
inappropriate intimacy