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 process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
intellectual property
Database normalization
Constructor
brief use case
2. Description of possible sequences of interactions between a user and the system.
sequence diagram
jquery
use case
Lifecycle
3. 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.
Lambda
message chain
First- class citizen
statement
4. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
feature envy
SOAP
Lexer
REST
5. Reusable - abstract 'blocks' of design
Constructor
code quality
Design pattern
Programming style
6. Testing tactic based on whether inputs and outputs match up for required functionality
patent
OOP
WSDL
black box testing
7. 'single dot rule'
Law of demeter
Casual use case
Software Quality
Functional Requirements
8. Absence of lifecycle
system testing
Analysis...
OOP
Cowboy coding
9. 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
Closure
Semantic Web
First- class citizen
long parameter list
10. (smell) If a set of variables are used together in multiple places
Large class
statement
Integration testing
data clumps
11. Tasks that a system must be able to perform
Recovery testing
conflict
duplicated code
Functional Requirements
12. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
middle man
copyright
Fully- dressed use case
13. Testing the whole system for functionality
Association
message chain
system testing
Requirements
14. Each possible path through the code is covered
OOP
Dijkstra's law
path
jquery
15. 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
16. Constraints on the design due to external factors
Validation
Closure
Non - functional Requirements
Design
17. Comprehensive description of software's intended purpose
technical managerial approach
Semantic Web
SRS Documentation
copyright
18. The rights governing the ownership and disposition of technology
intellectual property
Decorator pattern
Cowboy coding
branch
19. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Algorithm
Integration testing
jquery
white box testing
20. Derived methods should not assume more or deliver less
Refactoring
Lifecycle
black box testing
Liskov substitution principle
21. Freezing the state of the source code at a particular point
patent
statement
Versioning
Stress testing
22. Improve the internal design and implementation of code without affecting external behavior
Denormalization
feature envy
Refactoring
code quality
23. Object oriented programming; using objects to solve problems.
regression testing
data clumps
OOP
unit testing
24. (smell)class with too many instance variables or too much code
Software Quality
Scrum (Agile software development)
Programming style
Large class
25. People who care about the outcome
Phase
Lazy initialization or Lazy loading (Design pattern)
feature envy
Stakeholders
26. Test whether or not tasks can be accomplished efficiently by all levels of users
black box testing
Performance testing
Usability testing
feature- driven development
27. Formal testing against end user specifications
Large class
statement
Acceptance testing
Maturity level
28. A powerful motivator for change
Integration testing
conflict
Scrum (Agile software development)
Maturity level
29. The degree to which code is free of defects
code quality
First- class citizen
Programming syntax
white box testing
30. Reusable - abstract 'blocks' of design
Design Patterns
shotgun surgery
code quality
Stakeholders
31. 2nd step of requirements gathering
use case
Security testing
First- class citizen
Analysis...
32. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Anonymous function
Lexer
Programming style
Design Patterns
33. (smell) One class delegates all of its requests to another class
Stakeholders
REST
middle man
feature- driven development
34. Small - behaviour- preserving - source- to- source transformation
a refactoring
code smell
unit testing
REST
35. (smell) many parameters are being passed into a method
Law of demeter
Database normalization
long parameter list
Algorithm
36. A computer program that divides code up into functional components
Lifecycle
middle man
Parser
Algorithm
37. (smell) Classes using things that should be private in other classes
Stress testing
inappropriate intimacy
Code Quality
Cowboy coding
38. Figuring out what the requirements are
Elicitation
Decorator pattern
brief use case
duplicated code
39. A method that initializes a newly instantiated object
Acceptance testing
software quality
copyright
Constructor
40. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
SOP
regression testing
Maturity level
Lazy initialization or Lazy loading (Design pattern)
41. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
feature- driven development
Association
Anonymous function
regression testing
42. The things a system must do
Test- driven development
Lexer
Code Quality
Requirements
43. (smell) A class whose only purpose is to hold data
Specification
Data classes
white box testing
Software Quality
44. A way to automatically grade code based on heuristics
Security testing
Software Quality
Quality metrics
Delegation
45. Formal document outlining a task that needs to be performed on a system
Database normalization
Fully- dressed use case
statement
Anonymous function
46. Testing where modules are combined and tested as a group
Cowboy coding
Integration testing
Test- driven development
SOAP
47. Approach to team management that splits management up into two people with separate tasks
First- class citizen
Cowboy coding
technical managerial approach
Delegation
48. Each line of code is covered once
statement
Lifecycle
long method
brief use case
49. The rigorousness of the tests that are able to be placed on the code
WSDL
Dijkstra's law
Stakeholders
Maturity
50. 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
Algorithm
conflict
inappropriate intimacy
Delegation