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. Recognizable indicator that something may be wrong with code
statement
trademark
code smell
First- class citizen
2. 1st step of requirements gathering
intellectual property
Elicitation
code quality
feature envy
3. Models ->code work is done to keep models in sync with code
SOAP
Stakeholders
model- driven development
Security testing
4. Each line of code is covered once
Cowboy coding
statement
WSDL
shotgun surgery
5. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
shotgun surgery
Performance testing
regression testing
Design pattern
6. Diagram outlining the tasks that are going to be performed by the user
Recovery testing
Association
Use case diagram
Refactoring
7. A design pattern that allows behaviour to be added to an existing object dynamically.
Lambda
OOP
Decorator pattern
Large class
8. (smell) A method using another class more than its own
brief use case
Fully- dressed use case
Casual use case
feature envy
9. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Stakeholders
Lazy initialization or Lazy loading (Design pattern)
Lexer
Refactoring
10. Force software to fail in order to see how it recovers
Code Quality
Recovery testing
Stakeholders
architectural design
11. 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
Delegation
regression testing
Programming style
12. Ways to express the system's subsystems and their relationship
architectural design
system testing
jquery
long method
13. Object oriented programming; using objects to solve problems.
a refactoring
Dijkstra's law
OOP
Versioning
14. Single step in a lifecycle
Phase
Use case diagram
Integration testing
First- class citizen
15. Series of phases through which software is developed
Maturity
Association
Lifecycle
Dijkstra's law
16. Executes system in a manner that demands abnormal amounts of resources
Code Quality
Stress testing
Validation
Design Patterns
17. 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.
inappropriate intimacy
Feasibility
Association
SRS Documentation
18. (smell) Making one change requires changes in multiple places
Elicitation
architectural design
shotgun surgery
Closure
19. Improve the internal design and implementation of code without affecting external behavior
Validation
Refactoring
SRS Documentation
Lazy initialization or Lazy loading (Design pattern)
20. Evaluates upper limits of operational parameters
sequence diagram
jquery
Integration testing
Capacity testing
21. Formal document outlining a task that needs to be performed on a system
Programming syntax
Algorithm
jquery
Fully- dressed use case
22. Each possible path through the code is covered
path
feature envy
statement
Algorithm
23. (smell) A class whose only purpose is to hold data
Validation
Data classes
Security testing
Stakeholders
24. How developed code is (testing - documentation etc)
a refactoring
statement
Maturity level
Design
25. 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
26. A few sentences summarizing a use case
intellectual property
middle man
brief use case
Constructor
27. (smell) method has too many statements - loops or variables
Dijkstra's law
long method
jquery
Recovery testing
28. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
SOP
SOAP
Stakeholders
data clumps
29. Techniques for composing objects to form larger structures
Design patterns
Algorithm
Dijkstra's law
WSDL
30. 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
branch
Delegation
Versioning
Lazy initialization or Lazy loading (Design pattern)
31. Freezing the state of the source code at a particular point
Versioning
use case
Maturity
Anonymous function
32. People who care about the outcome
SRS Documentation
Stakeholders
Casual use case
Maturity level
33. Absence of lifecycle
system testing
inappropriate intimacy
intellectual property
Cowboy coding
34. The rigorousness of the tests that are able to be placed on the code
Maturity
Denormalization
Liskov substitution principle
Semantic Web
35. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
Dijkstra's law
Use case diagram
software quality
36. (smell) Smell deodorant
path
Validation
comments
patent
37. How well your fulfil your requirements
WSDL
Scrum (Agile software development)
architectural design
Software Quality
38. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Database normalization
Delegation
Decorator pattern
39. Developing a plan for a product - system or component. 'how' a system should perform a task
use case
Design
black box testing
Fully- dressed use case
40. Reusable - abstract 'blocks' of design
data clumps
Design Patterns
Programming style
duplicated code
41. The rights governing the ownership and disposition of technology
intellectual property
patent
duplicated code
Programming style
42. Testing tactic that looks at all ways that data can flow through the code
Lexer
Recovery testing
white box testing
WSDL
43. Contract between inventor - assignee and state giving a time and geographically limited monopoly
statement
message chain
patent
Specification
44. 4th step of requirements gathering
use case
Validation
Stress testing
trademark
45. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
regression testing
Denormalization
Design pattern
path
46. Representational State Transfer.
Algorithm
intellectual property
black box testing
REST
47. 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
48. A relationship between objects.
unit testing
duplicated code
regression testing
Association
49. Test whether or not tasks can be accomplished efficiently by all levels of users
Maturity level
Liskov substitution principle
software quality
Usability testing
50. Each condition is covered twice (true - false)
Security testing
Design pattern
architectural design
branch