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. The rights governing the ownership and disposition of technology
intellectual property
long parameter list
Recovery testing
SOP
2. A method that initializes a newly instantiated object
Performance testing
Data classes
Constructor
model- driven development
3. 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
regression testing
Programming style
Code Quality
4. Description of possible sequences of interactions between a user and the system.
First- class citizen
intellectual property
Stress testing
use case
5. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
path
code quality
architectural design
SOP
6. (smell) Classes using things that should be private in other classes
inappropriate intimacy
Versioning
Software Quality
Design pattern
7. Test whether or not tasks can be accomplished efficiently by all levels of users
Software Quality
shotgun surgery
Law of demeter
Usability testing
8. A design pattern that allows behaviour to be added to an existing object dynamically.
inappropriate intimacy
Elicitation
Decorator pattern
a refactoring
9. Tasks that a system must be able to perform
statement
Functional Requirements
Analysis...
Delegation
10. Each line of code is covered once
comments
statement
SOAP
Fully- dressed use case
11. Evaluates upper limits of operational parameters
Capacity testing
REST
Functional Requirements
code quality
12. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lazy initialization or Lazy loading (Design pattern)
Stakeholders
Dijkstra's law
Lexer
13. 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.
duplicated code
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
First- class citizen
Versioning
14. Series of phases through which software is developed
Non - functional Requirements
Lifecycle
SRS Documentation
Parser
15. (smell) code is repeated in multiple places
Quality metrics
feature- driven development
duplicated code
long method
16. (smell) Smell deodorant
path
comments
black box testing
use case
17. Testing tactic based on whether inputs and outputs match up for required functionality
SOP
Algorithm
middle man
black box testing
18. 2nd step of requirements gathering
Elicitation
Feasibility
middle man
Analysis...
19. Executes system in a manner that demands abnormal amounts of resources
shotgun surgery
Stress testing
Semantic Web
Design pattern
20. Figuring out what the requirements are
Elicitation
Denormalization
sequence diagram
Stress testing
21. Each condition is covered twice (true - false)
branch
jquery
Dijkstra's law
Capacity testing
22. 3rd step of requirements gathering
Phase
regression testing
Specification
comments
23. Improve the internal design and implementation of code without affecting external behavior
SOAP
Specification
Quality metrics
Refactoring
24. 1st step of requirements gathering
Requirements
Quality metrics
Elicitation
Casual use case
25. Derived methods should not assume more or deliver less
Liskov substitution principle
brief use case
Quality metrics
statement
26. (smell) A method using another class more than its own
OOP
feature envy
Delegation
patent
27. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Law of demeter
Usability testing
Design
28. Approach to team management that splits management up into two people with separate tasks
Test- driven development
Stress testing
Non - functional Requirements
technical managerial approach
29. Developing a plan for a product - system or component. 'how' a system should perform a task
Programming syntax
code quality
data clumps
Design
30. A relationship between objects.
Casual use case
brief use case
use case
Association
31. Representational State Transfer.
shotgun surgery
Refactoring
Design pattern
REST
32. Absence of lifecycle
Cowboy coding
Design patterns
Anonymous function
Design
33. Constraints on the design due to external factors
Design Patterns
Semantic Web
regression testing
Non - functional Requirements
34. 'single dot rule'
Law of demeter
Stress testing
brief use case
Specification
35. Verifies that system is protected against improper penetration
patent
Integration testing
Security testing
Lexer
36. Testing that verifies that individual units of source code are working
path
unit testing
Semantic Web
architectural design
37. Formal testing against end user specifications
Database normalization
Acceptance testing
Fully- dressed use case
SOP
38. How well your fulfil your requirements
inappropriate intimacy
model- driven development
Software Quality
Lazy initialization or Lazy loading (Design pattern)
39. (smell) One class delegates all of its requests to another class
middle man
Lazy initialization or Lazy loading (Design pattern)
SRS Documentation
system testing
40. 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
Anonymous function
Programming syntax
Design patterns
41. Diagram outlining the tasks that are going to be performed by the user
Acceptance testing
system testing
Use case diagram
Requirements
42. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
Versioning
code quality
Functional Requirements
43. A computer program that divides code up into functional components
Lifecycle
Parser
Use case diagram
Data classes
44. Single step in a lifecycle
Casual use case
sequence diagram
Phase
technical managerial approach
45. Small - behaviour- preserving - source- to- source transformation
Test- driven development
unit testing
a refactoring
Scrum (Agile software development)
46. Models ->code work is done to keep models in sync with code
long parameter list
OOP
Software Quality
model- driven development
47. The things a system must do
intellectual property
Requirements
feature- driven development
feature envy
48. Testing tactic that looks at all ways that data can flow through the code
black box testing
Maturity
white box testing
patent
49. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
white box testing
Fully- dressed use case
SRS Documentation
Database normalization
50. A way to automatically grade code based on heuristics
regression testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Quality metrics
Capacity testing