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 designed to uncover regressions (where stuff that used to work doesn't work anymore)
long method
branch
use case
regression testing
2. 1st step of requirements gathering
technical managerial approach
Elicitation
system testing
statement
3. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
white box testing
Versioning
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Constructor
4. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Data classes
duplicated code
5. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
comments
Denormalization
REST
long method
6. (smell) many parameters are being passed into a method
long parameter list
First- class citizen
Semantic Web
Algorithm
7. Test whether or not tasks can be accomplished efficiently by all levels of users
path
Usability testing
Data classes
middle man
8. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Capacity testing
Programming style
black box testing
Database normalization
9. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
regression testing
Database normalization
SRS Documentation
Recovery testing
10. (smell) code is repeated in multiple places
inappropriate intimacy
Feasibility
duplicated code
long parameter list
11. Testing that verifies that individual units of source code are working
middle man
Lazy initialization or Lazy loading (Design pattern)
Design pattern
unit testing
12. Derived methods should not assume more or deliver less
Security testing
Liskov substitution principle
Maturity
conflict
13. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
branch
data clumps
Programming syntax
Anonymous function
14. A movement that promotes common formats for data.
Semantic Web
Stress testing
Lambda
technical managerial approach
15. Constraints on the design due to external factors
Design
unit testing
patent
Non - functional Requirements
16. The things a system must do
brief use case
Requirements
Decorator pattern
comments
17. Executes system in a manner that demands abnormal amounts of resources
Security testing
Validation
Stress testing
Feasibility
18. A computer program that divides code up into functional components
path
Parser
Feasibility
Anonymous function
19. Representational State Transfer.
Elicitation
path
Test- driven development
REST
20. (smell) If a set of variables are used together in multiple places
Lazy initialization or Lazy loading (Design pattern)
data clumps
WSDL
software quality
21. Description of possible sequences of interactions between a user and the system.
use case
Algorithm
Acceptance testing
Maturity level
22. Small - behaviour- preserving - source- to- source transformation
Code Quality
a refactoring
Design pattern
software quality
23. Ways to express the system's subsystems and their relationship
Stakeholders
Requirements
Lifecycle
architectural design
24. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
Refactoring
Maturity level
data clumps
25. Diagram outlining the tasks that are going to be performed by the user
white box testing
system testing
Functional Requirements
Use case diagram
26. Techniques for composing objects to form larger structures
Refactoring
Design patterns
Security testing
Programming style
27. Formal document outlining a task that needs to be performed on a system
Law of demeter
Fully- dressed use case
Design patterns
system testing
28. Test cases made -> code compiles -> make code pass
Denormalization
Test- driven development
Parser
model- driven development
29. 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.
Test- driven development
Dijkstra's law
First- class citizen
Performance testing
30. Lack of errors in code - readability etc
Code Quality
Refactoring
a refactoring
Anonymous function
31. (smell)class with too many instance variables or too much code
Large class
code quality
Algorithm
middle man
32. A powerful motivator for change
conflict
Semantic Web
Cowboy coding
branch
33. Verifies that system is protected against improper penetration
Fully- dressed use case
code quality
Security testing
Recovery testing
34. Reusable - abstract 'blocks' of design
Design pattern
white box testing
Software Quality
shotgun surgery
35. An operator used to denote anonymous functions or closures.
Scrum (Agile software development)
duplicated code
long parameter list
Lambda
36. Each possible path through the code is covered
path
Data classes
Use case diagram
Liskov substitution principle
37. Tasks that a system must be able to perform
Feasibility
regression testing
Database normalization
Functional Requirements
38. 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
39. 3rd step of requirements gathering
Lazy initialization or Lazy loading (Design pattern)
Dijkstra's law
Specification
Dijkstra's law
40. How well your fulfil your requirements
Software Quality
Semantic Web
middle man
Law of demeter
41. (smell) client needs to use one object to get another and then use that one to get another
Data classes
message chain
REST
technical managerial approach
42. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.
Feasibility
data clumps
Lifecycle
Usability testing
43. Single step in a lifecycle
Phase
patent
copyright
Algorithm
44. Force software to fail in order to see how it recovers
Dijkstra's law
Recovery testing
Functional Requirements
conflict
45. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Lazy initialization or Lazy loading (Design pattern)
jquery
Stakeholders
46. A relationship between objects.
jquery
Association
Design
Constructor
47. The rigorousness of the tests that are able to be placed on the code
Maturity level
WSDL
Software Quality
Maturity
48. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
use case
First- class citizen
SOP
Parser
49. Freezing the state of the source code at a particular point
Lifecycle
Maturity
Versioning
WSDL
50. Absence of lifecycle
Decorator pattern
Cowboy coding
Algorithm
Delegation