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
Semantic Web
Closure
system testing
SOP
2. Testing that verifies that individual units of source code are working
unit testing
Maturity level
Functional Requirements
SOP
3. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Programming syntax
Dijkstra's law
Test- driven development
4. Diagram outlining the tasks that are going to be performed by the user
Use case diagram
system testing
SOAP
Cowboy coding
5. A computer program that divides code up into functional components
system testing
Parser
Programming style
Elicitation
6. Techniques for composing objects to form larger structures
Programming syntax
Dijkstra's law
Lexer
Design patterns
7. (smell) many parameters are being passed into a method
long parameter list
Validation
code smell
Association
8. An operator used to denote anonymous functions or closures.
Lexer
conflict
Lambda
SOAP
9. Iterative - incremental framework for project management.
Constructor
Law of demeter
comments
Scrum (Agile software development)
10. Tasks that a system must be able to perform
Design pattern
Decorator pattern
Functional Requirements
Analysis...
11. Figuring out what the requirements are
Algorithm
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Elicitation
Lifecycle
12. Testing tactic that looks at all ways that data can flow through the code
white box testing
Parser
system testing
Programming syntax
13. (smell) A class whose only purpose is to hold data
Algorithm
Data classes
jquery
WSDL
14. A design pattern that allows behaviour to be added to an existing object dynamically.
Validation
Design Patterns
architectural design
Decorator pattern
15. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Integration testing
Programming style
Semantic Web
16. Diagram used to show how information flows around the system
Quality metrics
Anonymous function
Lifecycle
sequence diagram
17. Approach to team management that splits management up into two people with separate tasks
technical managerial approach
Recovery testing
Law of demeter
comments
18. (smell) code is repeated in multiple places
white box testing
duplicated code
patent
Requirements
19. Comprehensive description of software's intended purpose
SRS Documentation
Specification
Algorithm
Elicitation
20. Description of possible sequences of interactions between a user and the system.
WSDL
use case
brief use case
Analysis...
21. The rigorousness of the tests that are able to be placed on the code
Maturity
comments
system testing
First- class citizen
22. (smell) Classes using things that should be private in other classes
Performance testing
inappropriate intimacy
Decorator pattern
Quality metrics
23. Testing the whole system for functionality
system testing
Casual use case
Stakeholders
Data classes
24. 'single dot rule'
unit testing
middle man
Design pattern
Law of demeter
25. Series of phases through which software is developed
Performance testing
Data classes
path
Lifecycle
26. A powerful motivator for change
Lambda
conflict
Capacity testing
SOP
27. Reusable - abstract 'blocks' of design
Design pattern
Decorator pattern
Maturity level
feature envy
28. The degree to which code is free of defects
jquery
code quality
Denormalization
brief use case
29. 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
Analysis...
REST
Delegation
Cowboy coding
30. (smell) Making one change requires changes in multiple places
Analysis...
SRS Documentation
jquery
shotgun surgery
31. A few sentences summarizing a use case
intellectual property
brief use case
patent
software quality
32. Formal document outlining a task that needs to be performed on a system
Scrum (Agile software development)
Fully- dressed use case
duplicated code
white box testing
33. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
Feasibility
Acceptance testing
Lambda
34. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
Scrum (Agile software development)
Database normalization
software quality
35. Freezing the state of the source code at a particular point
Lambda
branch
Phase
Versioning
36. Improve the internal design and implementation of code without affecting external behavior
Specification
Refactoring
sequence diagram
Capacity testing
37. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Elicitation
code smell
message chain
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
38. (smell) method has too many statements - loops or variables
Dijkstra's law
Security testing
white box testing
long method
39. Verifies that system is protected against improper penetration
Refactoring
Semantic Web
Security testing
middle man
40. Ways to express the system's subsystems and their relationship
Association
architectural design
Database normalization
Design patterns
41. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
white box testing
intellectual property
Functional Requirements
Anonymous function
42. 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
43. (smell)class with too many instance variables or too much code
First- class citizen
branch
Acceptance testing
Large class
44. 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.
feature envy
long method
Feasibility
Functional Requirements
45. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
inappropriate intimacy
trademark
Stress testing
46. How well your fulfil your requirements
Software Quality
message chain
Programming syntax
technical managerial approach
47. A way to automatically grade code based on heuristics
Design Patterns
Elicitation
Quality metrics
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
48. Small - behaviour- preserving - source- to- source transformation
trademark
Design pattern
a refactoring
Design
49. Reusable - abstract 'blocks' of design
Design Patterns
conflict
Dijkstra's law
Recovery testing
50. 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
Closure
patent
comments
use case