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. Each condition is covered twice (true - false)
Elicitation
Software Quality
trademark
branch
2. (smell) If a set of variables are used together in multiple places
data clumps
Fully- dressed use case
Feasibility
brief use case
3. Executes system in a manner that demands abnormal amounts of resources
architectural design
patent
Association
Stress testing
4. Absence of lifecycle
Algorithm
Cowboy coding
Design pattern
software quality
5. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
model- driven development
Phase
Usability testing
Lazy initialization or Lazy loading (Design pattern)
6. Reusable - abstract 'blocks' of design
Analysis...
code quality
Delegation
Design Patterns
7. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Algorithm
brief use case
Association
WSDL
8. 3rd step of requirements gathering
Parser
Specification
OOP
copyright
9. Figuring out what the requirements are
Use case diagram
Elicitation
Security testing
Law of demeter
10. An operator used to denote anonymous functions or closures.
Lambda
SRS Documentation
system testing
software quality
11. A computer program that divides code up into functional components
Programming style
Parser
Lazy initialization or Lazy loading (Design pattern)
Maturity level
12. Derived methods should not assume more or deliver less
middle man
Stakeholders
message chain
Liskov substitution principle
13. Each team member given set of features to work on
Feasibility
feature- driven development
Semantic Web
long parameter list
14. Approach to team management that splits management up into two people with separate tasks
branch
Decorator pattern
technical managerial approach
a refactoring
15. Ways to express the system's subsystems and their relationship
architectural design
Lambda
Design patterns
Fully- dressed use case
16. Formal testing against end user specifications
sequence diagram
Scrum (Agile software development)
Acceptance testing
Parser
17. Force software to fail in order to see how it recovers
Recovery testing
message chain
feature envy
a refactoring
18. Test cases made -> code compiles -> make code pass
Test- driven development
Recovery testing
Acceptance testing
Quality metrics
19. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
OOP
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Code Quality
20. (smell) method has too many statements - loops or variables
Constructor
white box testing
long method
Law of demeter
21. One or two paragraphs of text outlining a use case
Casual use case
system testing
duplicated code
long method
22. 'single dot rule'
sequence diagram
Dijkstra's law
Law of demeter
Versioning
23. 1st step of requirements gathering
code smell
Quality metrics
Elicitation
middle man
24. Testing the whole system for functionality
Versioning
Programming style
Delegation
system testing
25. Small - behaviour- preserving - source- to- source transformation
Cowboy coding
Quality metrics
a refactoring
Non - functional Requirements
26. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Programming syntax
Functional Requirements
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
long parameter list
27. A method that initializes a newly instantiated object
Usability testing
Phase
Constructor
intellectual property
28. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
Lifecycle
Recovery testing
Anonymous function
29. Testing that verifies that individual units of source code are working
Algorithm
Validation
a refactoring
unit testing
30. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
OOP
Feasibility
SOAP
31. Evaluates upper limits of operational parameters
Capacity testing
Semantic Web
architectural design
Anonymous function
32. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
Law of demeter
Stakeholders
Lexer
33. (smell)class with too many instance variables or too much code
Feasibility
Large class
Security testing
Stress testing
34. How well your fulfil your requirements
Acceptance testing
Test- driven development
white box testing
Software Quality
35. Testing where modules are combined and tested as a group
white box testing
Design pattern
Law of demeter
Integration testing
36. A relationship between objects.
Association
Recovery testing
technical managerial approach
a refactoring
37. Verifies that system is protected against improper penetration
patent
Lifecycle
SOP
Security testing
38. Models ->code work is done to keep models in sync with code
intellectual property
model- driven development
Scrum (Agile software development)
Delegation
39. Series of phases through which software is developed
REST
code smell
Lifecycle
system testing
40. (smell) A method using another class more than its own
technical managerial approach
model- driven development
WSDL
feature envy
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.
First- class citizen
conflict
software quality
Integration testing
42. The rigorousness of the tests that are able to be placed on the code
Maturity
Decorator pattern
Use case diagram
long parameter list
43. 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
44. 2nd step of requirements gathering
Analysis...
duplicated code
Quality metrics
a refactoring
45. Constraints on the design due to external factors
Non - functional Requirements
REST
path
SRS Documentation
46. Recognizable indicator that something may be wrong with code
white box testing
Design Patterns
Constructor
code smell
47. 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
48. Degree to which the system meets the specified requirements and development standards
Semantic Web
path
software quality
Acceptance testing
49. Object oriented programming; using objects to solve problems.
Use case diagram
Functional Requirements
OOP
Lazy initialization or Lazy loading (Design pattern)
50. People who care about the outcome
Fully- dressed use case
Stakeholders
Lexer
Non - functional Requirements