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 method that initializes a newly instantiated object
Semantic Web
Integration testing
Constructor
software quality
2. A relationship between objects.
middle man
Association
Lazy initialization or Lazy loading (Design pattern)
Requirements
3. Small - behaviour- preserving - source- to- source transformation
Quality metrics
Test- driven development
a refactoring
use case
4. 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.
Analysis...
First- class citizen
Programming syntax
Acceptance testing
5. Derived methods should not assume more or deliver less
Security testing
Liskov substitution principle
feature- driven development
Lazy initialization or Lazy loading (Design pattern)
6. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Design patterns
SOAP
feature- driven development
Code Quality
7. Degree to which the system meets the specified requirements and development standards
Recovery testing
model- driven development
software quality
Database normalization
8. The degree to which code is free of defects
Denormalization
Association
Scrum (Agile software development)
code quality
9. Absence of lifecycle
Security testing
path
brief use case
Cowboy coding
10. Approach to team management that splits management up into two people with separate tasks
use case
technical managerial approach
Decorator pattern
Denormalization
11. Test cases made -> code compiles -> make code pass
Security testing
First- class citizen
patent
Test- driven development
12. (smell) Making one change requires changes in multiple places
shotgun surgery
SOAP
Anonymous function
Design pattern
13. Figuring out what the requirements are
Performance testing
Elicitation
OOP
system testing
14. Force software to fail in order to see how it recovers
Fully- dressed use case
a refactoring
shotgun surgery
Recovery testing
15. Testing where modules are combined and tested as a group
Integration testing
patent
technical managerial approach
jquery
16. The rigorousness of the tests that are able to be placed on the code
feature envy
path
Maturity
trademark
17. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Validation
code smell
jquery
Design pattern
18. 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
19. A design pattern that allows behaviour to be added to an existing object dynamically.
comments
software quality
Denormalization
Decorator pattern
20. A way to automatically grade code based on heuristics
patent
First- class citizen
Quality metrics
Dijkstra's law
21. Reusable - abstract 'blocks' of design
Design Patterns
Lifecycle
Software Quality
copyright
22. One or two paragraphs of text outlining a use case
Programming syntax
Casual use case
Software Quality
Elicitation
23. (smell) Classes using things that should be private in other classes
jquery
conflict
Non - functional Requirements
inappropriate intimacy
24. (smell) Smell deodorant
Versioning
Design Patterns
Feasibility
comments
25. 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.
Feasibility
intellectual property
OOP
Lifecycle
26. Constraints on the design due to external factors
feature envy
message chain
Test- driven development
Non - functional Requirements
27. 2nd step of requirements gathering
Analysis...
Law of demeter
Specification
Acceptance testing
28. 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
SOAP
Programming style
branch
Delegation
29. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
feature- driven development
Delegation
Lazy initialization or Lazy loading (Design pattern)
Casual use case
30. Formal testing against end user specifications
Refactoring
Acceptance testing
system testing
Lambda
31. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Performance testing
Lexer
OOP
WSDL
32. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Stress testing
Recovery testing
Elicitation
33. Models ->code work is done to keep models in sync with code
Usability testing
comments
Requirements
model- driven development
34. Diagram used to show how information flows around the system
model- driven development
sequence diagram
Design patterns
system testing
35. (smell)class with too many instance variables or too much code
Software Quality
WSDL
Large class
patent
36. A computer program that divides code up into functional components
Parser
data clumps
middle man
REST
37. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Requirements
Test- driven development
SOP
38. Each team member given set of features to work on
feature- driven development
system testing
white box testing
inappropriate intimacy
39. Lack of errors in code - readability etc
Phase
Lexer
Algorithm
Code Quality
40. Each condition is covered twice (true - false)
branch
Maturity level
Recovery testing
Lexer
41. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Analysis...
Validation
OOP
WSDL
42. 4th step of requirements gathering
Performance testing
WSDL
technical managerial approach
Validation
43. Series of phases through which software is developed
Lifecycle
Feasibility
sequence diagram
Association
44. Testing that verifies that individual units of source code are working
unit testing
comments
Validation
Delegation
45. Each line of code is covered once
Delegation
statement
jquery
use case
46. Tasks that a system must be able to perform
intellectual property
white box testing
data clumps
Functional Requirements
47. 'single dot rule'
Law of demeter
Design Patterns
feature- driven development
OOP
48. (smell) A method using another class more than its own
Programming style
Integration testing
data clumps
feature envy
49. Reusable - abstract 'blocks' of design
Design pattern
Scrum (Agile software development)
path
SOAP
50. Testing the whole system for functionality
system testing
Database normalization
Use case diagram
Lexer