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 Principles And Concepts
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. Service locator
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
A registry or directory that provides a lookup so the consumer can browse the services
A mediator - it connects the consumer with the service provider
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
2. Define operational profile
Consider risks of selected alternatives
Identify use cases - occurrence probability - Engineer Just Right reliability
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
3. Interaction styles
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Direct manipulations: Video games - Menu - Form Filling - Command languages - Natural languages
Make the decision
4. Software reliability
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Identify use cases - occurrence probability - Engineer Just Right reliability
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
The probability that a system or capability functions without failure for a specified time or number of natural units in a specified environment
5. Defect
Any flaw in the specification - design or implementation of a product.
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
Consider risks of selected alternatives
Generate test cases from operational profile - include low probability tests
6. Other approaches to make decisions exist besides DARS
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
It help individuals to perform better - it helps to improve processes.
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
7. Retrospective - lessons learned or project post- mortem
Make the decision
Is a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
It help individuals to perform better - it helps to improve processes.
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
8. Steps to apply DARS #2. Establish decision objectives
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
Establish how much time do we have to make de decision - what resources are available.
9. CMMI
Identify alternatives
Team members establish common goals and define roles - Team: develops strategy - defines a customize process - participates in producing the plan and everyone understands the role - negotiates with management on the plan and resources - members fo wo
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Its targeted for organizational capabilities - Organizations depend on teams to be mature and capable.
10. Steps to apply DARS #9
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
Requirements - Design - Test and Maintenance
Total value score - Sum of weights x values
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
11. Victor Basili GQM paradigm
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
Quantitative measures of the defree to which some component possess a given attribute. Combination of measures.
Goal: Well defined goalm a purpose - why are you doing this - Question: Based on the goal formulate questions to achieve the goal - Metric: Define metrics to answer the questions.
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
12. The documentation of process paterns
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
13. TSP
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Identify required and desired objectives.
14. PSP2
What kind of defects do I make in my own work - How can I make fewer mistakes - How can I identify more defects that I overlooked in the past
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
Rank desired objectives in a 1 to 10 scale
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
15. Root cause analysis...
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
To prepare a software quality assurance plan - Participate in the development of the project process descriptions and definitions - Review software activities to verify compliance with the processes - Work product audits to verify compliance with pro
Reduce repair or re work cause - eliminate high priority problems and reduce error type
16. Middle phase of IDEAL model
Is a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
A registry or directory that provides a lookup so the consumer can browse the services
17. Steps to perform a root cause analysis #4
Develop and evaluate proposed solutions to eliminte defect root causes
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
18. Guiding test
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
Do things in trial basis - pilot projects - collect information - analyze information - iterate
Implement solutions and evaluate the results
19. Steps to apply DARS #3. Classify objectives
Things that should no be doing - comes from lessons learned
Boundaries of services have to be explicit. Services are autonomous - standalone - do not have dependencies - Services share schema and contracts not classes and types. Platform neutral - Compatibility is policy based - policies define the contraints
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
Identify required and desired objectives.
20. Steps to apply DARS #7. Score alternatives against desired objectives
An application function packaged as a reusable component for use in some process - typically a business or application process.
Strategies that software professionals use to solve recurring problems. Consist of a collection of general techniques - actions and tasks being use to solve recurring problems in an organization.
Process failure data - Tracking reliability growth - specify how fault tolerant architectures work - They rely on redundancy - They are able to recover by moving to a future state or restore to known safe state.
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
21. Quality assurance disciplines
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
Implement solutions and evaluate the results
22. Steps to perform a root cause analysis #5
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Directive Approach: A leader makes the decision alone - Consultative Approach: A leader makes the decision with the advise from other people - Democratic Approach: Some key team members vote for the best decision - Consensus Approach: Everybody parti
Implement solutions and evaluate the results
23. Steps to apply DARS #6
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
24. The Six Sigma for software engineering process
Things that should no be doing - comes from lessons learned
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
A mediator - it connects the consumer with the service provider
They have to objective - unambiguous and tailored to meet the needs
25. Organizational pattern
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Whatever uses the service - it can be an application or another service
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
26. Benefits of SOA
Total value score - Sum of weights x values
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
An application function packaged as a reusable component for use in some process - typically a business or application process.
27. DARS
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
They have to objective - unambiguous and tailored to meet the needs
Generate test cases from operational profile - include low probability tests
Decision Analysis and Resolution Process. Is a well defined process to analyze possible decisions using formal evaluation process - it involves identifying criteria and evaluate alternatives. It helps to make decision objectively.
28. Benefits of project retrospectives
It help individuals to perform better - it helps to improve processes.
The extent that specific attributes of interest to the user are satisfied. It is defined in terms of attributes that are determined by the users.
A registry or directory that provides a lookup so the consumer can browse the services
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
29. Learning phase of IDEAL model
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
Is a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
Team hold a meeting to identify common root causes - common problems. Techniques such as Fishbone diagram are used in this phase to support the analysis.
30. Steps to apply DARS #8. Calculate a value score
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
From the common root causes identified in the previous meeting - the team select the ones that they will be addressing. The root causes selected will be usually the ones that cause a lot of the defects.
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Reviews - Test - Measurements - Analysis/Reporting - Process definition/Standards
31. Define product
A registry or directory that provides a lookup so the consumer can browse the services
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Initial - Identify and analyze what is the trigger to perform a particular insertion reliability - reduce cycle time - reduce cost - Context: How does this technology fits within the overall busines goals - Secure support: Management - executive - mo
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
32. Goals for root cause analysis...
Test alternatives against required objectives - Make sure the alternatives identified meet the required objectives - otherwise disregard them
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Reduce repair or re work cause - eliminate high priority problems and reduce error type
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
33. Steps to apply DARS #5
Integrated Product Team is a group of people that has complementary skills and expertise - fully empowered to represent stakeohlders - to make the appropriate decisions. A team of people that comes from different backgrounds - with different skillset
Task process patterns: Detailed steps to perform a task - Stage process patterns: Depict steps in a project stage - Phase process patterns: Depicts the interactions between stages process paterns
Identify alternatives
Requirements - Design - Test and Maintenance
34. PSP3
Similar to the documentation of a design pattern. Specify a Name - Intent (Intended use of pattern) - Type (Task - Stage - Phase) - Initial Contact (Situation where the pattern solution applies to) - Solution (How the pattern solve the intended probl
Select the defects that will be analyse by the team and define the goals for the root cause analysis activities
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
How to integrate - to perform effectively on a team - How can you become a better team player
35. Service provider
Learnability: How long does it take to learn the system - Speed of operation: How long does it take to complete a task - Robustness: Tolerance to errors - Recoverability: Ability to recover from errors - Adaptability: Being able to customize the inte
Identify use cases - occurrence probability - Engineer Just Right reliability
The one who implements the service - it can be a network addressable entity - it needs to be able to accept and execute requests from consumer - it needs to publish a service description in a service registry that contains the collection of service d
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
36. PSP
Reuse cycle time - costs - Interoperability - Scalabilty - Flexibility/Maintainability
Is a group activity conducted at the end of a project cycle - where team members share knowledge gathered during the development of a project. They basically identify what went wrong - what worked well - how can they improve what they are doing - mak
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
37. How OCL (Object Constraint Language) is used in the context of the uml
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Implement solutions and evaluate the results
It is a semi formal language - partly mathematical. UML cannot describe constraints on model objects. Addresses invariants which are expressions holding true. Defines preconditions that must be true at the start of a method execution and post conditi
It help individuals to perform better - it helps to improve processes.
38. Advantages and disadvantages of formal methods
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
Make the decision
Whatever uses the service - it can be an application or another service
39. PSP1
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Describe common management techniques or organizational structures. A way to capture best practices within an organization.
Is group reasoning process applied to defect information to develop organizational understanding of the causes of a particular class of defects. A group of people analyze a group of defects to try to understand the causes of these defect.
They eliminate contradiction - ambiguities - vagueness and incompleteness from normal language descriptions. The disasvantages are the time/effort needed - the complexity - there are interface issues - they are cumbersome.
40. Prepare tests
The individual establish a personal performance baseline - Recognize how you do your job - Document personal processing - Gather data on where do you spend your time - Gather data on the errors you make
Whatever uses the service - it can be an application or another service
How do we size - resource and schedule plans - How do we estimate - What is the estimation process?
Generate test cases from operational profile - include low probability tests
41. The McCall's triangle of quality
Product revision: Maintainability - testability - re- usability - Product transition: Move the product into a domain. Portability - Revisability - interoperability - Product operation: Correctness - reliability - usability - performance
Who are the customers - how are they gonna use the product - undestand the product - define possible failures - understand customer needs
Establish product and business goals - Assigning the roles of individuals within the team - Determine the development product strategy - Build top level plans - Develop quality plan - Conduct risk assesment - Team will prepare a management briefing -
Consider risks of selected alternatives
42. Ethic
How to integrate - to perform effectively on a team - How can you become a better team player
User familiarity - User diversity - Consistency throughout the interface - Minimum surprise - Recoverability - User guidance
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
The discipline dealing with what is good and bad. Moral duty and obligation. The principles of conduct governing and individual or group
43. IPPD
Identify required and desired objectives.
Try to achieve products with 3.4 defects per million opportunities - Define customer requirements - meet customer needs - know what the customer wants - Measure the process - collecting defect metrics - Analyze to determine causes - Improve. Eliminat
Integrated Product and Process development is a systematic approach that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs. It involves the use of cross functional teams - inte
Define product - Define operational profile - Define failures - Prepare tests - Execute tests
44. Some examples of formal methods implementations
Diagnosing: Characterize current state versus desired state - Recommended actions for the technology insertion Identify potential barriers: legacy code - processes - standards - contracts - Establishing:What are the different actions - develop a pla
Generate test cases from operational profile - include low probability tests
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
Identify required and desired objectives.
45. Antipattern
Evaluate the remaining alternatives against the desired objectives and set a score that will show how well this alternative satisfy our desired objectives
Things that should no be doing - comes from lessons learned
A mediator - it connects the consumer with the service provider
Any flaw in the specification - design or implementation of a product.
46. Steps to apply DARS #4. Value the desired objectives
Identify required and desired objectives.
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
Rank desired objectives in a 1 to 10 scale
Algebraic Specification: Using methods from algebra - OBJ - Low level specifications - Syntax = signature and Semantic part = axioms. Model oriented specification: The state of the system - operations over the states.
47. How to avoid those defects
Communicative failure - Missing or incomplete information - Oversight failure - Did not consider all the variables and left out important things - Education or lack of thereof - Lack of understanding - Typo - human error
Targeted for teams. The goal is to produce effective teams by selecting skilled teams or providing tools to improve their skills.
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
Targeted for individuals. Analyse how an individual is doing his job - identify where you are spending your time - what mistakes are you making and how to improve the way you do your work. What is your process? Where do you spend your time? How good
48. The measurement process
Establish liaison between groups - better processes and better documentation - do checklists - automated checking - work product templates and reviews - Training and staff- ins - Transcription - Tools for automated checking
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
For each of the alternatives calculate the weight of the alternatives x value of the criteria
Define the decision we are trying to make - what do we want to accomplish and what questions we will ask
49. Service Oriented Architecture
Formulation: Define proper metrics - Collection: Collect data on the metric - Analysis: Tools to look at data - charts - graphics - Interpretation: Gain insight - Feedback: Derive recommendations and take actions
How to integrate - to perform effectively on a team - How can you become a better team player
The approach to build distributed systems that deliver application functionality as services to end user applications or to build other services.
An approach to construct and prove that a program is correct. Apply mathematical and logical techniques to analyze a program. Apply to system specification and system implementations. Not used for validation but are tied to verification.
50. Role of a software quality assurance group
Intelectual property - use software without credit - develop tools that help people to violate intelectual property - Privacy: credit - health - personal information - Confidentiality - Quality of work
To prepare a software quality assurance plan - Participate in the development of the project process descriptions and definitions - Review software activities to verify compliance with the processes - Work product audits to verify compliance with pro
Focus on customer needs - Reduce costs - Helps to make better decisions - Reduce time - Reduce risks
Lessons learned - have we achieved the desired features? - recommendations for future technologies insertions
Sorry!:) No result found.
Can you answer 50 questions in 15 minutes?
Let me suggest you:
Browse all subjects
Browse all tests
Most popular tests
Major Subjects
Tests & Exams
AP
CLEP
DSST
GRE
SAT
GMAT
Certifications
CISSP go to https://www.isc2.org/
PMP
ITIL
RHCE
MCTS
More...
IT Skills
Android Programming
Data Modeling
Objective C Programming
Basic Python Programming
Adobe Illustrator
More...
Business Skills
Advertising Techniques
Business Accounting Basics
Business Strategy
Human Resource Management
Marketing Basics
More...
Soft Skills
Body Language
People Skills
Public Speaking
Persuasion
Job Hunting And Resumes
More...
Vocabulary
GRE Vocab
SAT Vocab
TOEFL Essential Vocab
Basic English Words For All
Global Words You Should Know
Business English
More...
Languages
AP German Vocab
AP Latin Vocab
SAT Subject Test: French
Italian Survival
Norwegian Survival
More...
Engineering
Audio Engineering
Computer Science Engineering
Aerospace Engineering
Chemical Engineering
Structural Engineering
More...
Health Sciences
Basic Nursing Skills
Health Science Language Fundamentals
Veterinary Technology Medical Language
Cardiology
Clinical Surgery
More...
English
Grammar Fundamentals
Literary And Rhetorical Vocab
Elements Of Style Vocab
Introduction To English Major
Complete Advanced Sentences
Literature
Homonyms
More...
Math
Algebra Formulas
Basic Arithmetic: Measurements
Metric Conversions
Geometric Properties
Important Math Facts
Number Sense Vocab
Business Math
More...
Other Major Subjects
Science
Economics
History
Law
Performing-arts
Cooking
Logic & Reasoning
Trivia
Browse all subjects
Browse all tests
Most popular tests