top - download
⟦4007648c7⟧ Wang Wps File
Length: 23083 (0x5a2b)
Types: Wang Wps File
Notes: QAP
Names: »0071A «
Derivation
└─⟦83a4a04d1⟧ Bits:30005815 8" Wang WCS floppy, CR 0002A
└─ ⟦this⟧ »0071A «
WangText
8…0b…8…01…8…86…1
…02…
…02… …02…
…02…HAWK/amc/QAP/001/CRA
…02…SVO/800614…02……02…#
SOFTWARE
QUALITY
ASSURANCE
PLAN
…02……02…HAWK
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ........................................
1.1 Purpose ..................................
1.2 Major Quality Aspects ....................
1.2.1 Conformance ..........................
1.2.2 Credibility ..........................
…02……02……02…1.2.3 Reliability ..........................
…02……02……02…1.2.4 Maintainability ......................
2 ORGANISATION .................................
2.1 Quality Assurance Department .............
2.1.1 Quality Assurance Manager ............
2.2 Responsibility Sharing ...................
2.2.1 Surveillance by QAD ..................
2.2.2 Implementation and Follow-UP .........
2.2.3 Independence of QAD ..................
2.3 QA Access ................................
2.4 QA Relation to Subcontractors ............
2.5 Purchaser Supplied Material ..............
2.6 Products from other Supplier .............
3 PLANS ........................................
…02…3.1 General ..................................
3.2 QA Participation .........................
3.3 Description of Plans .....................
3.3.1 Project Implementation Plan ..........
3.3.2 Quality Assurance Plan ...............
3.3.3 Configuration Management Plan ........
3.3.4 Verification Plan ...................
4 STANDARDS ....................................
4.1 General ..................................
4.2 QA Participation .........................
4.3 Description of Standards .................
4.3.1 Documentation standard ...............
4.3.2 Coding standard ......................
4.3.3 Verification standard ................
4.3.4 Procedural standard ..................
5 REVIEWS ......................................
5.1 General ..................................
5.2 QA Participation in Reviews ..............
5.2.1 Planning Reviews .....................
5.2.2 Participation in Reviews .............
5.3 Description of Review ....................
5.3.1 Requirements Review ..................
…02……02……02…5.3.2 Preliminary Design Review ............
5.3.3 Detailed Design Review ...............
5.3.4 Verification Review(s) ...............
6 VERIFICATION .................................
6.1 General ..................................
6.2 QA Participation .........................
6.2.1 QA Participation in Planning .........
6.2.2 QA Participation in Verification .....
7 AUDITS ........................................
7.1 General ...................................
7.2 Access to Audit ...........................
7.3 Qad's Duty to Audit .......................
8 REPORTS .......................................
8.1 General ...................................
8.2 Detailed Reports ..........................
8.2.1 Review Reports .......................
8.2.2 Audit Reports .........................
8.2.3 Verification Report ...................
8.3. Summary Reports ..........................
8.4 Final Reports .............................
1 S̲C̲O̲P̲E̲
1.1 P̲u̲r̲p̲o̲s̲e̲
The purpose of this plan is to establish a systematic
pattern of all actions necessary to assure that software
products developed by the HAWK/amc project team to
the quality metric required for the product.
To assure the quality of a software product properly,
it is necessary to involve special measures in all
phases and aspects of a development project.
This plan will describe in detail which steps shall
be taken in each phase of the projects.
1.2 M̲a̲j̲o̲r̲ ̲Q̲u̲a̲l̲i̲t̲y̲ ̲A̲s̲p̲e̲c̲t̲s̲
The major characteristics of a software product for
which a quality level must be assured are as follows:
1.2.1 C̲o̲n̲f̲o̲r̲m̲a̲n̲c̲e̲
The product must conform to all requirements established
for the product.
- This comprise both basic requirement specification
and standards and procedures specified. A product
must also conform to all selfimplied requirements.
- The quality assurance measures used for this aspect
are
- reviews
- audits
- configuration control
- test
- improved implementation procedures
1.2.2 C̲r̲e̲d̲i̲b̲i̲l̲i̲t̲y̲
The purchasers confidence in the product's ability
to perform as required must be established.
- This is obtained through the overall activities
of the quality assurance program through providing
visibility into the implementation of the product.
- in particular
- customer participation in reviews
- implementation procedures giving visibility
- understandable documentation
- understandable test reports
1.2.3 R̲e̲l̲i̲a̲b̲i̲l̲i̲t̲y̲
For most software products it is necessary to assure
their ability to continue performance after delivery.
It may be required that this ability is maintained
even under operating conditions more difficult than
normal for the product.
This can be assured through
- a structured modular design
- extensive testing
- build in error detection
1.2.4 M̲a̲i̲n̲t̲a̲i̲n̲a̲b̲i̲l̲i̲t̲y̲
A software product is probable to contain errors even
after the most careful implementation and testing.
When those errors are detected during use it must be
easy to correct them.
It may also be found necessary to change the functions
of a product due to experience or development of new
requirements, such changes must be easy to implement.
This is assured through
- a structured modular design
- understandable documentation
- understandable commented code
2 O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
2.1 Q̲u̲a̲l̲i̲t̲y̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲D̲e̲p̲a̲r̲t̲m̲e̲n̲t̲
An independent Quality Assurance Department within
the company is responsible for the implementation of
the product assurance programme outlined in this plan.
2.1.1 Q̲u̲a̲l̲i̲t̲y̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲
The Quality Assurance Department (hereafter called
QAD) shall be headed by a Quality Assurance Manager
(QAM) who refers directly to the Division Manager.
The QAM shall have no responsibility towards management
of other departments or project managements.
2.2 R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲y̲ ̲S̲h̲a̲r̲i̲n̲g̲
The responsibility for the implementation of this plan
is shared between QAD and project manager as follows:
2.2.1 S̲u̲r̲v̲e̲i̲l̲l̲a̲n̲c̲e̲ ̲b̲y̲ ̲Q̲A̲D̲
The QAD will be limited in responsibility to survey
all activities within the project in accordance with
this plan and to report on any findings as described
in chapter 9.
2.2.2 I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲F̲o̲l̲l̲o̲w̲-̲U̲p̲
It will be the responsibility of the project management
to implement the product in a way compatible with rules
established in or derived from this plan.
It is also the responsibility of the project management
to take any follow-up action necessary to remedy descrepancies
reportes by QAD.
2.2 3 I̲n̲d̲e̲p̲e̲n̲d̲e̲n̲c̲e̲ ̲o̲f̲ ̲Q̲A̲D̲
No personnel employed by QAD will ever take part in
any work directly connected with the implementation
of a product nor in work for other departments indirectly
connected to this implementation.
This is necessary to assure a proper distinction between
the implementation of a product and the QA surveillance
of the product.
2.3 Q̲A̲ ̲A̲c̲c̲e̲s̲s̲
The personnel of QAD shall at all times have free access
to all material pertinent to the project.
It is the responsibility of the project management
to establish such procedures in the implementation
as necessary to assure this free access.
2.4 Q̲A̲ ̲R̲e̲l̲a̲t̲i̲o̲n̲ ̲t̲o̲ ̲S̲u̲b̲c̲o̲n̲t̲r̲a̲c̲t̲o̲r̲s̲
If part of the project is delegated to a subcontractor
the subcontract shall contain such clauses necessary
to make this plan applicable to the subcontractor.
Particularly, it is important to assure the free access
for QAD to project pertinent material residing at the
subcontractor.
If the subcontractor implements his own QA program
it shall be possible for QAD to audit this activity
as found necessary.
QAD may if subcontractors QA is satisfactory delegate
its authority to this function but QAD will still have
the full responsibility for this activity.
2.5 P̲u̲r̲c̲h̲a̲s̲e̲r̲ ̲S̲u̲p̲p̲l̲i̲e̲d̲ ̲M̲a̲t̲e̲r̲i̲a̲l̲
QAD shall implement the same procedures such as incoming
inspection, storage and maintenance of the purchaser
supplied material as provided for all other equipment.
Furthermore, QAD shall report promptly to the purchaser
any damage or discrepancy discovered. See procedure
in Handling of Purchaser Supplied Material.
2.6 P̲r̲o̲d̲u̲c̲t̲s̲ ̲f̲r̲o̲m̲ ̲o̲t̲h̲e̲r̲ ̲S̲u̲p̲p̲l̲i̲e̲r̲s̲
Equipment supplied by oems not quoted as subcontractors
- i.e. standard equipment from stock - is chosen in
accordance with the requirements stated compared to
the specifications given by the oem's.
QAD shall check and ensure that the quality of such
equipment fulfill all requirements in respect of
- performance (in accordance with specifications
given by manufacturer)
- durability
- stability under extreme working conditions
- maintainability.
3 P̲L̲A̲N̲S̲
3.1 G̲e̲n̲e̲r̲a̲l̲
For each project a set of plans describing the planned
implementation of the project shall exist.
As the methods of implementation have great influence
on the basic quality aspects of the produced software
the plans shall take proper consideration to this influence.
It is the responsibility of the project management
to establish such plans as early in the project lifecycle
as possible.
3.2 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲
QAD shall survey the establishment of those plans and
review the final result.
QAD will evaluate the plans with respect to the plans
influence on the quality of the product and with respect
to the plans influence on possibility of performing
the QA functions during the project life time. This
evaluation will result in a report describing QAD's
opinion on the quality of the plans.
3.3 D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲l̲a̲n̲s̲
The actual number of plans and their contents will
be individual for each project on the characteristics
and size of the project, but the following aspects
of planning shall be contained as a minimum.
3.3.1 P̲r̲o̲j̲e̲c̲t̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲
Shall provide description of methods to be used in
the software development, the division of the development
in phases and shall define major milestones where reviews
will be held.
3.3.2 Q̲u̲a̲l̲i̲t̲y̲ ̲A̲s̲s̲u̲r̲a̲n̲c̲e̲ ̲P̲l̲a̲n̲
This Plan defines Quality Assurance for the project.
3.3.3 C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲P̲l̲a̲n̲
Shall define and identify baselining of product at
major milestones. The establishment and maintenance
of controlled libraries, and the change control procedure
to be employed.
3.3.4 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲l̲a̲n̲
Shall contain a detailed definition of all verification
efforts, including writing of test procedures, performance
of test, and reporting of test results. The extend
and level of details of the verification shall be defined.
4. S̲T̲A̲N̲D̲A̲R̲D̲S̲
4.1 G̲e̲n̲e̲r̲a̲l̲
The manuals describing standards for S/W work within
the company shall be used by the project.
These standards contain detailed description of the
extension of work necessary to obtain a high quality
of the product.
It is the responsibility of the project management
to produce output conforming to these standards.
4.2 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲ ̲
All standards manuals shall be established and maintained
under the joint responsibility of QAD and other departments
with general authority concerning work within the company.
4.3 D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲t̲a̲n̲d̲a̲r̲d̲s̲
As a minimum the following standards shall be contained
in the company's standards manuals.
4.3.1 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲s̲t̲a̲n̲d̲a̲r̲d̲.̲
Shall contain a detailed definition of format and content
of all documents containing description of the products.
4.3.2 C̲o̲d̲i̲n̲g̲ ̲s̲t̲a̲n̲d̲a̲r̲d̲
Shall contain description of the format to be used
writing source code, the format and amount of comments
in code, and all restrictions on the programming language
used.
4.3.3 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲s̲t̲a̲n̲d̲a̲r̲d̲
Shall describe in detail all general procedures to
be used in software verification, all standard methods
of verification, and formats of test procedure and
reports.
4.3.4 P̲r̲o̲c̲e̲d̲u̲r̲a̲l̲ ̲s̲t̲a̲n̲d̲a̲r̲d̲
Shall describe all standardized procedures generally
applicable to software development work.
5̲ ̲ ̲R̲E̲V̲I̲E̲W̲S̲
5.1 G̲e̲n̲e̲r̲a̲l̲
The project implementation plan shall contain a split
of the implementation effort into several phases.
At the end of each phase the partial product produced
shall be reviewed in a formal way.
By inspecting the partial product thoroughly it is
assured that the quality metric for the product is
met at the time of the review, preventing errors to
be carried over to following phases.
It is the responsibility of project management to organize
such reviews in accordance with plans and make all
pertinent material available to participants.
5.2 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲ ̲i̲n̲ ̲R̲e̲v̲i̲e̲w̲s̲
5.2.1 P̲l̲a̲n̲n̲i̲n̲g̲ ̲R̲e̲v̲i̲e̲w̲s̲
QAD will survey the planning of reviews as well as
their inclusion in the overall plans of the project,
their proper schedules, and the organization of the
individual review.
5.2.2 P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲ ̲i̲n̲ ̲R̲e̲v̲i̲e̲w̲s̲
QAD will participate actively in all reviews, thoroughly
examining all available material.
All identified discrepancies between the product and
its quality metric will be contained in a report issued
by QAD.
5.3 D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲v̲i̲e̲w̲s̲
The following major points in the life time of a software
product will normally be considered end of a development
phase where a review is established.
5.3.1 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲R̲e̲v̲i̲e̲w̲
The requirements specifications are reviewed with particular
emphases on
- document format and organisation of content
- proper breakdown into elementary requirements
- proper identification of elementary requirements
- preciseness of requirement definitions
- implementability and testability
- consistency among requirements
5.3.2 P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲D̲e̲s̲i̲g̲n̲ ̲R̲e̲v̲i̲e̲w̲
Design Specifications are reviewed with emphasis on
- conformance to requirements
- proper modular breakdown of overall design
- completeneses of intermodule interface specifications.
5.3.3 D̲e̲t̲a̲i̲l̲e̲d̲ ̲D̲e̲s̲i̲g̲n̲ ̲R̲e̲v̲i̲e̲w̲
Detailed Design Specifications are reviewed with emphasis
on
- conformance to requirements, ICD's and standards
- proper modular breakdown until lowest levels
- proper level of detail to allow coding
- document format (conformance to standard)
- consistency among modules
- possible design flaws, mistakes, etc.
5.3.4 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲R̲e̲v̲i̲e̲w̲(̲s̲)̲
Dependant on the size and importance of the project
it may be necessary to split this review in several
phases. The Verification Plan produced in the planning
phase of a project are reviewed with emphasis on
- does a proper schedule for verification activities
exist
- are sufficient time and personnel allocated to
verification activities
- are production of Test procedures scheduled
- are performance of Test scheduled
- are production of Test reports scheduled
- are other verification activities than test scheduled
- are review(s) of verification scheduled.
The Test Specifications are reviewed with respect to
- document format and conformance to standard
- does test verify requirements properly
- are test level and extend sufficient
- are specification readable and practically useful.
The performance of tests must be witnessed by QA to
assure that
- Tests are performed according to specifications
- Test results are properly recorded
- Output related to the test are retained and marked.
The Test results must finally be reviewed with respect
to
- actually used input data
- are results in accordance with expected results
- are reports properly produced
- do reports conform to standards
- are proper actions initiated for handling discrepancies.
Other verification activities such as analysis of items
not suitable for testing will result in documentation
which is reviewed with respect to
- document format and conformance to standard
- completeness of activities in question
- completeness of documentation of these activities
- does activity verify requirements properly.
6̲ ̲ ̲V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲
6.1 G̲e̲n̲e̲r̲a̲l̲
Verification is all efforts (mainly tests) made throughout
the development of a software product in order to prove
the products ability to perform the required function.
This effort is essential in establishing the credibility
of the product and has a great role in showing product
conformance and reliability.
It is the responsibility of the project manager to
plan, perform and document the verification in accordance
with all applicable requirements and standards.
6,2 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲
6.2.1 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲ ̲i̲n̲ ̲P̲l̲a̲n̲n̲i̲n̲g̲
QAD will survey the planning of verification to assure
that the planning comprises a sufficient verification.
6.2.2 Q̲A̲ ̲P̲a̲r̲t̲i̲c̲i̲p̲a̲t̲i̲o̲n̲ ̲i̲n̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
QAD will review all produced test procedures and will
witness the actual performance of the tests.
All tests will result in test reports and all other
verification efforts in proper documentation. Such
reports and documents will be reviewed thoroughly by
QAD.
All observations during this effort will be contained
in a report from QAD.
7 A̲U̲D̲I̲T̲S̲
7.1 G̲e̲n̲e̲r̲a̲l̲
Audits through which all material produced during a
project lifetime is thoroughly inspected or employed
methods are evaluated shall be used as a powerful means
of assuring the conformance of a product.
Audits can be employed at any time from the birth of
a project until its formal finalization.
7.2 A̲c̲c̲e̲s̲s̲ ̲t̲o̲ ̲A̲u̲d̲i̲t̲
QAD shall have free access to perform audits at any
time.
QAD shall have full authority to demand audits established
whenever it is found necessary. It shall be the responsibility
of project management to assure that all material is
available and to assure the assistance of the project
personnel as requested.
7.3 Q̲A̲D̲'̲s̲ ̲D̲u̲t̲y̲ ̲t̲o̲ ̲A̲u̲d̲i̲t̲ ̲
It is the responsibility of QAD that audits on project
methods and produced materiel are held to the extend
necessary to assure proper surveillance of the project
quality.
8 R̲E̲P̲O̲R̲T̲S̲ ̲
8.1 G̲e̲n̲e̲r̲a̲l̲
Reports describing the observations done during the
work will be the only direct output from QAD.
Such reports shall contain descriptions on how the
projects fulfill the required quality metrics.
Reports shall not be limited to, but will due to the
nature of the work, mainly describe identified discrepancies.
It is the responsibility of the project management
to respond properly on the reports.
8.2 D̲e̲t̲a̲i̲l̲e̲d̲ ̲R̲e̲p̲o̲r̲t̲s̲
Whenever QAD personnel have participated directly in
any activities a detailed report describing all findings
during that activity shall be issued.
8.2.1 R̲e̲v̲i̲e̲w̲ ̲R̲e̲p̲o̲r̲t̲s̲
For each Review in which QAD has participated will
be issued a detailed report describing:
- The material subject to review
- The general quality of the material with emphasis
on the points described under Reviews
- All discrepancies between the materiel and its
requirements
- Proposal for correcting action if necessary
- Proposal for general improvements (if applicable).
8.2.2 A̲u̲d̲i̲t̲ ̲R̲e̲p̲o̲r̲t̲s̲
Whenever an unscheduled Audit has taken place a detailed
report will be issued describing:
- The material subject to audit
- The general quality of the material
- All discrepancies between the material and its
requirements
- Proposal for corrective actins or improvements
as applicable.
8.2.3 V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲R̲e̲p̲o̲r̲t̲
As Quality Assurance activity puts special emphasis
on verification it also puts special emphasis on giving
a more detailed and complete report on all activities
conected with the verification. This report will also
include a conclusion from QA on the acceptability of
the verification.
8.3 S̲u̲m̲m̲a̲r̲y̲ ̲R̲e̲p̲o̲r̲t̲s̲
Summary reports describing the general status of a
project shall be issued by QAD at suitable times during
a project life time.
8.4 F̲i̲n̲a̲l̲ ̲R̲e̲p̲o̲r̲t̲s̲
At finalization of the project QAD shall issue a final
report describing the quality status of the product.
This report will be an official document establishing
QAD's position towards the product.
The final report shall conclude either rejection, acceptance
with reservation, or full acceptance of the product.
A̲P̲P̲E̲N̲D̲I̲X̲ ̲A̲
Cross reference between
a) NATO Software Quality Assurance Requirements (AQAP-13)
as received in draft.
and
b) Christian Rovsing A/S' Software Quality Assurance
Plan (HAWK/AMC/QAP/001/CRA)
Reference a) Reference b)
101 N/A
102 Scope 1. SCOPE
103 Applicability N/A
104 Not defined
201 Requirements, general 2. ORGANISATION
202 Organization 2. ORGANISATION
203 System Review N/A
204 Software Support
Tools, Techniques
and Methoddologies 1.2 Major Quality
Aspects
3.1 PLANS, General
3.3 Description
of Plans
4.1 STANDARDS, General
4.3 Description
of Standards
5. REVIEWS
7. AUDITS
8. REPORTS
205. Planning General
206. Work Instructions 3. PLANS
207. Configuration Man. Plan being prepared
agreement (CM) (3.3.3 Configuration
control plan)
208. Library Controls Included in configuration
management plan
209. Software Documentation 4.3 Description
of Standards
210. Reviews/Audits 5. REVIEWS
7. AUDITS
8. REPORTS
211. Testing 6. VERIFICATION
212. Corrective Action 6. VERIFICATION
8. REPORTS
213. Subcontractor Control 2.5 QA Relation
to Subcontractors.
214 Purchaser Supplied Materiel 2.6 Purchaser supplied
material
215 Preparation for Delivery 8.4 Final Reports
216 Accommodation and Assistance 2.4 QA Access
