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. (smell) code is repeated in multiple places
comments
shotgun surgery
Lambda
duplicated code
2. Reusable - abstract 'blocks' of design
Non - functional Requirements
Versioning
Design pattern
a refactoring
3. An operator used to denote anonymous functions or closures.
Maturity
REST
Lambda
patent
4. Each possible path through the code is covered
Test- driven development
Delegation
path
data clumps
5. Developing a plan for a product - system or component. 'how' a system should perform a task
WSDL
Decorator pattern
Design
copyright
6. Figuring out what the requirements are
Maturity
Elicitation
Design pattern
intellectual property
7. Recognizable indicator that something may be wrong with code
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
code smell
Non - functional Requirements
Design patterns
8. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Software Quality
Design patterns
a refactoring
9. Formal testing against end user specifications
Validation
Acceptance testing
jquery
Closure
10. 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 envy
Programming syntax
Delegation
black box testing
11. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Programming style
Lazy initialization or Lazy loading (Design pattern)
Liskov substitution principle
branch
12. Approach to team management that splits management up into two people with separate tasks
Decorator pattern
trademark
technical managerial approach
REST
13. Ways to express the system's subsystems and their relationship
Decorator pattern
Quality metrics
architectural design
Design patterns
14. Object oriented programming; using objects to solve problems.
a refactoring
OOP
Algorithm
SRS Documentation
15. Series of phases through which software is developed
Lifecycle
Data classes
Non - functional Requirements
white box testing
16. 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
17. A computer program that divides code up into functional components
feature envy
Parser
OOP
Lexer
18. The degree to which code is free of defects
code quality
middle man
Design pattern
SRS Documentation
19. The things a system must do
Liskov substitution principle
Recovery testing
Fully- dressed use case
Requirements
20. 3rd step of requirements gathering
intellectual property
Lazy initialization or Lazy loading (Design pattern)
Specification
Stakeholders
21. One or two paragraphs of text outlining a use case
Programming syntax
Casual use case
Semantic Web
Large class
22. Small - behaviour- preserving - source- to- source transformation
Phase
Scrum (Agile software development)
a refactoring
Code Quality
23. 1st step of requirements gathering
Acceptance testing
Elicitation
Lazy initialization or Lazy loading (Design pattern)
Design
24. 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
system testing
code quality
25. 'single dot rule'
Law of demeter
shotgun surgery
Validation
Data classes
26. 4th step of requirements gathering
path
shotgun surgery
Design pattern
Validation
27. Representational State Transfer.
REST
brief use case
software quality
system testing
28. (smell) many parameters are being passed into a method
Lambda
long parameter list
Analysis...
model- driven development
29. 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
use case
Analysis...
white box testing
Delegation
30. Diagram used to show how information flows around the system
sequence diagram
model- driven development
message chain
black box testing
31. (smell) One class delegates all of its requests to another class
middle man
Phase
shotgun surgery
branch
32. How well your fulfil your requirements
Software Quality
code smell
Analysis...
Lazy initialization or Lazy loading (Design pattern)
33. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Non - functional Requirements
a refactoring
Versioning
34. A relationship between objects.
Requirements
data clumps
technical managerial approach
Association
35. Executes system in a manner that demands abnormal amounts of resources
code smell
Semantic Web
Stress testing
Large class
36. (smell) A class whose only purpose is to hold data
Integration testing
Data classes
code smell
Requirements
37. Test the run - time performance of the system
a refactoring
Performance testing
Security testing
path
38. Constraints on the design due to external factors
code quality
Refactoring
inappropriate intimacy
Non - functional Requirements
39. Each team member given set of features to work on
feature- driven development
Design Patterns
Cowboy coding
Law of demeter
40. Single step in a lifecycle
inappropriate intimacy
Integration testing
Phase
brief use case
41. Word - logo or symbol used to distinguish one organization's wares and services from another's
trademark
Security testing
a refactoring
SOP
42. Absence of lifecycle
Cowboy coding
Stakeholders
inappropriate intimacy
Recovery testing
43. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Anonymous function
Fully- dressed use case
Lexer
Parser
44. Testing that verifies that individual units of source code are working
SOP
Functional Requirements
Refactoring
unit testing
45. A design pattern that allows behaviour to be added to an existing object dynamically.
Design Patterns
inappropriate intimacy
Decorator pattern
long method
46. Derived methods should not assume more or deliver less
a refactoring
Liskov substitution principle
Casual use case
Quality metrics
47. The rigorousness of the tests that are able to be placed on the code
Lifecycle
Maturity
First- class citizen
Programming syntax
48. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Programming style
Lambda
Dijkstra's law
Constructor
49. Diagram outlining the tasks that are going to be performed by the user
intellectual property
Use case diagram
architectural design
Law of demeter
50. (smell) Making one change requires changes in multiple places
shotgun surgery
conflict
Security testing
Versioning