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. Word - logo or symbol used to distinguish one organization's wares and services from another's
Validation
intellectual property
Denormalization
trademark
2. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
Elicitation
Use case diagram
Database normalization
3. A relationship between objects.
Fully- dressed use case
Association
Dijkstra's law
Delegation
4. Verifies that system is protected against improper penetration
Security testing
Versioning
Decorator pattern
Lifecycle
5. Testing the whole system for functionality
branch
SOAP
system testing
Capacity testing
6. 3rd step of requirements gathering
statement
Specification
Elicitation
model- driven development
7. The things a system must do
Semantic Web
Requirements
Use case diagram
Acceptance testing
8. 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
Denormalization
inappropriate intimacy
middle man
9. Testing where modules are combined and tested as a group
software quality
Elicitation
Integration testing
Anonymous function
10. Evaluates upper limits of operational parameters
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Capacity testing
Phase
brief use case
11. Testing tactic based on whether inputs and outputs match up for required functionality
black box testing
Performance testing
Recovery testing
First- class citizen
12. 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
message chain
Lambda
middle man
Closure
13. (smell) One class delegates all of its requests to another class
middle man
Usability testing
Feasibility
path
14. The degree to which code is free of defects
code quality
Algorithm
a refactoring
Parser
15. Techniques for composing objects to form larger structures
inappropriate intimacy
WSDL
Versioning
Design patterns
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. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
regression testing
Maturity
long parameter list
18. Description of possible sequences of interactions between a user and the system.
use case
technical managerial approach
Programming syntax
jquery
19. Executes system in a manner that demands abnormal amounts of resources
Lifecycle
Stress testing
WSDL
SOP
20. Lack of errors in code - readability etc
conflict
Code Quality
duplicated code
Maturity level
21. How developed code is (testing - documentation etc)
Liskov substitution principle
Maturity level
Maturity
software quality
22. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Liskov substitution principle
patent
Association
Database normalization
23. Reusable - abstract 'blocks' of design
Algorithm
Programming syntax
Acceptance testing
Design Patterns
24. Test cases made -> code compiles -> make code pass
sequence diagram
Test- driven development
Dijkstra's law
branch
25. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Large class
Maturity level
black box testing
regression testing
26. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Maturity level
REST
conflict
Lazy initialization or Lazy loading (Design pattern)
27. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Security testing
Anonymous function
long parameter list
Lambda
28. Recognizable indicator that something may be wrong with code
shotgun surgery
Programming style
code smell
Stress testing
29. Object oriented programming; using objects to solve problems.
OOP
patent
path
Acceptance testing
30. Force software to fail in order to see how it recovers
Recovery testing
Casual use case
Algorithm
architectural design
31. Tasks that a system must be able to perform
SOAP
Code Quality
Functional Requirements
Acceptance testing
32. Constraints on the design due to external factors
shotgun surgery
Analysis...
Non - functional Requirements
Acceptance testing
33. 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
34. Each line of code is covered once
feature- driven development
statement
Lexer
Denormalization
35. Approach to team management that splits management up into two people with separate tasks
shotgun surgery
Scrum (Agile software development)
technical managerial approach
duplicated code
36. Each team member given set of features to work on
Design patterns
Dijkstra's law
feature- driven development
Constructor
37. Developing a plan for a product - system or component. 'how' a system should perform a task
trademark
Stress testing
conflict
Design
38. (smell) If a set of variables are used together in multiple places
Fully- dressed use case
data clumps
REST
Denormalization
39. A powerful motivator for change
conflict
Refactoring
Security testing
long parameter list
40. Small - behaviour- preserving - source- to- source transformation
Scrum (Agile software development)
trademark
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
a refactoring
41. 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.
trademark
Cowboy coding
First- class citizen
inappropriate intimacy
42. 1st step of requirements gathering
WSDL
Casual use case
Elicitation
First- class citizen
43. A design pattern that allows behaviour to be added to an existing object dynamically.
Lazy initialization or Lazy loading (Design pattern)
Usability testing
Versioning
Decorator pattern
44. Comprehensive description of software's intended purpose
Requirements
Code Quality
SRS Documentation
Algorithm
45. Iterative - incremental framework for project management.
trademark
shotgun surgery
Scrum (Agile software development)
feature envy
46. (smell) A class whose only purpose is to hold data
Data classes
path
Maturity level
SRS Documentation
47. Single step in a lifecycle
shotgun surgery
Use case diagram
Phase
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
48. An effective method expressed as a finite list of well- defined instructions for solving a problem.
white box testing
brief use case
Feasibility
Algorithm
49. One or two paragraphs of text outlining a use case
Scrum (Agile software development)
Stress testing
Casual use case
software quality
50. Formal testing against end user specifications
Decorator pattern
Acceptance testing
copyright
Integration testing