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
Analysis...
Design pattern
Non - functional Requirements
Recovery testing
2. A design pattern that allows behaviour to be added to an existing object dynamically.
Feasibility
black box testing
a refactoring
Decorator pattern
3. Each possible path through the code is covered
Stakeholders
copyright
path
Dijkstra's law
4. A way to automatically grade code based on heuristics
Specification
Quality metrics
Design patterns
Versioning
5. Test whether or not tasks can be accomplished efficiently by all levels of users
Capacity testing
Usability testing
duplicated code
Cowboy coding
6. People who care about the outcome
comments
Functional Requirements
Software Quality
Stakeholders
7. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Lazy initialization or Lazy loading (Design pattern)
sequence diagram
Liskov substitution principle
8. Diagram used to show how information flows around the system
REST
Design
Law of demeter
sequence diagram
9. Small - behaviour- preserving - source- to- source transformation
Algorithm
long method
Refactoring
a refactoring
10. Test cases made -> code compiles -> make code pass
Semantic Web
Cowboy coding
middle man
Test- driven development
11. Figuring out what the requirements are
Data classes
Recovery testing
Elicitation
Decorator pattern
12. Executes system in a manner that demands abnormal amounts of resources
trademark
model- driven development
Stress testing
sequence diagram
13. 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
Feasibility
Dijkstra's law
Delegation
Refactoring
14. Each team member given set of features to work on
feature- driven development
Association
unit testing
Semantic Web
15. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
software quality
Programming style
REST
Maturity
16. Testing tactic based on whether inputs and outputs match up for required functionality
Liskov substitution principle
black box testing
Analysis...
Stakeholders
17. The rigorousness of the tests that are able to be placed on the code
Analysis...
unit testing
Maturity
Requirements
18. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
patent
Feasibility
Elicitation
Denormalization
19. How developed code is (testing - documentation etc)
Maturity level
path
a refactoring
feature- driven development
20. A powerful motivator for change
conflict
architectural design
Lambda
Elicitation
21. 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
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
Closure
Liskov substitution principle
Casual use case
OOP
23. (smell) A method using another class more than its own
regression testing
feature envy
Specification
software quality
24. Degree to which the system meets the specified requirements and development standards
software quality
Fully- dressed use case
Cowboy coding
REST
25. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Acceptance testing
Lazy initialization or Lazy loading (Design pattern)
Phase
26. Constraints on the design due to external factors
Non - functional Requirements
feature- driven development
model- driven development
code quality
27. 3rd step of requirements gathering
Phase
Specification
Lexer
Design Patterns
28. (smell) method has too many statements - loops or variables
Capacity testing
long method
architectural design
Dijkstra's law
29. Formal document outlining a task that needs to be performed on a system
Law of demeter
Fully- dressed use case
Constructor
Casual use case
30. (smell) A class whose only purpose is to hold data
Use case diagram
Data classes
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Usability testing
31. Testing that verifies that individual units of source code are working
regression testing
long method
feature- driven development
unit testing
32. Single step in a lifecycle
Phase
intellectual property
Stress testing
code smell
33. (smell) code is repeated in multiple places
branch
duplicated code
Requirements
copyright
34. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
trademark
Lambda
statement
35. Test the run - time performance of the system
Algorithm
shotgun surgery
Cowboy coding
Performance testing
36. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
inappropriate intimacy
SOP
Data classes
shotgun surgery
37. Verifies that system is protected against improper penetration
Dijkstra's law
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Scrum (Agile software development)
Security testing
38. Each condition is covered twice (true - false)
intellectual property
branch
black box testing
code quality
39. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
technical managerial approach
Denormalization
intellectual property
Lazy initialization or Lazy loading (Design pattern)
40. Tasks that a system must be able to perform
sequence diagram
Algorithm
Denormalization
Functional Requirements
41. (smell)class with too many instance variables or too much code
Analysis...
Validation
Large class
Specification
42. (smell) One class delegates all of its requests to another class
Refactoring
middle man
Software Quality
REST
43. (smell) client needs to use one object to get another and then use that one to get another
feature- driven development
message chain
sequence diagram
Non - functional Requirements
44. 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.
Stakeholders
Maturity
shotgun surgery
First- class citizen
45. A movement that promotes common formats for data.
Functional Requirements
message chain
sequence diagram
Semantic Web
46. 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.
Design pattern
Feasibility
Dijkstra's law
SOAP
47. (smell) Smell deodorant
data clumps
comments
middle man
Closure
48. Reusable - abstract 'blocks' of design
Delegation
long parameter list
Refactoring
Design Patterns
49. Testing the whole system for functionality
system testing
WSDL
message chain
duplicated code
50. Force software to fail in order to see how it recovers
Recovery testing
statement
Feasibility
WSDL