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. 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
2. Test whether or not tasks can be accomplished efficiently by all levels of users
data clumps
Usability testing
system testing
middle man
3. (smell) A class whose only purpose is to hold data
Closure
branch
Data classes
Database normalization
4. Formal testing against end user specifications
a refactoring
Elicitation
Denormalization
Acceptance testing
5. The rigorousness of the tests that are able to be placed on the code
Software Quality
Law of demeter
Maturity
Phase
6. 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.
Large class
code quality
Programming syntax
system testing
7. Testing where modules are combined and tested as a group
Law of demeter
Denormalization
REST
Integration testing
8. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Acceptance testing
message chain
WSDL
code quality
9. Series of phases through which software is developed
Maturity
inappropriate intimacy
Lifecycle
Algorithm
10. (smell) Classes using things that should be private in other classes
Performance testing
use case
Programming syntax
inappropriate intimacy
11. Verifies that system is protected against improper penetration
Stress testing
Security testing
Liskov substitution principle
regression testing
12. Small - behaviour- preserving - source- to- source transformation
Software Quality
Feasibility
a refactoring
technical managerial approach
13. Lack of errors in code - readability etc
Design Patterns
Code Quality
Stakeholders
unit testing
14. Description of possible sequences of interactions between a user and the system.
SOP
OOP
Requirements
use case
15. A design pattern that allows behaviour to be added to an existing object dynamically.
software quality
Lifecycle
Decorator pattern
Analysis...
16. Approach to team management that splits management up into two people with separate tasks
middle man
technical managerial approach
Code Quality
Usability testing
17. (smell) A method using another class more than its own
sequence diagram
Casual use case
Dijkstra's law
feature envy
18. (smell)class with too many instance variables or too much code
Stress testing
Large class
Denormalization
Fully- dressed use case
19. The rights governing the ownership and disposition of technology
patent
Test- driven development
branch
intellectual property
20. The things a system must do
Requirements
brief use case
feature- driven development
Acceptance testing
21. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
WSDL
Anonymous function
duplicated code
patent
22. (smell) method has too many statements - loops or variables
long method
black box testing
Refactoring
Functional Requirements
23. Techniques for composing objects to form larger structures
system testing
Design patterns
code quality
Design
24. Single step in a lifecycle
Versioning
Phase
trademark
path
25. An operator used to denote anonymous functions or closures.
Lambda
code quality
Specification
Phase
26. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Programming style
Cowboy coding
Algorithm
SRS Documentation
27. (smell) many parameters are being passed into a method
trademark
Analysis...
Decorator pattern
long parameter list
28. 'single dot rule'
Dijkstra's law
Anonymous function
Law of demeter
Constructor
29. 1st step of requirements gathering
Algorithm
Design pattern
Elicitation
Software Quality
30. Force software to fail in order to see how it recovers
Recovery testing
Design pattern
Stakeholders
Software Quality
31. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Decorator pattern
Lexer
Test- driven development
Phase
32. Test cases made -> code compiles -> make code pass
Test- driven development
feature envy
Delegation
unit testing
33. People who care about the outcome
Anonymous function
Stress testing
Stakeholders
Delegation
34. Freezing the state of the source code at a particular point
Maturity
patent
conflict
Versioning
35. A way to automatically grade code based on heuristics
feature- driven development
use case
Quality metrics
conflict
36. 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
37. Recognizable indicator that something may be wrong with code
feature- driven development
Parser
code smell
Denormalization
38. A relationship between objects.
Association
trademark
Feasibility
SRS Documentation
39. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
path
Association
Phase
40. Reusable - abstract 'blocks' of design
WSDL
Denormalization
Design Patterns
Versioning
41. The degree to which code is free of defects
use case
code quality
Software Quality
brief use case
42. Improve the internal design and implementation of code without affecting external behavior
Refactoring
Liskov substitution principle
duplicated code
OOP
43. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Large class
Database normalization
Requirements
Law of demeter
44. Testing tactic that looks at all ways that data can flow through the code
Validation
white box testing
Performance testing
code quality
45. 3rd step of requirements gathering
sequence diagram
Specification
message chain
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
46. Test the run - time performance of the system
Integration testing
Performance testing
long method
architectural design
47. 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
inappropriate intimacy
shotgun surgery
Delegation
Data classes
48. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
trademark
Software Quality
WSDL
49. A few sentences summarizing a use case
brief use case
Fully- dressed use case
conflict
Use case diagram
50. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
OOP
model- driven development
Phase