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. A way to automatically grade code based on heuristics
Denormalization
Quality metrics
SRS Documentation
Constructor
2. (smell) Classes using things that should be private in other classes
code smell
Law of demeter
inappropriate intimacy
REST
3. Reusable - abstract 'blocks' of design
Design Patterns
Database normalization
Large class
Quality metrics
4. The degree to which code is free of defects
code quality
OOP
brief use case
Cowboy coding
5. Reusable - abstract 'blocks' of design
Recovery testing
Design pattern
inappropriate intimacy
Maturity
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
SOP
Closure
Stakeholders
SOAP
7. Diagram used to show how information flows around the system
Quality metrics
sequence diagram
branch
Capacity testing
8. Test the run - time performance of the system
Usability testing
Constructor
Programming style
Performance testing
9. An operator used to denote anonymous functions or closures.
Lambda
Casual use case
long parameter list
Scrum (Agile software development)
10. Testing the whole system for functionality
system testing
Specification
Lazy initialization or Lazy loading (Design pattern)
data clumps
11. Freezing the state of the source code at a particular point
Casual use case
Versioning
Database normalization
Cowboy coding
12. How developed code is (testing - documentation etc)
unit testing
Maturity level
Dijkstra's law
Capacity testing
13. Executes system in a manner that demands abnormal amounts of resources
regression testing
Stress testing
inappropriate intimacy
Design Patterns
14. A powerful motivator for change
software quality
REST
Lifecycle
conflict
15. Tasks that a system must be able to perform
Functional Requirements
trademark
Lexer
Analysis...
16. One or two paragraphs of text outlining a use case
Casual use case
system testing
First- class citizen
Parser
17. (smell) method has too many statements - loops or variables
comments
Cowboy coding
long method
path
18. Testing that verifies that individual units of source code are working
unit testing
Design patterns
Lazy initialization or Lazy loading (Design pattern)
Capacity testing
19. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
Large class
feature envy
Acceptance testing
20. Single step in a lifecycle
Capacity testing
Lifecycle
a refactoring
Phase
21. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
shotgun surgery
Decorator pattern
Lambda
22. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Association
Lexer
Functional Requirements
Anonymous function
23. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
SOP
Stakeholders
technical managerial approach
Dijkstra's law
24. Comprehensive description of software's intended purpose
Anonymous function
unit testing
SRS Documentation
branch
25. Each team member given set of features to work on
Analysis...
feature- driven development
Quality metrics
Design pattern
26. 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
27. A computer program that divides code up into functional components
model- driven development
Parser
black box testing
system testing
28. Protecting the embodiment of an idea
Stress testing
Design
copyright
SOP
29. Evaluates upper limits of operational parameters
Capacity testing
regression testing
data clumps
Validation
30. The rights governing the ownership and disposition of technology
intellectual property
Database normalization
trademark
Specification
31. 2nd step of requirements gathering
Lifecycle
Analysis...
Refactoring
inappropriate intimacy
32. The things a system must do
path
Integration testing
Performance testing
Requirements
33. Approach to team management that splits management up into two people with separate tasks
comments
technical managerial approach
statement
Acceptance testing
34. 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
Decorator pattern
brief use case
intellectual property
35. 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
Use case diagram
sequence diagram
Elicitation
36. (smell) many parameters are being passed into a method
Fully- dressed use case
unit testing
long parameter list
SOP
37. A movement that promotes common formats for data.
Semantic Web
code quality
Constructor
middle man
38. (smell) A class whose only purpose is to hold data
conflict
Validation
white box testing
Data classes
39. (smell) client needs to use one object to get another and then use that one to get another
Use case diagram
sequence diagram
message chain
Casual use case
40. (smell)class with too many instance variables or too much code
Large class
patent
long method
a refactoring
41. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Cowboy coding
Lambda
system testing
42. Formal document outlining a task that needs to be performed on a system
a refactoring
Security testing
Acceptance testing
Fully- dressed use case
43. Degree to which the system meets the specified requirements and development standards
Denormalization
Association
branch
software quality
44. Formal testing against end user specifications
Phase
statement
Acceptance testing
Law of demeter
45. Techniques for composing objects to form larger structures
Design patterns
Security testing
Lazy initialization or Lazy loading (Design pattern)
Elicitation
46. 'single dot rule'
Law of demeter
jquery
SRS Documentation
OOP
47. (smell) If a set of variables are used together in multiple places
system testing
data clumps
Closure
Denormalization
48. How well your fulfil your requirements
Analysis...
Programming syntax
Software Quality
Large class
49. Contract between inventor - assignee and state giving a time and geographically limited monopoly
code quality
Software Quality
Parser
patent
50. Small - behaviour- preserving - source- to- source transformation
duplicated code
a refactoring
Recovery testing
patent