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. Small - behaviour- preserving - source- to- source transformation
Elicitation
a refactoring
duplicated code
Delegation
2. 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.
white box testing
Semantic Web
First- class citizen
Constructor
3. (smell) method has too many statements - loops or variables
long method
software quality
technical managerial approach
OOP
4. Lack of errors in code - readability etc
inappropriate intimacy
Code Quality
Design patterns
REST
5. The rights governing the ownership and disposition of technology
Usability testing
Software Quality
intellectual property
Law of demeter
6. Protecting the embodiment of an idea
copyright
Large class
Programming style
Integration testing
7. Testing tactic that looks at all ways that data can flow through the code
branch
white box testing
Use case diagram
long method
8. 4th step of requirements gathering
Validation
Law of demeter
copyright
path
9. A way to automatically grade code based on heuristics
Quality metrics
model- driven development
shotgun surgery
inappropriate intimacy
10. The degree to which code is free of defects
software quality
intellectual property
code quality
Feasibility
11. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
path
Stakeholders
Dijkstra's law
12. Recognizable indicator that something may be wrong with code
code smell
intellectual property
model- driven development
comments
13. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Constructor
REST
SOP
Use case diagram
14. Degree to which the system meets the specified requirements and development standards
Usability testing
Dijkstra's law
software quality
Parser
15. 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
Closure
Integration testing
message chain
Delegation
16. 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
17. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Lazy initialization or Lazy loading (Design pattern)
copyright
Specification
Design Patterns
18. Test cases made -> code compiles -> make code pass
a refactoring
statement
Test- driven development
code quality
19. (smell) A method using another class more than its own
middle man
sequence diagram
Specification
feature envy
20. Iterative - incremental framework for project management.
Maturity
Usability testing
Scrum (Agile software development)
Delegation
21. 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.
architectural design
Law of demeter
Phase
Programming syntax
22. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Algorithm
technical managerial approach
WSDL
Functional Requirements
23. Representational State Transfer.
long method
REST
Dijkstra's law
path
24. Contract between inventor - assignee and state giving a time and geographically limited monopoly
sequence diagram
comments
patent
long method
25. A powerful motivator for change
conflict
Security testing
Design
unit testing
26. 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
Parser
Closure
Non - functional Requirements
SRS Documentation
27. Comprehensive description of software's intended purpose
a refactoring
SOAP
SRS Documentation
branch
28. Force software to fail in order to see how it recovers
Lexer
Maturity
feature- driven development
Recovery testing
29. Description of possible sequences of interactions between a user and the system.
brief use case
use case
code quality
Data classes
30. 'single dot rule'
Test- driven development
Law of demeter
OOP
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
31. (smell) code is repeated in multiple places
Denormalization
duplicated code
Test- driven development
architectural design
32. (smell) A class whose only purpose is to hold data
Maturity
Maturity level
Data classes
middle man
33. (smell)class with too many instance variables or too much code
Delegation
Fully- dressed use case
middle man
Large class
34. A movement that promotes common formats for data.
message chain
regression testing
Semantic Web
Analysis...
35. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
system testing
white box testing
a refactoring
36. Formal testing against end user specifications
Fully- dressed use case
Association
Acceptance testing
Lifecycle
37. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
duplicated code
branch
Dijkstra's law
38. (smell) many parameters are being passed into a method
REST
long parameter list
code quality
middle man
39. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
Non - functional Requirements
Dijkstra's law
system testing
40. Approach to team management that splits management up into two people with separate tasks
statement
black box testing
technical managerial approach
Casual use case
41. Reusable - abstract 'blocks' of design
First- class citizen
Acceptance testing
black box testing
Design pattern
42. (smell) client needs to use one object to get another and then use that one to get another
Semantic Web
system testing
message chain
Code Quality
43. 3rd step of requirements gathering
use case
Refactoring
Delegation
Specification
44. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
long parameter list
Validation
jquery
patent
45. Test the run - time performance of the system
Programming style
intellectual property
architectural design
Performance testing
46. 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
Delegation
black box testing
unit testing
47. A few sentences summarizing a use case
conflict
path
copyright
brief use case
48. Verifies that system is protected against improper penetration
copyright
Security testing
sequence diagram
Recovery testing
49. Each line of code is covered once
Usability testing
statement
long parameter list
technical managerial approach
50. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Software Quality
shotgun surgery
regression testing
copyright