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. Series of phases through which software is developed
Acceptance testing
Dijkstra's law
Stakeholders
Lifecycle
2. Each team member given set of features to work on
feature- driven development
Dijkstra's law
Code Quality
white box testing
3. People who care about the outcome
Semantic Web
Stakeholders
Acceptance testing
Security testing
4. Each possible path through the code is covered
Performance testing
architectural design
Stress testing
path
5. Word - logo or symbol used to distinguish one organization's wares and services from another's
Usability testing
Large class
statement
trademark
6. The degree to which code is free of defects
Use case diagram
Stakeholders
First- class citizen
code quality
7. A method that initializes a newly instantiated object
system testing
feature- driven development
Constructor
Lazy initialization or Lazy loading (Design pattern)
8. Test the run - time performance of the system
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
duplicated code
Performance testing
conflict
9. (smell) One class delegates all of its requests to another class
middle man
SOP
Maturity level
Design patterns
10. Testing tactic based on whether inputs and outputs match up for required functionality
black box testing
Parser
white box testing
Non - functional Requirements
11. (smell)class with too many instance variables or too much code
copyright
Programming style
code smell
Large class
12. 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
Parser
system testing
Delegation
WSDL
13. Test whether or not tasks can be accomplished efficiently by all levels of users
Database normalization
Usability testing
message chain
Semantic Web
14. Single step in a lifecycle
patent
Lexer
Dijkstra's law
Phase
15. Lack of errors in code - readability etc
Code Quality
Lazy initialization or Lazy loading (Design pattern)
long method
Law of demeter
16. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Performance testing
Anonymous function
Denormalization
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
17. 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.
inappropriate intimacy
Parser
First- class citizen
Database normalization
18. A computer program that divides code up into functional components
Parser
SRS Documentation
Recovery testing
Use case diagram
19. A relationship between objects.
use case
feature- driven development
Liskov substitution principle
Association
20. Iterative - incremental framework for project management.
white box testing
Scrum (Agile software development)
SOP
Lambda
21. Protecting the embodiment of an idea
Phase
copyright
system testing
Specification
22. Small - behaviour- preserving - source- to- source transformation
trademark
Lifecycle
Stress testing
a refactoring
23. 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.
trademark
Feasibility
Capacity testing
Acceptance testing
24. Improve the internal design and implementation of code without affecting external behavior
Refactoring
Security testing
Programming style
statement
25. Testing tactic that looks at all ways that data can flow through the code
Usability testing
Association
Semantic Web
white box testing
26. 4th step of requirements gathering
Semantic Web
software quality
Validation
Functional Requirements
27. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Elicitation
copyright
28. 'single dot rule'
Law of demeter
sequence diagram
technical managerial approach
code smell
29. An operator used to denote anonymous functions or closures.
Lambda
Phase
data clumps
black box testing
30. Diagram used to show how information flows around the system
Elicitation
Performance testing
brief use case
sequence diagram
31. 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
32. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
branch
Dijkstra's law
shotgun surgery
Anonymous function
33. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
OOP
architectural design
Requirements
jquery
34. (smell) Smell deodorant
Law of demeter
comments
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Performance testing
35. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
SOAP
use case
regression testing
Lazy initialization or Lazy loading (Design pattern)
36. Freezing the state of the source code at a particular point
Elicitation
Performance testing
Versioning
Casual use case
37. Formal testing against end user specifications
Acceptance testing
Refactoring
feature envy
conflict
38. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
software quality
middle man
OOP
Denormalization
39. Representational State Transfer.
statement
REST
Validation
feature envy
40. (smell) A class whose only purpose is to hold data
Data classes
Code Quality
white box testing
message chain
41. The rights governing the ownership and disposition of technology
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Performance testing
intellectual property
Design
42. Executes system in a manner that demands abnormal amounts of resources
Programming syntax
Stress testing
Usability testing
unit testing
43. Test cases made -> code compiles -> make code pass
Test- driven development
Programming style
REST
Maturity
44. Derived methods should not assume more or deliver less
long parameter list
OOP
Liskov substitution principle
Denormalization
45. 2nd step of requirements gathering
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Analysis...
Requirements
Maturity
46. Reusable - abstract 'blocks' of design
SRS Documentation
Design Patterns
Design
Large class
47. (smell) code is repeated in multiple places
duplicated code
Maturity level
First- class citizen
black box testing
48. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Lazy initialization or Lazy loading (Design pattern)
data clumps
Programming style
system testing
49. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
trademark
Association
a refactoring
50. Figuring out what the requirements are
regression testing
statement
Capacity testing
Elicitation