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. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Denormalization
jquery
middle man
Algorithm
2. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Parser
middle man
Denormalization
Test- driven development
3. (smell) method has too many statements - loops or variables
Elicitation
long method
Recovery testing
Lifecycle
4. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
Cowboy coding
Requirements
Lexer
5. Tasks that a system must be able to perform
path
Quality metrics
model- driven development
Functional Requirements
6. How well your fulfil your requirements
brief use case
jquery
Design patterns
Software Quality
7. Testing where modules are combined and tested as a group
Stakeholders
intellectual property
Integration testing
REST
8. Derived methods should not assume more or deliver less
use case
Liskov substitution principle
Maturity level
black box testing
9. The rigorousness of the tests that are able to be placed on the code
Requirements
Maturity
architectural design
First- class citizen
10. Evaluates upper limits of operational parameters
technical managerial approach
Capacity testing
feature envy
jquery
11. Testing tactic that looks at all ways that data can flow through the code
Dijkstra's law
Lazy initialization or Lazy loading (Design pattern)
black box testing
white box testing
12. Constraints on the design due to external factors
Integration testing
Performance testing
Lambda
Non - functional Requirements
13. Testing the whole system for functionality
Law of demeter
system testing
Stress testing
Lazy initialization or Lazy loading (Design pattern)
14. Comprehensive description of software's intended purpose
SRS Documentation
Capacity testing
Constructor
a refactoring
15. Contract between inventor - assignee and state giving a time and geographically limited monopoly
WSDL
Capacity testing
patent
Requirements
16. 2nd step of requirements gathering
Analysis...
Software Quality
REST
Closure
17. Formal testing against end user specifications
WSDL
path
message chain
Acceptance testing
18. 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.
trademark
Large class
Fully- dressed use case
First- class citizen
19. Series of phases through which software is developed
Law of demeter
software quality
OOP
Lifecycle
20. (smell)class with too many instance variables or too much code
Large class
long method
Association
Lambda
21. Approach to team management that splits management up into two people with separate tasks
shotgun surgery
technical managerial approach
Analysis...
SOP
22. Reusable - abstract 'blocks' of design
conflict
Design pattern
Lazy initialization or Lazy loading (Design pattern)
Design
23. How developed code is (testing - documentation etc)
Stress testing
Large class
Maturity level
Decorator pattern
24. Diagram used to show how information flows around the system
technical managerial approach
Delegation
sequence diagram
message chain
25. A way to automatically grade code based on heuristics
use case
Scrum (Agile software development)
Database normalization
Quality metrics
26. Each line of code is covered once
Data classes
Database normalization
statement
feature envy
27. (smell) code is repeated in multiple places
duplicated code
Programming style
Stakeholders
Quality metrics
28. (smell) A class whose only purpose is to hold data
Data classes
Functional Requirements
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Requirements
29. A design pattern that allows behaviour to be added to an existing object dynamically.
Dijkstra's law
Refactoring
WSDL
Decorator pattern
30. 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.
Programming syntax
Software Quality
code smell
regression testing
31. (smell) Smell deodorant
Performance testing
software quality
Test- driven development
comments
32. Iterative - incremental framework for project management.
Quality metrics
architectural design
Scrum (Agile software development)
intellectual property
33. The rights governing the ownership and disposition of technology
black box testing
intellectual property
Lambda
Functional Requirements
34. A computer program that divides code up into functional components
comments
Decorator pattern
Parser
Maturity level
35. People who care about the outcome
Acceptance testing
Stakeholders
Usability testing
Anonymous function
36. 4th step of requirements gathering
Validation
Lexer
duplicated code
Recovery testing
37. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Design patterns
REST
Algorithm
Lifecycle
38. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Anonymous function
Scrum (Agile software development)
copyright
Recovery testing
39. 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
40. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
Functional Requirements
Refactoring
Algorithm
41. Force software to fail in order to see how it recovers
Design Patterns
Recovery testing
Requirements
long parameter list
42. One or two paragraphs of text outlining a use case
Elicitation
Stakeholders
brief use case
Casual use case
43. Figuring out what the requirements are
Recovery testing
Performance testing
Elicitation
Dijkstra's law
44. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Data classes
Lazy initialization or Lazy loading (Design pattern)
Integration testing
Parser
45. Testing that verifies that individual units of source code are working
comments
Scrum (Agile software development)
unit testing
Quality metrics
46. Single step in a lifecycle
trademark
Phase
patent
Recovery testing
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. The degree to which code is free of defects
Software Quality
white box testing
code quality
shotgun surgery
49. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
software quality
code quality
use case
50. Word - logo or symbol used to distinguish one organization's wares and services from another's
Functional Requirements
Software Quality
Programming syntax
trademark