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. Object oriented programming; using objects to solve problems.
code quality
Lambda
OOP
SOAP
2. Word - logo or symbol used to distinguish one organization's wares and services from another's
Database normalization
Fully- dressed use case
trademark
Stakeholders
3. A movement that promotes common formats for data.
branch
Constructor
feature- driven development
Semantic Web
4. Series of phases through which software is developed
Acceptance testing
Design Patterns
software quality
Lifecycle
5. Formal document outlining a task that needs to be performed on a system
Validation
Fully- dressed use case
long parameter list
branch
6. (smell) A method using another class more than its own
feature envy
Elicitation
Design
Elicitation
7. A design pattern that allows behaviour to be added to an existing object dynamically.
Stress testing
architectural design
Decorator pattern
First- class citizen
8. 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
9. A method that initializes a newly instantiated object
Validation
Liskov substitution principle
Data classes
Constructor
10. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
data clumps
Database normalization
Phase
Code Quality
11. Freezing the state of the source code at a particular point
code quality
Versioning
Design
Design Patterns
12. One or two paragraphs of text outlining a use case
Association
Design patterns
Casual use case
technical managerial approach
13. (smell) code is repeated in multiple places
duplicated code
Acceptance testing
Design Patterns
brief use case
14. An operator used to denote anonymous functions or closures.
Data classes
Lambda
Quality metrics
Casual use case
15. A computer program that divides code up into functional components
Parser
Integration testing
Closure
Code Quality
16. A way to automatically grade code based on heuristics
white box testing
Quality metrics
Non - functional Requirements
SOAP
17. Testing tactic that looks at all ways that data can flow through the code
Design patterns
comments
white box testing
copyright
18. 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.
path
Closure
comments
Feasibility
19. Single step in a lifecycle
Security testing
code quality
Phase
brief use case
20. 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
21. Testing the whole system for functionality
Security testing
Test- driven development
Anonymous function
system testing
22. The things a system must do
Requirements
conflict
Decorator pattern
Performance testing
23. 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.
Lazy initialization or Lazy loading (Design pattern)
shotgun surgery
First- class citizen
branch
24. Techniques for composing objects to form larger structures
Denormalization
Design patterns
Analysis...
Constructor
25. Reusable - abstract 'blocks' of design
intellectual property
duplicated code
Design Patterns
white box testing
26. 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
Elicitation
duplicated code
Denormalization
Delegation
27. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Law of demeter
Cowboy coding
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
28. Executes system in a manner that demands abnormal amounts of resources
Lifecycle
Capacity testing
Stress testing
long method
29. Comprehensive description of software's intended purpose
Design Patterns
statement
SRS Documentation
intellectual property
30. Verifies that system is protected against improper penetration
Refactoring
Security testing
statement
architectural design
31. (smell) Making one change requires changes in multiple places
shotgun surgery
use case
Code Quality
code smell
32. Test cases made -> code compiles -> make code pass
SOP
Constructor
code smell
Test- driven development
33. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Quality metrics
Programming style
SOAP
Scrum (Agile software development)
34. Degree to which the system meets the specified requirements and development standards
Acceptance testing
Recovery testing
software quality
Algorithm
35. (smell) Classes using things that should be private in other classes
technical managerial approach
Design Patterns
inappropriate intimacy
Integration testing
36. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Stress testing
Stakeholders
Refactoring
37. (smell) Smell deodorant
statement
comments
Scrum (Agile software development)
Decorator pattern
38. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
Algorithm
Database normalization
OOP
39. Constraints on the design due to external factors
Design
Non - functional Requirements
Lexer
trademark
40. 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
branch
Maturity
Database normalization
41. Improve the internal design and implementation of code without affecting external behavior
Lexer
statement
Programming syntax
Refactoring
42. 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
Closure
Scrum (Agile software development)
Maturity level
Liskov substitution principle
43. (smell) method has too many statements - loops or variables
Test- driven development
long method
Elicitation
middle man
44. 3rd step of requirements gathering
Performance testing
Specification
SRS Documentation
Lambda
45. (smell) One class delegates all of its requests to another class
Dijkstra's law
Use case diagram
middle man
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
46. Formal testing against end user specifications
Acceptance testing
Lifecycle
Versioning
regression testing
47. A few sentences summarizing a use case
Lazy initialization or Lazy loading (Design pattern)
brief use case
Semantic Web
Large class
48. Description of possible sequences of interactions between a user and the system.
conflict
use case
Performance testing
architectural design
49. A powerful motivator for change
conflict
SRS Documentation
Decorator pattern
Refactoring
50. Ways to express the system's subsystems and their relationship
Stress testing
Refactoring
architectural design
REST