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. The rigorousness of the tests that are able to be placed on the code
Design
Maturity
Software Quality
technical managerial approach
2. 'single dot rule'
code smell
Design Patterns
Law of demeter
Design
3. 2nd step of requirements gathering
Analysis...
Denormalization
Quality metrics
trademark
4. (smell) One class delegates all of its requests to another class
Scrum (Agile software development)
comments
middle man
intellectual property
5. A few sentences summarizing a use case
brief use case
architectural design
Software Quality
Design
6. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Dijkstra's law
long parameter list
feature- driven development
7. Protecting the embodiment of an idea
jquery
Recovery testing
copyright
path
8. Formal testing against end user specifications
Semantic Web
Acceptance testing
Validation
shotgun surgery
9. A movement that promotes common formats for data.
Semantic Web
Parser
Scrum (Agile software development)
feature- driven development
10. Approach to team management that splits management up into two people with separate tasks
feature envy
technical managerial approach
statement
conflict
11. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Lambda
Denormalization
conflict
jquery
12. The rights governing the ownership and disposition of technology
intellectual property
Cowboy coding
Maturity
Stress testing
13. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
Maturity
Decorator pattern
data clumps
14. 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
15. A powerful motivator for change
system testing
long method
conflict
feature- driven development
16. Testing where modules are combined and tested as a group
Dijkstra's law
software quality
Integration testing
a refactoring
17. Improve the internal design and implementation of code without affecting external behavior
Dijkstra's law
Refactoring
statement
use case
18. A method that initializes a newly instantiated object
Maturity
shotgun surgery
Lazy initialization or Lazy loading (Design pattern)
Constructor
19. 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
20. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Large class
Lexer
code quality
unit testing
21. Lack of errors in code - readability etc
jquery
Programming style
Code Quality
use case
22. 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.
sequence diagram
Programming syntax
Functional Requirements
Phase
23. A design pattern that allows behaviour to be added to an existing object dynamically.
architectural design
Decorator pattern
middle man
trademark
24. Reusable - abstract 'blocks' of design
shotgun surgery
Usability testing
copyright
Design pattern
25. Representational State Transfer.
OOP
REST
Scrum (Agile software development)
Delegation
26. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Law of demeter
Algorithm
Recovery testing
Dijkstra's law
27. Small - behaviour- preserving - source- to- source transformation
Law of demeter
a refactoring
copyright
path
28. 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
regression testing
Code Quality
Design pattern
Closure
29. People who care about the outcome
Stakeholders
Constructor
Non - functional Requirements
Feasibility
30. One or two paragraphs of text outlining a use case
shotgun surgery
Casual use case
comments
intellectual property
31. The degree to which code is free of defects
code smell
shotgun surgery
code quality
Integration testing
32. Testing tactic that looks at all ways that data can flow through the code
Phase
Liskov substitution principle
Denormalization
white box testing
33. Test whether or not tasks can be accomplished efficiently by all levels of users
Integration testing
Usability testing
First- class citizen
Cowboy coding
34. Ways to express the system's subsystems and their relationship
path
architectural design
Database normalization
Lazy initialization or Lazy loading (Design pattern)
35. 4th step of requirements gathering
Anonymous function
Stakeholders
Programming style
Validation
36. Techniques for composing objects to form larger structures
Constructor
Performance testing
Design patterns
First- class citizen
37. Force software to fail in order to see how it recovers
brief use case
Algorithm
Recovery testing
Software Quality
38. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
unit testing
long method
Lazy initialization or Lazy loading (Design pattern)
Use case diagram
39. (smell) many parameters are being passed into a method
Maturity
long parameter list
Anonymous function
feature- driven development
40. (smell)class with too many instance variables or too much code
unit testing
duplicated code
long method
Large class
41. 3rd step of requirements gathering
Use case diagram
Specification
Casual use case
Denormalization
42. Each possible path through the code is covered
Performance testing
path
Integration testing
comments
43. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Elicitation
Recovery testing
patent
Performance testing
44. Comprehensive description of software's intended purpose
Security testing
SRS Documentation
Functional Requirements
Large class
45. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
copyright
Database normalization
feature envy
model- driven development
46. An operator used to denote anonymous functions or closures.
Lambda
Integration testing
long method
Functional Requirements
47. 1st step of requirements gathering
Liskov substitution principle
Lifecycle
Database normalization
Elicitation
48. Iterative - incremental framework for project management.
path
black box testing
Scrum (Agile software development)
Use case diagram
49. Recognizable indicator that something may be wrong with code
Maturity
Lambda
Code Quality
code smell
50. Derived methods should not assume more or deliver less
system testing
patent
Liskov substitution principle
Design pattern