Suborbital-Systems-Public/ReadySetGit
3
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

fix GFM links

Browse Source
This commit is contained in:
William Sandner
2018-08-14 17:55:05 +02:00
parent b9a83ae836
commit 154f9e132a
31 changed files with 196 additions and 239 deletions
Download Patch File Download Diff File Expand all files Collapse all files

70
QA-Plan.md
View File

@@ -44,9 +44,9 @@ those answers that do not apply.*
- QA plan > [System test runs](test-run-suite.html)
##### Related Documents:
- [Software Requirements Specification](srs.html)
- [Design](design.html)
- [Project plan](plan.html)
- [Software Requirements Specification](SRS)
- [Design](Design)
- [Project plan](Project-Plan)
- [Software development methodology](sdm.html)
- ::LINKS TO RELEVANT STANDARDS
- ::LINKS TO OTHER DOCUMENTS
@@ -58,7 +58,7 @@ strategies for assuring that those goals have been met, and details a
plan of action to carry out those strategies.
### Introduction
 
#### Why is this QA plan needed?
::"Quality" refers to all the good things that we would like to see in
@@ -118,33 +118,33 @@ activities:
that make sense for your project on this particular release.*
- ::Essential
- [Functionality > Correctness](glossary-std.html#functionality_gt_correctness)
- [Functionality > Robustness](glossary-std.html#functionality_gt_robustness)
- [Functionality > Correctness](Glossary-Std#functionality_gt_correctness)
- [Functionality > Robustness](Glossary-Std#functionality_gt_robustness)
- ::Expected
- [Functionality > Accuracy](glossary-std.html#functionality_gt_accuracy)
- [Functionality > Compatibility](glossary-std.html#functionality_gt_compatibility)
- [Functionality > Factual correctness](glossary-std.html#functionality_gt_factual_correctness)
- [Usability > Understandability and Readability](glossary-std.html#usability_gt_understandability_and_readability)
- [Usability > Learnability and Memorability](glossary-std.html#usability_gt_learnability_and_memorability)
- [Usability > Task support](glossary-std.html#usability_gt_task_support)
- [Usability > Efficiency](glossary-std.html#usability_gt_efficiency)
- [Usability > Safety](glossary-std.html#usability_gt_safety)
- [Usability > Consistency and Familiarity](glossary-std.html#usability_gt_consistency_and_familiarity)
- [Usability > Subjective satisfaction](glossary-std.html#usability_gt_subjective_satisfaction)
- [Security](glossary-std.html#security)
- [Functionality > Accuracy](Glossary-Std#functionality_gt_accuracy)
- [Functionality > Compatibility](Glossary-Std#functionality_gt_compatibility)
- [Functionality > Factual correctness](Glossary-Std#functionality_gt_factual_correctness)
- [Usability > Understandability and Readability](Glossary-Std#usability_gt_understandability_and_readability)
- [Usability > Learnability and Memorability](Glossary-Std#usability_gt_learnability_and_memorability)
- [Usability > Task support](Glossary-Std#usability_gt_task_support)
- [Usability > Efficiency](Glossary-Std#usability_gt_efficiency)
- [Usability > Safety](Glossary-Std#usability_gt_safety)
- [Usability > Consistency and Familiarity](Glossary-Std#usability_gt_consistency_and_familiarity)
- [Usability > Subjective satisfaction](Glossary-Std#usability_gt_subjective_satisfaction)
- [Security](Glossary-Std#security)
- ::Desired
- [Reliability > Consistency under load](glossary-std.html#reliability_gt_consistency_under_load)
- [Reliability > Consistency under concurrency](glossary-std.html#reliability_gt_consistency_under_concurrency)
- [Reliability > Availability under load](glossary-std.html#reliability_gt_availability_under_load)
- [Reliability > Longevity](glossary-std.html#reliability_gt_longevity)
- [Efficiency](glossary-std.html#efficiency)
- [Scalability](glossary-std.html#scalability)
- [Scalability > Performance under load](glossary-std.html#scalability_gt_performance_under_load)
- [Scalability > Large data volume](glossary-std.html#scalability_gt_large_data_volume)
- [Operability](glossary-std.html#operability)
- [Maintainability > Understandability](glossary-std.html#maintainability_gt_understandability)
- [Maintainability > Evolvability](glossary-std.html#maintainability_gt_evolvability)
- [Maintainability > Testability](glossary-std.html#maintainability_gt_testability)
- [Reliability > Consistency under load](Glossary-Std#reliability_gt_consistency_under_load)
- [Reliability > Consistency under concurrency](Glossary-Std#reliability_gt_consistency_under_concurrency)
- [Reliability > Availability under load](Glossary-Std#reliability_gt_availability_under_load)
- [Reliability > Longevity](Glossary-Std#reliability_gt_longevity)
- [Efficiency](Glossary-Std#efficiency)
- [Scalability](Glossary-Std#scalability)
- [Scalability > Performance under load](Glossary-Std#scalability_gt_performance_under_load)
- [Scalability > Large data volume](Glossary-Std#scalability_gt_large_data_volume)
- [Operability](Glossary-Std#operability)
- [Maintainability > Understandability](Glossary-Std#maintainability_gt_understandability)
- [Maintainability > Evolvability](Glossary-Std#maintainability_gt_evolvability)
- [Maintainability > Testability](Glossary-Std#maintainability_gt_testability)
### QA Strategy
@@ -277,7 +277,7 @@ and tracked to completion.*
[SDM](sdm.html#issuetracking).
### QA-Plan Checklist
 
#### Do the selected activities in the QA Strategy provide enough assurance that the project will meet it's quality goals?
::Yes, if all activities are carried out as planned, we are confident
@@ -291,10 +291,10 @@ and tracked to completion.*
#### Have human resources been allocated to carry out the QA activities?
::Yes, human resources have been allocated. They are listed in the
[Resource Needs](resource-needs.html) document.
[Resource Needs](Resource-Needs) document.
::No, human resources have not been allocated. They are listed as
"pending" in the [Resource Needs](resource-needs.html) document.
"pending" in the [Resource Needs](Resource-Needs) document.
#### Have machine and software resources been allocated as needed for the QA activities?
@@ -302,10 +302,10 @@ and tracked to completion.*
already allocated to them.
::Yes, a QA Lab has been set up. The needed machine and software
resources are listed in the [Resource Needs](resource-needs.html) document.
resources are listed in the [Resource Needs](Resource-Needs) document.
::No, needed machine and software resources are listed as pending in
the [Resource Needs](resource-needs.html) document.
the [Resource Needs](Resource-Needs) document.
#### Has this QA Plan been communicated to the development team and other stakeholders?
@@ -318,7 +318,7 @@ is welcome.
::No, some developers are not aware of the quality goals and planned
QA activities for this release. This is a risk that is noted in the
[Risk Management](plan.html#risks) section of the [Project Plan](plan.html).
[Risk Management](plan.html#risks) section of the [Project Plan](Project-Plan).
<!-- End Markdown content -->