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 things a system must do
feature envy
Delegation
Requirements
Integration testing
2. The rights governing the ownership and disposition of technology
copyright
intellectual property
Design Patterns
Test- driven development
3. Reusable - abstract 'blocks' of design
long parameter list
Maturity
path
Design pattern
4. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
Capacity testing
Database normalization
Dijkstra's law
5. 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.
model- driven development
Database normalization
Feasibility
Requirements
6. A relationship between objects.
code smell
Quality metrics
Association
duplicated code
7. The rigorousness of the tests that are able to be placed on the code
Data classes
WSDL
black box testing
Maturity
8. Recognizable indicator that something may be wrong with code
middle man
Design Patterns
code smell
Liskov substitution principle
9. Small - behaviour- preserving - source- to- source transformation
unit testing
code smell
First- class citizen
a refactoring
10. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
system testing
Semantic Web
Scrum (Agile software development)
11. 4th step of requirements gathering
Security testing
data clumps
Validation
Semantic Web
12. Derived methods should not assume more or deliver less
Liskov substitution principle
Non - functional Requirements
a refactoring
Lifecycle
13. Description of possible sequences of interactions between a user and the system.
Phase
architectural design
use case
duplicated code
14. Protecting the embodiment of an idea
Casual use case
copyright
SOAP
brief use case
15. (smell) If a set of variables are used together in multiple places
jquery
sequence diagram
Design
data clumps
16. Models ->code work is done to keep models in sync with code
model- driven development
use case
path
Use case diagram
17. A design pattern that allows behaviour to be added to an existing object dynamically.
architectural design
Decorator pattern
Lifecycle
code smell
18. A computer program that divides code up into functional components
Parser
long parameter list
long method
Large class
19. (smell) code is repeated in multiple places
Stress testing
Delegation
Use case diagram
duplicated code
20. Improve the internal design and implementation of code without affecting external behavior
system testing
Database normalization
Refactoring
Dijkstra's law
21. Test the run - time performance of the system
Algorithm
Scrum (Agile software development)
Stakeholders
Performance testing
22. Object oriented programming; using objects to solve problems.
jquery
OOP
Liskov substitution principle
path
23. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Dijkstra's law
long parameter list
Constructor
Programming style
24. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
feature envy
Analysis...
SRS Documentation
jquery
25. Representational State Transfer.
Performance testing
REST
Use case diagram
Quality metrics
26. Each condition is covered twice (true - false)
patent
branch
Semantic Web
Specification
27. (smell) client needs to use one object to get another and then use that one to get another
statement
message chain
Maturity level
Dijkstra's law
28. People who care about the outcome
sequence diagram
Anonymous function
Analysis...
Stakeholders
29. How developed code is (testing - documentation etc)
Programming syntax
Maturity level
data clumps
software quality
30. Testing that verifies that individual units of source code are working
unit testing
Integration testing
Algorithm
Dijkstra's law
31. Approach to team management that splits management up into two people with separate tasks
SOAP
technical managerial approach
Specification
Delegation
32. A powerful motivator for change
conflict
Dijkstra's law
Stakeholders
Non - functional Requirements
33. (smell) One class delegates all of its requests to another class
Test- driven development
Large class
middle man
WSDL
34. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
SOP
SOAP
SRS Documentation
intellectual property
35. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
SOAP
Closure
Specification
36. Lack of errors in code - readability etc
Validation
feature envy
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Code Quality
37. Absence of lifecycle
statement
Data classes
long method
Cowboy coding
38. Reusable - abstract 'blocks' of design
Design Patterns
Design
long method
Programming syntax
39. Testing tactic that looks at all ways that data can flow through the code
Functional Requirements
Acceptance testing
architectural design
white box testing
40. Verifies that system is protected against improper penetration
shotgun surgery
white box testing
trademark
Security testing
41. Series of phases through which software is developed
data clumps
Lifecycle
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
path
42. A few sentences summarizing a use case
code quality
brief use case
Design pattern
Semantic Web
43. A method that initializes a newly instantiated object
Constructor
Specification
Code Quality
patent
44. Comprehensive description of software's intended purpose
regression testing
SRS Documentation
Dijkstra's law
copyright
45. 3rd step of requirements gathering
shotgun surgery
Specification
Algorithm
black box testing
46. A way to automatically grade code based on heuristics
Design Patterns
Quality metrics
Delegation
Constructor
47. Force software to fail in order to see how it recovers
Lazy initialization or Lazy loading (Design pattern)
Non - functional Requirements
Recovery testing
Integration testing
48. Diagram outlining the tasks that are going to be performed by the user
Lexer
Semantic Web
Use case diagram
Fully- dressed use case
49. (smell) Smell deodorant
use case
Fully- dressed use case
comments
Validation
50. 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.
Analysis...
First- class citizen
Maturity level
path