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. Single step in a lifecycle
Phase
Functional Requirements
Elicitation
software quality
2. Reusable - abstract 'blocks' of design
Performance testing
Design Patterns
Algorithm
architectural design
3. Test the run - time performance of the system
a refactoring
Closure
code quality
Performance testing
4. 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.
Lambda
Programming syntax
Design
jquery
5. Formal testing against end user specifications
code smell
SOP
Acceptance testing
long parameter list
6. Diagram outlining the tasks that are going to be performed by the user
Acceptance testing
Requirements
Use case diagram
branch
7. Degree to which the system meets the specified requirements and development standards
Non - functional Requirements
trademark
use case
software quality
8. Description of possible sequences of interactions between a user and the system.
Denormalization
model- driven development
use case
Use case diagram
9. How well your fulfil your requirements
Algorithm
statement
Software Quality
Programming style
10. The things a system must do
Requirements
Use case diagram
Dijkstra's law
jquery
11. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Data classes
Anonymous function
jquery
Quality metrics
12. Techniques for composing objects to form larger structures
Stress testing
Design patterns
Maturity
Closure
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.
use case
First- class citizen
Closure
Test- driven development
14. Executes system in a manner that demands abnormal amounts of resources
Denormalization
Phase
Stress testing
Dijkstra's law
15. The degree to which code is free of defects
code quality
Dijkstra's law
WSDL
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
16. 4th step of requirements gathering
Quality metrics
Feasibility
Phase
Validation
17. 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
Closure
Design Patterns
Decorator pattern
Maturity
18. Force software to fail in order to see how it recovers
WSDL
inappropriate intimacy
Recovery testing
Lexer
19. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Versioning
Integration testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
comments
20. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
Association
unit testing
Law of demeter
21. Testing tactic based on whether inputs and outputs match up for required functionality
Refactoring
architectural design
black box testing
Acceptance testing
22. (smell) many parameters are being passed into a method
Stress testing
long parameter list
Elicitation
Software Quality
23. (smell) Smell deodorant
comments
duplicated code
Closure
regression testing
24. Each condition is covered twice (true - false)
Large class
branch
black box testing
Code Quality
25. One or two paragraphs of text outlining a use case
Capacity testing
Performance testing
Casual use case
Cowboy coding
26. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Decorator pattern
architectural design
Code Quality
27. Absence of lifecycle
Capacity testing
black box testing
Cowboy coding
jquery
28. Models ->code work is done to keep models in sync with code
intellectual property
model- driven development
copyright
jquery
29. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
feature- driven development
path
WSDL
Phase
30. 2nd step of requirements gathering
long parameter list
Data classes
Scrum (Agile software development)
Analysis...
31. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Security testing
long method
statement
32. (smell) A class whose only purpose is to hold data
Decorator pattern
Data classes
feature envy
Versioning
33. Freezing the state of the source code at a particular point
Design patterns
Versioning
message chain
Closure
34. 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
black box testing
Specification
Programming style
Delegation
35. 'single dot rule'
Maturity
Law of demeter
Software Quality
Performance testing
36. Figuring out what the requirements are
Security testing
Elicitation
duplicated code
Database normalization
37. Testing the whole system for functionality
Stakeholders
system testing
Use case diagram
conflict
38. Reusable - abstract 'blocks' of design
Large class
Functional Requirements
Programming style
Design pattern
39. Improve the internal design and implementation of code without affecting external behavior
Specification
Quality metrics
architectural design
Refactoring
40. Word - logo or symbol used to distinguish one organization's wares and services from another's
trademark
Semantic Web
code quality
Requirements
41. People who care about the outcome
branch
Stress testing
Quality metrics
Stakeholders
42. A way to automatically grade code based on heuristics
sequence diagram
Phase
Law of demeter
Quality metrics
43. Evaluates upper limits of operational parameters
Design pattern
architectural design
Capacity testing
Performance testing
44. The rigorousness of the tests that are able to be placed on the code
Semantic Web
model- driven development
feature envy
Maturity
45. Each team member given set of features to work on
feature- driven development
Lambda
Algorithm
feature envy
46. (smell) A method using another class more than its own
feature envy
First- class citizen
path
regression testing
47. 1st step of requirements gathering
Quality metrics
unit testing
Cowboy coding
Elicitation
48. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
shotgun surgery
regression testing
black box testing
SOP
49. (smell) Making one change requires changes in multiple places
Lifecycle
shotgun surgery
REST
Versioning
50. (smell) client needs to use one object to get another and then use that one to get another
code smell
Test- driven development
message chain
Refactoring