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. (smell) A class whose only purpose is to hold data
Refactoring
Data classes
shotgun surgery
intellectual property
2. Verifies that system is protected against improper penetration
software quality
REST
Security testing
Anonymous function
3. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
copyright
feature envy
Acceptance testing
4. How well your fulfil your requirements
Decorator pattern
WSDL
use case
Software Quality
5. Derived methods should not assume more or deliver less
Maturity
Design patterns
Stress testing
Liskov substitution principle
6. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Semantic Web
First- class citizen
Lexer
Liskov substitution principle
7. Reusable - abstract 'blocks' of design
Dijkstra's law
Programming style
Design Patterns
Cowboy coding
8. Description of possible sequences of interactions between a user and the system.
Programming syntax
Closure
use case
duplicated code
9. (smell) method has too many statements - loops or variables
statement
sequence diagram
Maturity level
long method
10. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
duplicated code
SOP
middle man
Security testing
11. Object oriented programming; using objects to solve problems.
shotgun surgery
path
Non - functional Requirements
OOP
12. Testing that verifies that individual units of source code are working
Specification
unit testing
Law of demeter
long parameter list
13. The rigorousness of the tests that are able to be placed on the code
Maturity
Design pattern
Anonymous function
use case
14. Comprehensive description of software's intended purpose
Design patterns
SRS Documentation
branch
architectural design
15. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Integration testing
Non - functional Requirements
message chain
jquery
16. Lack of errors in code - readability etc
Requirements
sequence diagram
Code Quality
intellectual property
17. (smell)class with too many instance variables or too much code
middle man
Large class
software quality
path
18. 3rd step of requirements gathering
Specification
architectural design
comments
Quality metrics
19. Representational State Transfer.
message chain
a refactoring
REST
Stakeholders
20. Each line of code is covered once
statement
SOAP
Fully- dressed use case
Refactoring
21. The things a system must do
Maturity level
Liskov substitution principle
middle man
Requirements
22. People who care about the outcome
SOP
Stakeholders
Versioning
Lambda
23. Word - logo or symbol used to distinguish one organization's wares and services from another's
Lambda
trademark
architectural design
code quality
24. Models ->code work is done to keep models in sync with code
Requirements
white box testing
model- driven development
long method
25. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
model- driven development
Usability testing
Refactoring
26. 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
shotgun surgery
SOAP
Quality metrics
27. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Acceptance testing
Programming style
Feasibility
28. Each condition is covered twice (true - false)
SOP
Stress testing
branch
model- driven development
29. 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.
OOP
Programming syntax
Elicitation
Phase
30. Executes system in a manner that demands abnormal amounts of resources
use case
Maturity
Stress testing
Casual use case
31. Developing a plan for a product - system or component. 'how' a system should perform a task
Design
message chain
unit testing
Code Quality
32. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
patent
unit testing
Lazy initialization or Lazy loading (Design pattern)
Dijkstra's law
33. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
use case
Programming syntax
white box testing
34. (smell) Making one change requires changes in multiple places
shotgun surgery
trademark
sequence diagram
Refactoring
35. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Denormalization
Stakeholders
Large class
unit testing
36. A powerful motivator for change
WSDL
copyright
conflict
Programming style
37. A way to automatically grade code based on heuristics
Capacity testing
statement
trademark
Quality metrics
38. A computer program that divides code up into functional components
Test- driven development
message chain
Parser
branch
39. Freezing the state of the source code at a particular point
Capacity testing
Versioning
Integration testing
Casual use case
40. 4th step of requirements gathering
Dijkstra's law
Law of demeter
Casual use case
Validation
41. (smell) Classes using things that should be private in other classes
shotgun surgery
Decorator pattern
inappropriate intimacy
black box testing
42. Improve the internal design and implementation of code without affecting external behavior
software quality
sequence diagram
Refactoring
intellectual property
43. Degree to which the system meets the specified requirements and development standards
technical managerial approach
conflict
Database normalization
software quality
44. Testing where modules are combined and tested as a group
SRS Documentation
intellectual property
Integration testing
Law of demeter
45. One or two paragraphs of text outlining a use case
OOP
Decorator pattern
branch
Casual use case
46. Single step in a lifecycle
Phase
brief use case
Programming syntax
First- class citizen
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.
trademark
Anonymous function
First- class citizen
Delegation
48. Testing the whole system for functionality
Stakeholders
copyright
Association
system testing
49. (smell) client needs to use one object to get another and then use that one to get another
brief use case
Maturity level
code quality
message chain
50. Evaluates upper limits of operational parameters
long method
white box testing
Algorithm
Capacity testing