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. A powerful motivator for change
Casual use case
conflict
Non - functional Requirements
Design pattern
2. 'single dot rule'
duplicated code
a refactoring
code quality
Law of demeter
3. Absence of lifecycle
Cowboy coding
brief use case
WSDL
Usability testing
4. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Usability testing
WSDL
a refactoring
Recovery testing
5. Formal testing against end user specifications
Fully- dressed use case
Design patterns
technical managerial approach
Acceptance testing
6. Reusable - abstract 'blocks' of design
REST
Design pattern
Lifecycle
Design Patterns
7. A method that initializes a newly instantiated object
trademark
Constructor
Semantic Web
Law of demeter
8. 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
Use case diagram
Design
Recovery testing
9. 4th step of requirements gathering
code quality
Validation
Casual use case
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
10. 2nd step of requirements gathering
Acceptance testing
Lazy initialization or Lazy loading (Design pattern)
Parser
Analysis...
11. Protecting the embodiment of an idea
copyright
Dijkstra's law
Code Quality
sequence diagram
12. Object oriented programming; using objects to solve problems.
middle man
Algorithm
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
OOP
13. 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.
Software Quality
Integration testing
Programming syntax
use case
14. How developed code is (testing - documentation etc)
Validation
Maturity level
patent
Design pattern
15. Testing that verifies that individual units of source code are working
code quality
Validation
unit testing
sequence diagram
16. Approach to team management that splits management up into two people with separate tasks
WSDL
sequence diagram
statement
technical managerial approach
17. Series of phases through which software is developed
Lifecycle
Semantic Web
SOP
Validation
18. An operator used to denote anonymous functions or closures.
a refactoring
Acceptance testing
model- driven development
Lambda
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.
Recovery testing
Lexer
Lifecycle
Law of demeter
21. People who care about the outcome
Analysis...
Capacity testing
Recovery testing
Stakeholders
22. The rights governing the ownership and disposition of technology
feature envy
Feasibility
intellectual property
SRS Documentation
23. Evaluates upper limits of operational parameters
Non - functional Requirements
Capacity testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Maturity level
24. Diagram outlining the tasks that are going to be performed by the user
a refactoring
Use case diagram
code quality
jquery
25. Lack of errors in code - readability etc
system testing
Code Quality
Capacity testing
sequence diagram
26. Freezing the state of the source code at a particular point
Versioning
patent
Capacity testing
OOP
27. Derived methods should not assume more or deliver less
Liskov substitution principle
middle man
black box testing
Lifecycle
28. The things a system must do
SOAP
system testing
Requirements
code quality
29. Testing tactic that looks at all ways that data can flow through the code
white box testing
Lifecycle
use case
duplicated code
30. 1st step of requirements gathering
Elicitation
software quality
Cowboy coding
Recovery testing
31. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
code smell
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Analysis...
Denormalization
32. (smell) method has too many statements - loops or variables
long method
sequence diagram
Programming syntax
feature envy
33. Each possible path through the code is covered
Lambda
path
use case
long method
34. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
comments
Lambda
Data classes
35. Contract between inventor - assignee and state giving a time and geographically limited monopoly
inappropriate intimacy
Functional Requirements
patent
Denormalization
36. A relationship between objects.
Capacity testing
Association
comments
white box testing
37. (smell)class with too many instance variables or too much code
REST
Programming syntax
Large class
Refactoring
38. Techniques for composing objects to form larger structures
Lazy initialization or Lazy loading (Design pattern)
Test- driven development
Design patterns
sequence diagram
39. Word - logo or symbol used to distinguish one organization's wares and services from another's
Delegation
Casual use case
trademark
Programming style
40. (smell) code is repeated in multiple places
message chain
Phase
duplicated code
Data classes
41. 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
feature envy
Closure
Performance testing
Fully- dressed use case
42. Test the run - time performance of the system
Performance testing
Code Quality
Non - functional Requirements
Cowboy coding
43. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
data clumps
Closure
Database normalization
Test- driven development
44. Formal document outlining a task that needs to be performed on a system
Requirements
Liskov substitution principle
Fully- dressed use case
Delegation
45. 3rd step of requirements gathering
Denormalization
Specification
brief use case
Law of demeter
46. Reusable - abstract 'blocks' of design
Design pattern
First- class citizen
Database normalization
Dijkstra's law
47. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Association
Stakeholders
Anonymous function
Maturity
48. Ways to express the system's subsystems and their relationship
architectural design
technical managerial approach
model- driven development
patent
49. Tasks that a system must be able to perform
Functional Requirements
Closure
Design Patterns
Code Quality
50. Test cases made -> code compiles -> make code pass
Test- driven development
Recovery testing
Constructor
system testing