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. People who care about the outcome
intellectual property
Software Quality
Stakeholders
Code Quality
2. Absence of lifecycle
Cowboy coding
Requirements
Security testing
unit testing
3. Improve the internal design and implementation of code without affecting external behavior
Refactoring
Cowboy coding
Parser
Use case diagram
4. Each line of code is covered once
statement
architectural design
code quality
Decorator pattern
5. 3rd step of requirements gathering
Refactoring
Algorithm
Liskov substitution principle
Specification
6. 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.
message chain
Programming syntax
Elicitation
Lifecycle
7. Contract between inventor - assignee and state giving a time and geographically limited monopoly
WSDL
patent
technical managerial approach
Fully- dressed use case
8. Formal document outlining a task that needs to be performed on a system
code smell
Large class
Fully- dressed use case
model- driven development
9. Test the run - time performance of the system
Phase
Performance testing
Large class
Capacity testing
10. Figuring out what the requirements are
Elicitation
technical managerial approach
black box testing
unit testing
11. (smell) A method using another class more than its own
Data classes
feature envy
Design patterns
Validation
12. 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
13. The rigorousness of the tests that are able to be placed on the code
Phase
software quality
Versioning
Maturity
14. Formal testing against end user specifications
Lexer
Test- driven development
WSDL
Acceptance testing
15. Testing tactic that looks at all ways that data can flow through the code
black box testing
Elicitation
white box testing
unit testing
16. 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
17. An operator used to denote anonymous functions or closures.
inappropriate intimacy
code quality
Specification
Lambda
18. Small - behaviour- preserving - source- to- source transformation
Liskov substitution principle
a refactoring
Functional Requirements
Decorator pattern
19. Reusable - abstract 'blocks' of design
Phase
Parser
Design pattern
feature envy
20. Object oriented programming; using objects to solve problems.
path
OOP
shotgun surgery
unit testing
21. A movement that promotes common formats for data.
SOP
Semantic Web
conflict
Dijkstra's law
22. 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.
message chain
Code Quality
Feasibility
intellectual property
23. 2nd step of requirements gathering
Cowboy coding
inappropriate intimacy
Analysis...
middle man
24. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
regression testing
Requirements
Usability testing
Decorator pattern
25. Test cases made -> code compiles -> make code pass
regression testing
a refactoring
Test- driven development
Dijkstra's law
26. The rights governing the ownership and disposition of technology
Dijkstra's law
Non - functional Requirements
intellectual property
Stress testing
27. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
Analysis...
REST
data clumps
28. 4th step of requirements gathering
Large class
Specification
feature- driven development
Validation
29. Comprehensive description of software's intended purpose
First- class citizen
SRS Documentation
Refactoring
Database normalization
30. (smell)class with too many instance variables or too much code
Large class
Quality metrics
Design pattern
Anonymous function
31. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
regression testing
Programming style
Elicitation
model- driven development
32. Executes system in a manner that demands abnormal amounts of resources
Stress testing
black box testing
intellectual property
Analysis...
33. Techniques for composing objects to form larger structures
Design patterns
Cowboy coding
code smell
Database normalization
34. Lack of errors in code - readability etc
Code Quality
Delegation
Semantic Web
Non - functional Requirements
35. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
SOP
jquery
Specification
Performance testing
36. (smell) method has too many statements - loops or variables
unit testing
Stress testing
long method
OOP
37. (smell) Making one change requires changes in multiple places
a refactoring
shotgun surgery
Capacity testing
middle man
38. Protecting the embodiment of an idea
Lexer
copyright
Usability testing
Software Quality
39. How developed code is (testing - documentation etc)
Lexer
Usability testing
Maturity level
statement
40. (smell) If a set of variables are used together in multiple places
system testing
code quality
data clumps
brief use case
41. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Association
Denormalization
long method
Code Quality
42. Diagram outlining the tasks that are going to be performed by the user
Versioning
Use case diagram
message chain
Cowboy coding
43. Ways to express the system's subsystems and their relationship
patent
WSDL
comments
architectural design
44. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
Versioning
shotgun surgery
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
45. Degree to which the system meets the specified requirements and development standards
Acceptance testing
software quality
Use case diagram
WSDL
46. Verifies that system is protected against improper penetration
Security testing
a refactoring
Liskov substitution principle
Non - functional Requirements
47. Testing tactic based on whether inputs and outputs match up for required functionality
Integration testing
black box testing
Closure
unit testing
48. Reusable - abstract 'blocks' of design
Design Patterns
WSDL
Stakeholders
intellectual property
49. Evaluates upper limits of operational parameters
Lambda
Capacity testing
Functional Requirements
Lexer
50. A method that initializes a newly instantiated object
Programming syntax
Integration testing
Constructor
white box testing