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. Diagram used to show how information flows around the system
Validation
Constructor
Parser
sequence diagram
2. Reusable - abstract 'blocks' of design
Design pattern
Casual use case
duplicated code
comments
3. Each team member given set of features to work on
long method
feature- driven development
message chain
First- class citizen
4. Force software to fail in order to see how it recovers
Recovery testing
Law of demeter
Security testing
SOP
5. A movement that promotes common formats for data.
data clumps
Stakeholders
message chain
Semantic Web
6. Lack of errors in code - readability etc
Quality metrics
Code Quality
branch
statement
7. (smell) many parameters are being passed into a method
long parameter list
black box testing
copyright
Lazy initialization or Lazy loading (Design pattern)
8. 1st step of requirements gathering
patent
Elicitation
Stress testing
Security testing
9. Constraints on the design due to external factors
code quality
Parser
Constructor
Non - functional Requirements
10. (smell) A method using another class more than its own
Lambda
Denormalization
Casual use case
feature envy
11. (smell) client needs to use one object to get another and then use that one to get another
WSDL
Constructor
message chain
First- class citizen
12. 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
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
Delegation
Dijkstra's law
system testing
middle man
14. Recognizable indicator that something may be wrong with code
SOP
Non - functional Requirements
code smell
feature envy
15. Degree to which the system meets the specified requirements and development standards
technical managerial approach
software quality
Programming style
Integration testing
16. Word - logo or symbol used to distinguish one organization's wares and services from another's
code smell
unit testing
trademark
Versioning
17. Diagram outlining the tasks that are going to be performed by the user
Denormalization
Data classes
Use case diagram
Feasibility
18. Executes system in a manner that demands abnormal amounts of resources
Stress testing
sequence diagram
Design patterns
model- driven development
19. 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.
Fully- dressed use case
Dijkstra's law
Feasibility
Lexer
20. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
feature- driven development
Security testing
SOAP
Large class
21. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
duplicated code
brief use case
Anonymous function
OOP
22. How well your fulfil your requirements
Lazy initialization or Lazy loading (Design pattern)
Software Quality
Stakeholders
WSDL
23. Testing tactic based on whether inputs and outputs match up for required functionality
Analysis...
black box testing
technical managerial approach
First- class citizen
24. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Programming style
duplicated code
Scrum (Agile software development)
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
25. Test whether or not tasks can be accomplished efficiently by all levels of users
feature- driven development
jquery
Usability testing
Programming syntax
26. (smell) code is repeated in multiple places
shotgun surgery
feature- driven development
duplicated code
statement
27. Object oriented programming; using objects to solve problems.
Functional Requirements
Quality metrics
architectural design
OOP
28. 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
29. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Software Quality
model- driven development
regression testing
Liskov substitution principle
30. 'single dot rule'
jquery
Anonymous function
Law of demeter
Constructor
31. Derived methods should not assume more or deliver less
Law of demeter
Decorator pattern
Delegation
Liskov substitution principle
32. Freezing the state of the source code at a particular point
Versioning
data clumps
Algorithm
middle man
33. Tasks that a system must be able to perform
intellectual property
Elicitation
Functional Requirements
duplicated code
34. Ways to express the system's subsystems and their relationship
patent
First- class citizen
architectural design
Test- driven development
35. Techniques for composing objects to form larger structures
Design patterns
Acceptance testing
regression testing
Anonymous function
36. Testing that verifies that individual units of source code are working
OOP
unit testing
Code Quality
Constructor
37. Series of phases through which software is developed
WSDL
Lifecycle
code quality
Analysis...
38. 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
Semantic Web
middle man
Closure
Delegation
39. The rights governing the ownership and disposition of technology
Lifecycle
Versioning
Scrum (Agile software development)
intellectual property
40. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
SOP
code quality
Denormalization
sequence diagram
41. An operator used to denote anonymous functions or closures.
unit testing
Algorithm
Lambda
Design patterns
42. Iterative - incremental framework for project management.
statement
Association
Scrum (Agile software development)
Decorator pattern
43. Protecting the embodiment of an idea
Lazy initialization or Lazy loading (Design pattern)
jquery
copyright
Decorator pattern
44. The degree to which code is free of defects
inappropriate intimacy
long method
code quality
Feasibility
45. 2nd step of requirements gathering
Analysis...
Recovery testing
a refactoring
path
46. The rigorousness of the tests that are able to be placed on the code
Liskov substitution principle
Maturity
Dijkstra's law
regression testing
47. Figuring out what the requirements are
Test- driven development
Elicitation
Functional Requirements
Design patterns
48. Reusable - abstract 'blocks' of design
Refactoring
WSDL
Design Patterns
intellectual property
49. Description of possible sequences of interactions between a user and the system.
Programming syntax
path
use case
Lambda
50. A few sentences summarizing a use case
path
brief use case
white box testing
Constructor