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 where modules are combined and tested as a group
SOP
white box testing
shotgun surgery
Integration testing
2. Series of phases through which software is developed
patent
Lifecycle
Phase
Programming syntax
3. (smell)class with too many instance variables or too much code
Large class
trademark
Algorithm
Refactoring
4. 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
Delegation
comments
Fully- dressed use case
Design patterns
5. (smell) One class delegates all of its requests to another class
middle man
duplicated code
Large class
comments
6. Improve the internal design and implementation of code without affecting external behavior
Refactoring
shotgun surgery
Acceptance testing
unit testing
7. Test the run - time performance of the system
Programming style
Performance testing
brief use case
Security testing
8. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
statement
jquery
technical managerial approach
Acceptance testing
9. Recognizable indicator that something may be wrong with code
Elicitation
Denormalization
code smell
Delegation
10. Each possible path through the code is covered
Algorithm
Non - functional Requirements
path
First- class citizen
11. Freezing the state of the source code at a particular point
middle man
Test- driven development
Refactoring
Versioning
12. A relationship between objects.
Association
statement
SOP
feature- driven development
13. Representational State Transfer.
Non - functional Requirements
Usability testing
architectural design
REST
14. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
model- driven development
jquery
middle man
15. Description of possible sequences of interactions between a user and the system.
Association
long parameter list
use case
Non - functional Requirements
16. Formal testing against end user specifications
Elicitation
Denormalization
Acceptance testing
Specification
17. The rigorousness of the tests that are able to be placed on the code
Design
Maturity level
Maturity
Usability testing
18. Derived methods should not assume more or deliver less
Design pattern
Liskov substitution principle
Acceptance testing
branch
19. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
Anonymous function
jquery
Code Quality
20. (smell) A class whose only purpose is to hold data
Large class
Specification
Database normalization
Data classes
21. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
comments
SOP
data clumps
Usability testing
22. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
path
Constructor
Refactoring
23. 2nd step of requirements gathering
trademark
Analysis...
duplicated code
data clumps
24. 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
sequence diagram
patent
Elicitation
25. How well your fulfil your requirements
First- class citizen
Versioning
Software Quality
Requirements
26. Verifies that system is protected against improper penetration
branch
Security testing
shotgun surgery
black box testing
27. Each line of code is covered once
Dijkstra's law
system testing
statement
Law of demeter
28. (smell) Classes using things that should be private in other classes
Lazy initialization or Lazy loading (Design pattern)
Design Patterns
Anonymous function
inappropriate intimacy
29. Testing tactic that looks at all ways that data can flow through the code
Elicitation
First- class citizen
white box testing
Casual use case
30. Force software to fail in order to see how it recovers
Recovery testing
Design
Stress testing
Law of demeter
31. Models ->code work is done to keep models in sync with code
Use case diagram
model- driven development
Recovery testing
Lifecycle
32. (smell) If a set of variables are used together in multiple places
Denormalization
Cowboy coding
data clumps
Programming syntax
33. (smell) many parameters are being passed into a method
OOP
long parameter list
inappropriate intimacy
Capacity testing
34. 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.
message chain
Requirements
Programming syntax
unit testing
35. Absence of lifecycle
system testing
intellectual property
Cowboy coding
Phase
36. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
shotgun surgery
Denormalization
Lazy initialization or Lazy loading (Design pattern)
Dijkstra's law
37. Each team member given set of features to work on
Lifecycle
Stress testing
Design patterns
feature- driven development
38. Testing the whole system for functionality
Scrum (Agile software development)
REST
system testing
Design pattern
39. The degree to which code is free of defects
code quality
Use case diagram
Delegation
black box testing
40. Iterative - incremental framework for project management.
First- class citizen
Association
Feasibility
Scrum (Agile software development)
41. Evaluates upper limits of operational parameters
Integration testing
Capacity testing
Large class
regression testing
42. Executes system in a manner that demands abnormal amounts of resources
branch
Stress testing
copyright
shotgun surgery
43. A few sentences summarizing a use case
Phase
brief use case
intellectual property
Casual use case
44. Diagram outlining the tasks that are going to be performed by the user
statement
Use case diagram
feature envy
sequence diagram
45. Tasks that a system must be able to perform
trademark
architectural design
Functional Requirements
sequence diagram
46. A way to automatically grade code based on heuristics
Specification
Recovery testing
Dijkstra's law
Quality metrics
47. 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
Database normalization
brief use case
Maturity
48. Single step in a lifecycle
Phase
Dijkstra's law
Refactoring
patent
49. A method that initializes a newly instantiated object
Non - functional Requirements
Constructor
Performance testing
Anonymous function
50. Techniques for composing objects to form larger structures
brief use case
Specification
Design patterns
Stakeholders