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. (smell) client needs to use one object to get another and then use that one to get another
Dijkstra's law
black box testing
message chain
Phase
2. Single step in a lifecycle
Stress testing
Phase
system testing
Scrum (Agile software development)
3. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
long parameter list
Association
Database normalization
shotgun surgery
4. Testing that verifies that individual units of source code are working
OOP
unit testing
Dijkstra's law
Decorator pattern
5. The rigorousness of the tests that are able to be placed on the code
white box testing
Lazy initialization or Lazy loading (Design pattern)
Denormalization
Maturity
6. Figuring out what the requirements are
Semantic Web
Elicitation
Cowboy coding
Lifecycle
7. Testing tactic based on whether inputs and outputs match up for required functionality
Delegation
inappropriate intimacy
black box testing
Cowboy coding
8. Description of possible sequences of interactions between a user and the system.
Stress testing
use case
Quality metrics
Denormalization
9. Iterative - incremental framework for project management.
Programming syntax
long method
a refactoring
Scrum (Agile software development)
10. A computer program that divides code up into functional components
Parser
Large class
Capacity testing
software quality
11. (smell) Classes using things that should be private in other classes
inappropriate intimacy
Closure
code smell
use case
12. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
message chain
Security testing
Specification
Lexer
13. Ways to express the system's subsystems and their relationship
architectural design
Closure
copyright
Usability testing
14. (smell) method has too many statements - loops or variables
code smell
long method
Recovery testing
use case
15. 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
16. Test whether or not tasks can be accomplished efficiently by all levels of users
Performance testing
Usability testing
Dijkstra's law
Versioning
17. Each condition is covered twice (true - false)
Refactoring
inappropriate intimacy
branch
architectural design
18. Techniques for composing objects to form larger structures
Fully- dressed use case
Design patterns
Functional Requirements
Constructor
19. Reusable - abstract 'blocks' of design
Data classes
Law of demeter
Design pattern
architectural design
20. Absence of lifecycle
Feasibility
Denormalization
Cowboy coding
code quality
21. Models ->code work is done to keep models in sync with code
model- driven development
Functional Requirements
Constructor
long method
22. The degree to which code is free of defects
OOP
code quality
Scrum (Agile software development)
Dijkstra's law
23. Word - logo or symbol used to distinguish one organization's wares and services from another's
Lazy initialization or Lazy loading (Design pattern)
architectural design
Design
trademark
24. Representational State Transfer.
Design patterns
REST
Phase
duplicated code
25. Executes system in a manner that demands abnormal amounts of resources
long method
software quality
Stress testing
Elicitation
26. People who care about the outcome
Programming style
Stakeholders
Security testing
white box testing
27. Lack of errors in code - readability etc
Code Quality
Law of demeter
inappropriate intimacy
Feasibility
28. Diagram used to show how information flows around the system
shotgun surgery
Delegation
Stress testing
sequence diagram
29. (smell) many parameters are being passed into a method
Maturity
Design Patterns
long parameter list
unit testing
30. 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
31. Improve the internal design and implementation of code without affecting external behavior
Design Patterns
Acceptance testing
Refactoring
Denormalization
32. Derived methods should not assume more or deliver less
Elicitation
SRS Documentation
Liskov substitution principle
Constructor
33. 3rd step of requirements gathering
Specification
Quality metrics
copyright
Design Patterns
34. Small - behaviour- preserving - source- to- source transformation
use case
a refactoring
Lexer
Parser
35. (smell) code is repeated in multiple places
Feasibility
Stress testing
inappropriate intimacy
duplicated code
36. Each line of code is covered once
Code Quality
Capacity testing
statement
Lambda
37. Series of phases through which software is developed
Lifecycle
middle man
branch
Lazy initialization or Lazy loading (Design pattern)
38. A few sentences summarizing a use case
brief use case
software quality
Constructor
Semantic Web
39. 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
white box testing
message chain
Closure
sequence diagram
40. (smell) A class whose only purpose is to hold data
statement
Requirements
Data classes
path
41. Testing where modules are combined and tested as a group
Integration testing
Usability testing
REST
Stakeholders
42. A relationship between objects.
Association
Versioning
code quality
Validation
43. A way to automatically grade code based on heuristics
Lifecycle
Casual use case
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Quality metrics
44. Developing a plan for a product - system or component. 'how' a system should perform a task
Stress testing
white box testing
Casual use case
Design
45. The rights governing the ownership and disposition of technology
Semantic Web
Phase
statement
intellectual property
46. Degree to which the system meets the specified requirements and development standards
Cowboy coding
software quality
Closure
middle man
47. A powerful motivator for change
Security testing
conflict
SOP
Denormalization
48. Protecting the embodiment of an idea
copyright
model- driven development
REST
Design Patterns
49. Recognizable indicator that something may be wrong with code
software quality
code smell
Elicitation
architectural design
50. (smell) One class delegates all of its requests to another class
Design
copyright
middle man
Integration testing