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 team member given set of features to work on
Usability testing
patent
Capacity testing
feature- driven development
2. Ways to express the system's subsystems and their relationship
Algorithm
architectural design
Programming style
brief use case
3. 4th step of requirements gathering
conflict
long method
Validation
Recovery testing
4. 1st step of requirements gathering
Functional Requirements
Elicitation
Refactoring
Delegation
5. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
code quality
Database normalization
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Specification
6. Series of phases through which software is developed
REST
Design Patterns
Large class
Lifecycle
7. Single step in a lifecycle
Phase
Anonymous function
Lazy initialization or Lazy loading (Design pattern)
trademark
8. People who care about the outcome
feature envy
WSDL
Stakeholders
Closure
9. Formal testing against end user specifications
feature- driven development
Maturity level
Programming style
Acceptance testing
10. Each condition is covered twice (true - false)
branch
path
software quality
long method
11. (smell) Classes using things that should be private in other classes
middle man
long parameter list
inappropriate intimacy
model- driven development
12. 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.
Dijkstra's law
Feasibility
path
code smell
13. (smell) many parameters are being passed into a method
Specification
long parameter list
Maturity level
Quality metrics
14. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
Capacity testing
Dijkstra's law
message chain
15. Force software to fail in order to see how it recovers
Recovery testing
Algorithm
Stakeholders
Design Patterns
16. Small - behaviour- preserving - source- to- source transformation
software quality
Test- driven development
a refactoring
Feasibility
17. Test whether or not tasks can be accomplished efficiently by all levels of users
Maturity level
First- class citizen
Usability testing
Versioning
18. Improve the internal design and implementation of code without affecting external behavior
Capacity testing
Refactoring
inappropriate intimacy
WSDL
19. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Casual use case
Versioning
20. Evaluates upper limits of operational parameters
Casual use case
inappropriate intimacy
Capacity testing
Anonymous function
21. (smell) If a set of variables are used together in multiple places
long method
Analysis...
SRS Documentation
data clumps
22. Description of possible sequences of interactions between a user and the system.
Validation
Design
Functional Requirements
use case
23. 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
sequence diagram
Lexer
Software Quality
Delegation
24. Freezing the state of the source code at a particular point
Versioning
brief use case
sequence diagram
use case
25. Reusable - abstract 'blocks' of design
Semantic Web
system testing
Refactoring
Design Patterns
26. Test the run - time performance of the system
SRS Documentation
Performance testing
model- driven development
Elicitation
27. A few sentences summarizing a use case
brief use case
Liskov substitution principle
Decorator pattern
Lambda
28. Testing where modules are combined and tested as a group
Maturity level
long parameter list
Integration testing
Algorithm
29. Executes system in a manner that demands abnormal amounts of resources
Stakeholders
Fully- dressed use case
feature- driven development
Stress testing
30. (smell) Making one change requires changes in multiple places
shotgun surgery
Closure
code quality
Recovery testing
31. Absence of lifecycle
Cowboy coding
Requirements
SRS Documentation
WSDL
32. Degree to which the system meets the specified requirements and development standards
Closure
software quality
Denormalization
Elicitation
33. Word - logo or symbol used to distinguish one organization's wares and services from another's
model- driven development
trademark
inappropriate intimacy
Data classes
34. How developed code is (testing - documentation etc)
Capacity testing
path
Cowboy coding
Maturity level
35. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
First- class citizen
Semantic Web
Performance testing
SOAP
36. (smell) code is repeated in multiple places
architectural design
Phase
Programming syntax
duplicated code
37. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
Requirements
Recovery testing
technical managerial approach
38. Models ->code work is done to keep models in sync with code
Closure
Data classes
patent
model- driven development
39. A method that initializes a newly instantiated object
Specification
First- class citizen
Acceptance testing
Constructor
40. Comprehensive description of software's intended purpose
SRS Documentation
Refactoring
black box testing
a refactoring
41. Figuring out what the requirements are
inappropriate intimacy
Elicitation
OOP
Refactoring
42. Verifies that system is protected against improper penetration
Capacity testing
middle man
sequence diagram
Security testing
43. The degree to which code is free of defects
code smell
Validation
unit testing
code quality
44. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Database normalization
Integration testing
sequence diagram
Programming style
45. (smell) A method using another class more than its own
architectural design
Closure
feature envy
Algorithm
46. Constraints on the design due to external factors
Integration testing
Non - functional Requirements
sequence diagram
Design
47. 3rd step of requirements gathering
Lazy initialization or Lazy loading (Design pattern)
Specification
Phase
brief use case
48. 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
Quality metrics
Closure
Database normalization
copyright
49. (smell) One class delegates all of its requests to another class
Database normalization
use case
Law of demeter
middle man
50. A design pattern that allows behaviour to be added to an existing object dynamically.
Programming style
regression testing
Decorator pattern
model- driven development