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. Description of possible sequences of interactions between a user and the system.
use case
Requirements
Programming syntax
conflict
2. Each team member given set of features to work on
Phase
feature- driven development
architectural design
Recovery testing
3. Contract between inventor - assignee and state giving a time and geographically limited monopoly
conflict
Acceptance testing
white box testing
patent
4. Developing a plan for a product - system or component. 'how' a system should perform a task
trademark
Design
Stress testing
Analysis...
5. Improve the internal design and implementation of code without affecting external behavior
Design Patterns
Law of demeter
Refactoring
duplicated code
6. Degree to which the system meets the specified requirements and development standards
shotgun surgery
software quality
conflict
Large class
7. 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
feature envy
code quality
model- driven development
8. (smell) Making one change requires changes in multiple places
shotgun surgery
SOP
Feasibility
Integration testing
9. Lack of errors in code - readability etc
Requirements
path
Code Quality
Cowboy coding
10. Each line of code is covered once
statement
a refactoring
long method
REST
11. 4th step of requirements gathering
long method
Validation
Constructor
Requirements
12. 'single dot rule'
Law of demeter
Anonymous function
statement
Lazy initialization or Lazy loading (Design pattern)
13. Formal document outlining a task that needs to be performed on a system
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Stakeholders
Fully- dressed use case
Liskov substitution principle
14. A computer program that divides code up into functional components
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Parser
Casual use case
Liskov substitution principle
15. The rigorousness of the tests that are able to be placed on the code
code smell
Maturity
Denormalization
Non - functional Requirements
16. 3rd step of requirements gathering
Functional Requirements
Use case diagram
Test- driven development
Specification
17. Diagram used to show how information flows around the system
Stakeholders
Programming style
Dijkstra's law
sequence diagram
18. Each possible path through the code is covered
Design Patterns
Refactoring
path
sequence diagram
19. Derived methods should not assume more or deliver less
system testing
use case
SRS Documentation
Liskov substitution principle
20. 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.
Casual use case
regression testing
Database normalization
Programming syntax
21. A method that initializes a newly instantiated object
Code Quality
Algorithm
Constructor
Analysis...
22. A few sentences summarizing a use case
inappropriate intimacy
brief use case
Decorator pattern
Design
23. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
branch
Analysis...
SOAP
24. Tasks that a system must be able to perform
statement
Functional Requirements
Lazy initialization or Lazy loading (Design pattern)
Test- driven development
25. Comprehensive description of software's intended purpose
Cowboy coding
SRS Documentation
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Phase
26. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Closure
SOP
use case
Elicitation
27. The things a system must do
Delegation
Lambda
Requirements
Stakeholders
28. How developed code is (testing - documentation etc)
black box testing
code quality
Maturity level
a refactoring
29. Object oriented programming; using objects to solve problems.
Algorithm
jquery
OOP
Validation
30. Reusable - abstract 'blocks' of design
SRS Documentation
Design patterns
Dijkstra's law
Design pattern
31. (smell) Smell deodorant
black box testing
comments
regression testing
unit testing
32. 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
Casual use case
Large class
Acceptance testing
Closure
33. Constraints on the design due to external factors
message chain
Non - functional Requirements
a refactoring
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
34. (smell) One class delegates all of its requests to another class
middle man
Casual use case
SOAP
Programming syntax
35. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
Parser
Casual use case
trademark
36. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
regression testing
WSDL
SRS Documentation
37. Test cases made -> code compiles -> make code pass
Lexer
Test- driven development
OOP
Lazy initialization or Lazy loading (Design pattern)
38. Reusable - abstract 'blocks' of design
duplicated code
Elicitation
jquery
Design Patterns
39. Test whether or not tasks can be accomplished efficiently by all levels of users
WSDL
Usability testing
Constructor
Lifecycle
40. 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
41. (smell) many parameters are being passed into a method
WSDL
Database normalization
long parameter list
regression testing
42. 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
statement
Analysis...
Data classes
43. Models ->code work is done to keep models in sync with code
model- driven development
Large class
Feasibility
patent
44. (smell) code is repeated in multiple places
Lifecycle
Usability testing
duplicated code
intellectual property
45. (smell) Classes using things that should be private in other classes
Liskov substitution principle
Functional Requirements
inappropriate intimacy
Design patterns
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.
Large class
model- driven development
Feasibility
duplicated code
47. (smell) method has too many statements - loops or variables
Maturity level
Data classes
long method
Quality metrics
48. A way to automatically grade code based on heuristics
statement
Quality metrics
Stress testing
Cowboy coding
49. A powerful motivator for change
SRS Documentation
Stress testing
Cowboy coding
conflict
50. Ways to express the system's subsystems and their relationship
Delegation
intellectual property
SOAP
architectural design