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. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Elicitation
Feasibility
Database normalization
SOP
2. (smell) One class delegates all of its requests to another class
middle man
Maturity level
data clumps
Scrum (Agile software development)
3. (smell) A method using another class more than its own
feature envy
message chain
SOP
shotgun surgery
4. Approach to team management that splits management up into two people with separate tasks
Non - functional Requirements
model- driven development
technical managerial approach
Programming syntax
5. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
branch
WSDL
Lambda
Algorithm
6. Constraints on the design due to external factors
Denormalization
Lambda
sequence diagram
Non - functional Requirements
7. Recognizable indicator that something may be wrong with code
code smell
Recovery testing
software quality
Specification
8. Diagram used to show how information flows around the system
sequence diagram
architectural design
Law of demeter
Functional Requirements
9. Improve the internal design and implementation of code without affecting external behavior
black box testing
Validation
Refactoring
white box testing
10. Testing tactic that looks at all ways that data can flow through the code
conflict
Liskov substitution principle
Database normalization
white box testing
11. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Lexer
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
feature envy
Stakeholders
12. Description of possible sequences of interactions between a user and the system.
SRS Documentation
Versioning
use case
Scrum (Agile software development)
13. Each condition is covered twice (true - false)
long method
branch
Acceptance testing
software quality
14. (smell) many parameters are being passed into a method
Constructor
path
black box testing
long parameter list
15. Derived methods should not assume more or deliver less
shotgun surgery
Liskov substitution principle
Closure
comments
16. (smell) If a set of variables are used together in multiple places
data clumps
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
WSDL
Scrum (Agile software development)
17. (smell) Classes using things that should be private in other classes
Programming style
architectural design
inappropriate intimacy
data clumps
18. Diagram outlining the tasks that are going to be performed by the user
architectural design
Use case diagram
system testing
regression testing
19. How developed code is (testing - documentation etc)
Maturity level
SOAP
Acceptance testing
Dijkstra's law
20. Ways to express the system's subsystems and their relationship
shotgun surgery
Delegation
architectural design
Lexer
21. 1st step of requirements gathering
data clumps
shotgun surgery
Elicitation
Law of demeter
22. A way to automatically grade code based on heuristics
Analysis...
Quality metrics
Validation
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
23. Iterative - incremental framework for project management.
conflict
Semantic Web
Scrum (Agile software development)
middle man
24. Series of phases through which software is developed
architectural design
Dijkstra's law
Lifecycle
use case
25. A relationship between objects.
Association
Maturity level
REST
architectural design
26. 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
Association
Feasibility
SOP
Closure
27. People who care about the outcome
Lambda
WSDL
Design Patterns
Stakeholders
28. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
conflict
Requirements
Versioning
29. 'single dot rule'
Maturity
Database normalization
technical managerial approach
Law of demeter
30. Each team member given set of features to work on
feature- driven development
Lazy initialization or Lazy loading (Design pattern)
Programming syntax
Large class
31. Techniques for composing objects to form larger structures
a refactoring
Design patterns
sequence diagram
code quality
32. Small - behaviour- preserving - source- to- source transformation
a refactoring
Test- driven development
sequence diagram
duplicated code
33. A movement that promotes common formats for data.
SOAP
SRS Documentation
Semantic Web
jquery
34. 3rd step of requirements gathering
Specification
technical managerial approach
Lambda
Fully- dressed use case
35. Testing that verifies that individual units of source code are working
branch
unit testing
Analysis...
Association
36. 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
Fully- dressed use case
Phase
37. A computer program that divides code up into functional components
Casual use case
Parser
Association
Requirements
38. The rights governing the ownership and disposition of technology
system testing
Lexer
Stakeholders
intellectual property
39. Formal document outlining a task that needs to be performed on a system
Stress testing
copyright
Fully- dressed use case
Dijkstra's law
40. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Stress testing
Decorator pattern
Lazy initialization or Lazy loading (Design pattern)
Programming style
41. A few sentences summarizing a use case
Validation
white box testing
Programming style
brief use case
42. Each possible path through the code is covered
path
Cowboy coding
Lexer
Security testing
43. Figuring out what the requirements are
Code Quality
Stress testing
Constructor
Elicitation
44. The rigorousness of the tests that are able to be placed on the code
Closure
Database normalization
Maturity
Acceptance testing
45. Object oriented programming; using objects to solve problems.
Quality metrics
OOP
Security testing
Lambda
46. (smell) Smell deodorant
comments
feature- driven development
branch
duplicated code
47. Lack of errors in code - readability etc
brief use case
shotgun surgery
Stress testing
Code Quality
48. Freezing the state of the source code at a particular point
Dijkstra's law
branch
Versioning
Dijkstra's law
49. Test whether or not tasks can be accomplished efficiently by all levels of users
intellectual property
Usability testing
Elicitation
Validation
50. Reusable - abstract 'blocks' of design
code smell
First- class citizen
Design pattern
Fully- dressed use case