SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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. Testing that verifies that individual units of source code are working
Capacity testing
Parser
unit testing
Programming style
2. Formal document outlining a task that needs to be performed on a system
Programming style
Fully- dressed use case
branch
Association
3. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Constructor
WSDL
Test- driven development
a refactoring
4. Each line of code is covered once
Software Quality
patent
duplicated code
statement
5. Evaluates upper limits of operational parameters
Capacity testing
black box testing
Use case diagram
Large class
6. 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.
First- class citizen
Fully- dressed use case
branch
Non - functional Requirements
7. Lack of errors in code - readability etc
Phase
Code Quality
patent
software quality
8. Testing can show the presence but not absence of errors
9. The rigorousness of the tests that are able to be placed on the code
copyright
Elicitation
Maturity
Recovery testing
10. The things a system must do
Integration testing
Liskov substitution principle
middle man
Requirements
11. Techniques for composing objects to form larger structures
Design patterns
REST
Phase
Elicitation
12. Reusable - abstract 'blocks' of design
system testing
Lexer
Design pattern
Scrum (Agile software development)
13. Tasks that a system must be able to perform
SOP
Functional Requirements
SRS Documentation
a refactoring
14. Description of possible sequences of interactions between a user and the system.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
long method
white box testing
use case
15. Derived methods should not assume more or deliver less
Casual use case
Analysis...
feature envy
Liskov substitution principle
16. Each condition is covered twice (true - false)
branch
REST
duplicated code
Refactoring
17. (smell) Smell deodorant
comments
Maturity level
black box testing
conflict
18. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Denormalization
Lazy initialization or Lazy loading (Design pattern)
Algorithm
Performance testing
19. Absence of lifecycle
regression testing
a refactoring
Cowboy coding
Design patterns
20. Formal testing against end user specifications
SRS Documentation
Acceptance testing
Analysis...
Security testing
21. 1st step of requirements gathering
Elicitation
Programming style
Data classes
copyright
22. A few sentences summarizing a use case
Decorator pattern
SOAP
brief use case
Functional Requirements
23. A movement that promotes common formats for data.
REST
use case
Closure
Semantic Web
24. Figuring out what the requirements are
Elicitation
Design pattern
jquery
Decorator pattern
25. Diagram outlining the tasks that are going to be performed by the user
Lexer
REST
Use case diagram
use case
26. A method that initializes a newly instantiated object
Constructor
technical managerial approach
code quality
conflict
27. Recognizable indicator that something may be wrong with code
code smell
technical managerial approach
Non - functional Requirements
Software Quality
28. Protecting the embodiment of an idea
copyright
Refactoring
Analysis...
REST
29. Test cases made -> code compiles -> make code pass
Test- driven development
software quality
First- class citizen
Anonymous function
30. Test the run - time performance of the system
Law of demeter
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Performance testing
Acceptance testing
31. The rights governing the ownership and disposition of technology
Database normalization
intellectual property
system testing
technical managerial approach
32. Diagram used to show how information flows around the system
Stakeholders
Delegation
Association
sequence diagram
33. Small - behaviour- preserving - source- to- source transformation
feature- driven development
Test- driven development
a refactoring
shotgun surgery
34. A computer program that divides code up into functional components
Programming syntax
system testing
technical managerial approach
Parser
35. One or two paragraphs of text outlining a use case
Casual use case
Quality metrics
WSDL
OOP
36. Freezing the state of the source code at a particular point
Lambda
Versioning
Law of demeter
SRS Documentation
37. Constraints on the design due to external factors
Non - functional Requirements
Elicitation
OOP
patent
38. 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.
Programming syntax
shotgun surgery
Law of demeter
Non - functional Requirements
39. 3rd step of requirements gathering
Specification
brief use case
SRS Documentation
architectural design
40. Word - logo or symbol used to distinguish one organization's wares and services from another's
Software Quality
trademark
Dijkstra's law
Casual use case
41. Series of phases through which software is developed
Lifecycle
Design pattern
jquery
Decorator pattern
42. How well your fulfil your requirements
Stress testing
comments
Software Quality
Test- driven development
43. 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
Code Quality
Dijkstra's law
Design Patterns
Delegation
44. An operator used to denote anonymous functions or closures.
Lambda
Constructor
Stress testing
jquery
45. Iterative - incremental framework for project management.
Scrum (Agile software development)
Software Quality
Denormalization
statement
46. 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
OOP
Data classes
Closure
Integration testing
47. A way to automatically grade code based on heuristics
Use case diagram
Dijkstra's law
Quality metrics
patent
48. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
Non - functional Requirements
Decorator pattern
Lazy initialization or Lazy loading (Design pattern)
49. Test whether or not tasks can be accomplished efficiently by all levels of users
Fully- dressed use case
Non - functional Requirements
Large class
Usability testing
50. Ways to express the system's subsystems and their relationship
Design pattern
Analysis...
architectural design
Maturity