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
Lambda
Functional Requirements
comments
2. (smell) method has too many statements - loops or variables
data clumps
code smell
statement
long method
3. A powerful motivator for change
conflict
Code Quality
Validation
Design pattern
4. Each team member given set of features to work on
Programming style
Lifecycle
feature- driven development
software quality
5. Figuring out what the requirements are
Use case diagram
Elicitation
copyright
patent
6. Diagram used to show how information flows around the system
sequence diagram
Lifecycle
Lexer
patent
7. (smell) Classes using things that should be private in other classes
Test- driven development
Design patterns
Non - functional Requirements
inappropriate intimacy
8. A movement that promotes common formats for data.
Non - functional Requirements
Algorithm
Semantic Web
Acceptance testing
9. Test whether or not tasks can be accomplished efficiently by all levels of users
Lambda
jquery
Usability testing
Functional Requirements
10. The degree to which code is free of defects
code quality
Programming syntax
duplicated code
Constructor
11. 'single dot rule'
Maturity level
Maturity
Cowboy coding
Law of demeter
12. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Denormalization
Design Patterns
long method
copyright
13. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
Design patterns
software quality
Stress testing
14. 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
Elicitation
Delegation
path
Acceptance testing
15. (smell) many parameters are being passed into a method
long parameter list
Cowboy coding
Usability testing
Specification
16. A design pattern that allows behaviour to be added to an existing object dynamically.
Integration testing
Decorator pattern
Non - functional Requirements
long parameter list
17. Description of possible sequences of interactions between a user and the system.
REST
Use case diagram
SOAP
use case
18. How developed code is (testing - documentation etc)
middle man
Integration testing
Maturity level
code quality
19. Representational State Transfer.
Usability testing
Algorithm
REST
SOAP
20. Testing tactic that looks at all ways that data can flow through the code
Test- driven development
Closure
white box testing
Acceptance testing
21. Testing tactic based on whether inputs and outputs match up for required functionality
Decorator pattern
copyright
Use case diagram
black box testing
22. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Dijkstra's law
patent
Constructor
23. Series of phases through which software is developed
Law of demeter
code smell
Lifecycle
Capacity testing
24. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Design
SOP
Programming style
Lexer
25. Testing the whole system for functionality
conflict
First- class citizen
data clumps
system testing
26. Ways to express the system's subsystems and their relationship
architectural design
Versioning
duplicated code
Phase
27. 1st step of requirements gathering
Design patterns
Anonymous function
OOP
Elicitation
28. Freezing the state of the source code at a particular point
Versioning
Association
jquery
Maturity level
29. Testing where modules are combined and tested as a group
Refactoring
Integration testing
technical managerial approach
Law of demeter
30. Reusable - abstract 'blocks' of design
Design Patterns
Analysis...
Fully- dressed use case
Liskov substitution principle
31. A few sentences summarizing a use case
brief use case
code quality
Programming style
Closure
32. Test cases made -> code compiles -> make code pass
Lexer
intellectual property
Test- driven development
code smell
33. Diagram outlining the tasks that are going to be performed by the user
Lifecycle
regression testing
Use case diagram
Versioning
34. Formal testing against end user specifications
Feasibility
WSDL
Acceptance testing
Programming style
35. Derived methods should not assume more or deliver less
Maturity level
Liskov substitution principle
Lexer
Analysis...
36. 3rd step of requirements gathering
sequence diagram
trademark
Specification
Capacity testing
37. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Programming style
Elicitation
Design patterns
Lambda
38. Techniques for composing objects to form larger structures
Design patterns
OOP
Lexer
Parser
39. Word - logo or symbol used to distinguish one organization's wares and services from another's
trademark
Integration testing
Programming style
inappropriate intimacy
40. An operator used to denote anonymous functions or closures.
black box testing
use case
Lambda
Association
41. Models ->code work is done to keep models in sync with code
SOAP
model- driven development
Usability testing
software quality
42. A method that initializes a newly instantiated object
Stakeholders
Design patterns
WSDL
Constructor
43. 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.
black box testing
First- class citizen
Performance testing
Recovery testing
44. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
code quality
Usability testing
Casual use case
45. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Data classes
intellectual property
Anonymous function
Validation
46. Improve the internal design and implementation of code without affecting external behavior
Refactoring
technical managerial approach
shotgun surgery
message chain
47. A relationship between objects.
Anonymous function
Requirements
feature- driven development
Association
48. Approach to team management that splits management up into two people with separate tasks
Code Quality
Refactoring
technical managerial approach
path
49. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Code Quality
Validation
Lazy initialization or Lazy loading (Design pattern)
trademark
50. Tasks that a system must be able to perform
SOAP
Dijkstra's law
Database normalization
Functional Requirements