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. The degree to which code is free of defects
long parameter list
Phase
code quality
Refactoring
2. (smell) Making one change requires changes in multiple places
Refactoring
shotgun surgery
model- driven development
Cowboy coding
3. Diagram outlining the tasks that are going to be performed by the user
Use case diagram
Design pattern
Software Quality
Code Quality
4. A method that initializes a newly instantiated object
Constructor
SOAP
patent
code smell
5. Techniques for composing objects to form larger structures
SRS Documentation
Design patterns
Scrum (Agile software development)
Large class
6. A movement that promotes common formats for data.
Dijkstra's law
Stakeholders
Semantic Web
statement
7. Contract between inventor - assignee and state giving a time and geographically limited monopoly
system testing
patent
Design patterns
Use case diagram
8. A computer program that divides code up into functional components
sequence diagram
Parser
SOP
model- driven development
9. One or two paragraphs of text outlining a use case
Design patterns
jquery
Casual use case
Programming syntax
10. Small - behaviour- preserving - source- to- source transformation
Functional Requirements
a refactoring
Phase
feature- driven development
11. Test the run - time performance of the system
Performance testing
Database normalization
Security testing
architectural design
12. 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
Requirements
Maturity level
branch
13. 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
14. 4th step of requirements gathering
Lambda
Validation
use case
Code Quality
15. Developing a plan for a product - system or component. 'how' a system should perform a task
Programming syntax
Database normalization
Lambda
Design
16. 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.
Refactoring
Performance testing
Programming syntax
middle man
17. Improve the internal design and implementation of code without affecting external behavior
Refactoring
duplicated code
conflict
Code Quality
18. Testing tactic based on whether inputs and outputs match up for required functionality
black box testing
Quality metrics
Casual use case
Maturity level
19. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Dijkstra's law
Lazy initialization or Lazy loading (Design pattern)
statement
SOAP
20. Derived methods should not assume more or deliver less
jquery
feature- driven development
Dijkstra's law
Liskov substitution principle
21. (smell) If a set of variables are used together in multiple places
Capacity testing
data clumps
Lambda
message chain
22. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Database normalization
regression testing
conflict
Maturity level
23. Figuring out what the requirements are
Semantic Web
Elicitation
Algorithm
Delegation
24. Reusable - abstract 'blocks' of design
Casual use case
Refactoring
unit testing
Design pattern
25. 'single dot rule'
Refactoring
copyright
sequence diagram
Law of demeter
26. Ways to express the system's subsystems and their relationship
Fully- dressed use case
architectural design
intellectual property
long method
27. Freezing the state of the source code at a particular point
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Lexer
brief use case
Versioning
28. Lack of errors in code - readability etc
Denormalization
duplicated code
long parameter list
Code Quality
29. Each condition is covered twice (true - false)
duplicated code
Database normalization
branch
Test- driven development
30. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Closure
black box testing
Programming syntax
31. Each line of code is covered once
path
jquery
statement
Closure
32. Test cases made -> code compiles -> make code pass
black box testing
Test- driven development
Lifecycle
Programming style
33. Series of phases through which software is developed
Lifecycle
sequence diagram
Design patterns
code smell
34. Tasks that a system must be able to perform
code smell
feature envy
Decorator pattern
Functional Requirements
35. Executes system in a manner that demands abnormal amounts of resources
Stress testing
Capacity testing
Anonymous function
Association
36. 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.
Test- driven development
copyright
Fully- dressed use case
Feasibility
37. The things a system must do
Test- driven development
Lazy initialization or Lazy loading (Design pattern)
inappropriate intimacy
Requirements
38. Diagram used to show how information flows around the system
Fully- dressed use case
system testing
long method
sequence diagram
39. Evaluates upper limits of operational parameters
Capacity testing
Casual use case
Performance testing
Code Quality
40. (smell) A class whose only purpose is to hold data
Maturity level
Data classes
message chain
white box testing
41. (smell) method has too many statements - loops or variables
long method
Phase
Casual use case
Use case diagram
42. Representational State Transfer.
Versioning
REST
SRS Documentation
shotgun surgery
43. Description of possible sequences of interactions between a user and the system.
copyright
Database normalization
Acceptance testing
use case
44. How well your fulfil your requirements
comments
trademark
Software Quality
jquery
45. (smell)class with too many instance variables or too much code
system testing
Large class
Lazy initialization or Lazy loading (Design pattern)
Constructor
46. Testing where modules are combined and tested as a group
Integration testing
Elicitation
Design Patterns
Parser
47. Word - logo or symbol used to distinguish one organization's wares and services from another's
duplicated code
trademark
a refactoring
Law of demeter
48. Verifies that system is protected against improper penetration
long parameter list
Security testing
patent
architectural design
49. Iterative - incremental framework for project management.
Versioning
Stakeholders
Scrum (Agile software development)
SRS Documentation
50. (smell) Smell deodorant
comments
Dijkstra's law
Scrum (Agile software development)
Capacity testing