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. Tasks that a system must be able to perform
Maturity
Functional Requirements
Specification
long method
2. Lack of errors in code - readability etc
Code Quality
Lexer
feature- driven development
Recovery testing
3. (smell) Making one change requires changes in multiple places
code smell
Specification
Design patterns
shotgun surgery
4. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
code smell
Test- driven development
Scrum (Agile software development)
5. Protecting the embodiment of an idea
software quality
sequence diagram
copyright
WSDL
6. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Maturity
feature- driven development
regression testing
SRS Documentation
7. Object oriented programming; using objects to solve problems.
Validation
SOP
OOP
shotgun surgery
8. Formal document outlining a task that needs to be performed on a system
statement
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Fully- dressed use case
Design Patterns
9. Small - behaviour- preserving - source- to- source transformation
a refactoring
black box testing
comments
Design patterns
10. An operator used to denote anonymous functions or closures.
Closure
statement
Use case diagram
Lambda
11. Test the run - time performance of the system
Performance testing
sequence diagram
use case
Decorator pattern
12. The things a system must do
OOP
Elicitation
Large class
Requirements
13. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Constructor
use case
data clumps
Algorithm
14. People who care about the outcome
Data classes
copyright
Stakeholders
black box testing
15. 2nd step of requirements gathering
Design pattern
white box testing
Analysis...
sequence diagram
16. Figuring out what the requirements are
regression testing
Elicitation
Dijkstra's law
OOP
17. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Parser
Data classes
Lazy initialization or Lazy loading (Design pattern)
SOP
18. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Association
Closure
patent
long method
19. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Denormalization
regression testing
Test- driven development
Algorithm
20. A design pattern that allows behaviour to be added to an existing object dynamically.
Database normalization
Non - functional Requirements
WSDL
Decorator pattern
21. Absence of lifecycle
Cowboy coding
comments
Closure
Design pattern
22. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Dijkstra's law
trademark
Database normalization
white box testing
23. (smell) method has too many statements - loops or variables
long method
Decorator pattern
REST
Lifecycle
24. Representational State Transfer.
data clumps
long method
REST
Phase
25. (smell) Smell deodorant
comments
Stress testing
SRS Documentation
code quality
26. A few sentences summarizing a use case
brief use case
intellectual property
Non - functional Requirements
Elicitation
27. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
inappropriate intimacy
Parser
Maturity level
28. Techniques for composing objects to form larger structures
Design patterns
Programming style
Use case diagram
technical managerial approach
29. Models ->code work is done to keep models in sync with code
model- driven development
Liskov substitution principle
feature- driven development
patent
30. A relationship between objects.
code quality
Association
Dijkstra's law
Dijkstra's law
31. Iterative - incremental framework for project management.
Versioning
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Scrum (Agile software development)
SOP
32. (smell) many parameters are being passed into a method
OOP
duplicated code
Lifecycle
long parameter list
33. A computer program that divides code up into functional components
Parser
Security testing
long method
Lifecycle
34. A method that initializes a newly instantiated object
model- driven development
feature envy
Constructor
software quality
35. Each possible path through the code is covered
Decorator pattern
Semantic Web
Recovery testing
path
36. (smell) If a set of variables are used together in multiple places
Lifecycle
data clumps
Acceptance testing
architectural design
37. Testing tactic that looks at all ways that data can flow through the code
brief use case
Cowboy coding
Design
white box testing
38. One or two paragraphs of text outlining a use case
Dijkstra's law
software quality
Casual use case
feature- driven development
39. Testing can show the presence but not absence of errors
Warning
: Invalid argument supplied for foreach() in
/var/www/html/basicversity.com/show_quiz.php
on line
183
40. Constraints on the design due to external factors
Functional Requirements
a refactoring
code quality
Non - functional Requirements
41. (smell) Classes using things that should be private in other classes
Liskov substitution principle
Scrum (Agile software development)
inappropriate intimacy
Design pattern
42. Single step in a lifecycle
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Maturity
SRS Documentation
Phase
43. 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.
Delegation
Programming syntax
Functional Requirements
inappropriate intimacy
44. Diagram outlining the tasks that are going to be performed by the user
Use case diagram
code smell
jquery
Maturity level
45. (smell) client needs to use one object to get another and then use that one to get another
Dijkstra's law
white box testing
Anonymous function
message chain
46. 3rd step of requirements gathering
Closure
Specification
Maturity level
Phase
47. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Anonymous function
message chain
SOAP
duplicated code
48. Executes system in a manner that demands abnormal amounts of resources
Denormalization
brief use case
Stress testing
Closure
49. 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
inappropriate intimacy
Recovery testing
copyright
50. 1st step of requirements gathering
Design patterns
Elicitation
inappropriate intimacy
Security testing