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. 2nd step of requirements gathering
SOP
feature- driven development
Fully- dressed use case
Analysis...
2. (smell) If a set of variables are used together in multiple places
data clumps
Closure
Requirements
statement
3. Testing tactic that looks at all ways that data can flow through the code
Acceptance testing
Decorator pattern
path
white box testing
4. A relationship between objects.
Association
REST
SRS Documentation
use case
5. Recognizable indicator that something may be wrong with code
feature envy
Usability testing
code smell
brief use case
6. Representational State Transfer.
Software Quality
REST
statement
comments
7. A method that initializes a newly instantiated object
Versioning
Capacity testing
Constructor
Delegation
8. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Quality metrics
code smell
jquery
conflict
9. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
code smell
long parameter list
Closure
10. Figuring out what the requirements are
Elicitation
Data classes
jquery
conflict
11. Testing the whole system for functionality
Design
Integration testing
REST
system testing
12. The rights governing the ownership and disposition of technology
OOP
regression testing
intellectual property
Functional Requirements
13. (smell) Making one change requires changes in multiple places
shotgun surgery
feature envy
intellectual property
path
14. 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.
Association
Constructor
First- class citizen
SOAP
15. Testing where modules are combined and tested as a group
Data classes
Integration testing
Design patterns
Requirements
16. The things a system must do
Requirements
Parser
data clumps
message chain
17. A computer program that divides code up into functional components
trademark
Dijkstra's law
Parser
long method
18. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
long parameter list
Integration testing
First- class citizen
19. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
SOP
model- driven development
Algorithm
Recovery testing
20. 4th step of requirements gathering
Database normalization
Versioning
white box testing
Validation
21. (smell) client needs to use one object to get another and then use that one to get another
brief use case
message chain
Security testing
sequence diagram
22. 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
SOP
message chain
Closure
Maturity level
23. A movement that promotes common formats for data.
Scrum (Agile software development)
Semantic Web
Liskov substitution principle
Closure
24. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Functional Requirements
Elicitation
Database normalization
25. 3rd step of requirements gathering
model- driven development
Design Patterns
duplicated code
Specification
26. (smell) Classes using things that should be private in other classes
Test- driven development
inappropriate intimacy
unit testing
Versioning
27. Constraints on the design due to external factors
Feasibility
Non - functional Requirements
comments
trademark
28. 1st step of requirements gathering
Association
Elicitation
technical managerial approach
feature- driven development
29. Testing tactic based on whether inputs and outputs match up for required functionality
code quality
Cowboy coding
black box testing
Casual use case
30. Iterative - incremental framework for project management.
Algorithm
Quality metrics
Scrum (Agile software development)
SOP
31. Degree to which the system meets the specified requirements and development standards
Design Patterns
software quality
system testing
Stress testing
32. 'single dot rule'
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Lazy initialization or Lazy loading (Design pattern)
Fully- dressed use case
Law of demeter
33. 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
First- class citizen
Test- driven development
Delegation
system testing
34. A few sentences summarizing a use case
system testing
SRS Documentation
brief use case
Phase
35. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
duplicated code
Programming syntax
Stakeholders
36. Diagram used to show how information flows around the system
copyright
Design patterns
sequence diagram
Programming syntax
37. Techniques for composing objects to form larger structures
Design patterns
sequence diagram
architectural design
Refactoring
38. Testing that verifies that individual units of source code are working
system testing
Elicitation
unit testing
SOP
39. Formal testing against end user specifications
Acceptance testing
code quality
Validation
system testing
40. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Capacity testing
Parser
Data classes
Lexer
41. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Fully- dressed use case
SOAP
Anonymous function
copyright
42. Evaluates upper limits of operational parameters
patent
Design pattern
conflict
Capacity testing
43. (smell) method has too many statements - loops or variables
Requirements
long method
Law of demeter
comments
44. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
Large class
regression testing
Constructor
45. Each team member given set of features to work on
Law of demeter
model- driven development
feature- driven development
Recovery testing
46. (smell) A method using another class more than its own
white box testing
Denormalization
feature envy
black box testing
47. Models ->code work is done to keep models in sync with code
architectural design
Specification
model- driven development
code smell
48. The degree to which code is free of defects
Large class
code quality
Elicitation
SRS Documentation
49. A way to automatically grade code based on heuristics
Design pattern
Delegation
code quality
Quality metrics
50. 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