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. Protecting the embodiment of an idea
comments
SRS Documentation
copyright
Cowboy coding
2. (smell) method has too many statements - loops or variables
Algorithm
long method
Parser
feature envy
3. Testing the whole system for functionality
system testing
Semantic Web
Constructor
branch
4. A relationship between objects.
REST
First- class citizen
Association
Security testing
5. 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 Quality
shotgun surgery
code quality
6. The things a system must do
Fully- dressed use case
Maturity level
Requirements
use case
7. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
path
message chain
Denormalization
8. Contract between inventor - assignee and state giving a time and geographically limited monopoly
Test- driven development
patent
Scrum (Agile software development)
Algorithm
9. (smell) A method using another class more than its own
feature envy
Specification
long method
Use case diagram
10. 4th step of requirements gathering
Validation
middle man
technical managerial approach
statement
11. Force software to fail in order to see how it recovers
Design
Recovery testing
Constructor
WSDL
12. Series of phases through which software is developed
Lifecycle
Performance testing
Lexer
Design patterns
13. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
jquery
Usability testing
Fully- dressed use case
Lexer
14. A method that initializes a newly instantiated object
Constructor
a refactoring
Fully- dressed use case
Refactoring
15. Developing a plan for a product - system or component. 'how' a system should perform a task
Lazy initialization or Lazy loading (Design pattern)
Design
Specification
intellectual property
16. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Security testing
Dijkstra's law
Anonymous function
REST
17. 'single dot rule'
Design patterns
SOAP
Law of demeter
black box testing
18. Diagram used to show how information flows around the system
technical managerial approach
Recovery testing
sequence diagram
Casual use case
19. Formal testing against end user specifications
Denormalization
Acceptance testing
Maturity
Specification
20. (smell) Making one change requires changes in multiple places
Maturity
jquery
shotgun surgery
regression testing
21. Comprehensive description of software's intended purpose
brief use case
SRS Documentation
Acceptance testing
Usability testing
22. Recognizable indicator that something may be wrong with code
Refactoring
Closure
Programming syntax
code smell
23. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Denormalization
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Maturity
Scrum (Agile software development)
24. Constraints on the design due to external factors
Scrum (Agile software development)
sequence diagram
Maturity
Non - functional Requirements
25. (smell)class with too many instance variables or too much code
Large class
Recovery testing
Lexer
Code Quality
26. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Analysis...
SRS Documentation
branch
27. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
conflict
Use case diagram
Lambda
SOP
28. Small - behaviour- preserving - source- to- source transformation
a refactoring
intellectual property
use case
Casual use case
29. 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
OOP
middle man
Design
30. Test cases made -> code compiles -> make code pass
Recovery testing
shotgun surgery
Test- driven development
Stakeholders
31. 1st step of requirements gathering
sequence diagram
Closure
Algorithm
Elicitation
32. Improve the internal design and implementation of code without affecting external behavior
model- driven development
Refactoring
Elicitation
Elicitation
33. Each possible path through the code is covered
Integration testing
path
patent
Parser
34. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
patent
Integration testing
Decorator pattern
35. Derived methods should not assume more or deliver less
Design patterns
software quality
Maturity
Liskov substitution principle
36. The rigorousness of the tests that are able to be placed on the code
Maturity
Stakeholders
Constructor
code quality
37. Figuring out what the requirements are
Design
software quality
Elicitation
Closure
38. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Fully- dressed use case
Non - functional Requirements
WSDL
branch
39. One or two paragraphs of text outlining a use case
duplicated code
Functional Requirements
Casual use case
Integration testing
40. Single step in a lifecycle
Feasibility
Phase
architectural design
statement
41. Lack of errors in code - readability etc
branch
REST
feature- driven development
Code Quality
42. 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 syntax
Integration testing
patent
Programming style
43. 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.
REST
Programming syntax
First- class citizen
Use case diagram
44. Techniques for composing objects to form larger structures
branch
duplicated code
Design patterns
Stakeholders
45. Ways to express the system's subsystems and their relationship
software quality
Design
architectural design
Recovery testing
46. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
inappropriate intimacy
feature- driven development
jquery
middle man
47. The degree to which code is free of defects
message chain
code quality
inappropriate intimacy
Programming style
48. Each line of code is covered once
Functional Requirements
long parameter list
statement
Stress testing
49. Degree to which the system meets the specified requirements and development standards
software quality
data clumps
Constructor
feature- driven development
50. A few sentences summarizing a use case
code quality
brief use case
intellectual property
unit testing