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. Testing tactic based on whether inputs and outputs match up for required functionality
feature envy
code smell
black box testing
feature- driven development
2. 2nd step of requirements gathering
Semantic Web
middle man
Anonymous function
Analysis...
3. Derived methods should not assume more or deliver less
Liskov substitution principle
Maturity
data clumps
feature envy
4. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Security testing
Programming style
Recovery testing
a refactoring
5. Recognizable indicator that something may be wrong with code
jquery
shotgun surgery
code smell
Lexer
6. A relationship between objects.
Use case diagram
Design patterns
Association
SRS Documentation
7. Test the run - time performance of the system
Lifecycle
Programming syntax
Performance testing
Design pattern
8. (smell) many parameters are being passed into a method
message chain
long parameter list
branch
Design patterns
9. Protecting the embodiment of an idea
Scrum (Agile software development)
WSDL
middle man
copyright
10. Approach to team management that splits management up into two people with separate tasks
Design pattern
Law of demeter
unit testing
technical managerial approach
11. Test whether or not tasks can be accomplished efficiently by all levels of users
path
Acceptance testing
Usability testing
Design Patterns
12. How developed code is (testing - documentation etc)
Cowboy coding
path
Elicitation
Maturity level
13. Improve the internal design and implementation of code without affecting external behavior
Phase
Functional Requirements
Refactoring
Lambda
14. A few sentences summarizing a use case
brief use case
Versioning
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Elicitation
15. Degree to which the system meets the specified requirements and development standards
Recovery testing
Algorithm
software quality
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
16. (smell) A class whose only purpose is to hold data
Lambda
Data classes
Maturity
model- driven development
17. (smell) Classes using things that should be private in other classes
Design Patterns
Maturity level
inappropriate intimacy
Maturity
18. 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
shotgun surgery
middle man
regression testing
Closure
19. Object oriented programming; using objects to solve problems.
Lazy initialization or Lazy loading (Design pattern)
brief use case
OOP
Use case diagram
20. Single step in a lifecycle
inappropriate intimacy
path
brief use case
Phase
21. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Code Quality
SOAP
WSDL
Phase
22. Iterative - incremental framework for project management.
Denormalization
Scrum (Agile software development)
code smell
Dijkstra's law
23. 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
sequence diagram
Maturity
Data classes
24. The degree to which code is free of defects
long method
Constructor
patent
code quality
25. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
REST
duplicated code
Lazy initialization or Lazy loading (Design pattern)
white box testing
26. (smell) One class delegates all of its requests to another class
Design
middle man
Delegation
Stress testing
27. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Liskov substitution principle
Casual use case
SOP
Programming style
28. (smell) If a set of variables are used together in multiple places
data clumps
Design pattern
long parameter list
Lambda
29. 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
Software Quality
Design patterns
Design Patterns
30. Contract between inventor - assignee and state giving a time and geographically limited monopoly
a refactoring
use case
Analysis...
patent
31. Force software to fail in order to see how it recovers
comments
SRS Documentation
Recovery testing
Performance testing
32. Diagram used to show how information flows around the system
sequence diagram
Performance testing
Data classes
Feasibility
33. A powerful motivator for change
statement
Acceptance testing
conflict
Constructor
34. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Elicitation
Software Quality
35. Word - logo or symbol used to distinguish one organization's wares and services from another's
Decorator pattern
statement
trademark
Code Quality
36. Description of possible sequences of interactions between a user and the system.
use case
Validation
Lambda
Usability testing
37. 3rd step of requirements gathering
Feasibility
Stakeholders
Specification
trademark
38. The things a system must do
Programming style
Functional Requirements
Liskov substitution principle
Requirements
39. 'single dot rule'
a refactoring
Refactoring
OOP
Law of demeter
40. (smell)class with too many instance variables or too much code
Data classes
Code Quality
Large class
Maturity
41. 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
Validation
Data classes
Delegation
Dijkstra's law
42. Representational State Transfer.
SOP
Decorator pattern
Security testing
REST
43. Each line of code is covered once
statement
Scrum (Agile software development)
Validation
Stress testing
44. Each condition is covered twice (true - false)
Anonymous function
Elicitation
Liskov substitution principle
branch
45. Small - behaviour- preserving - source- to- source transformation
a refactoring
Non - functional Requirements
Dijkstra's law
Versioning
46. A computer program that divides code up into functional components
Parser
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Use case diagram
Data classes
47. Testing the whole system for functionality
brief use case
SRS Documentation
system testing
Constructor
48. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
data clumps
jquery
architectural design
Software Quality
49. A movement that promotes common formats for data.
Semantic Web
Design patterns
Analysis...
OOP
50. Techniques for composing objects to form larger structures
Design patterns
Elicitation
duplicated code
First- class citizen