Crisis (1) Patch (2) Service Pack (3) New Version (5)

oduct Management
Research & DevelopmentQuality Assurance
1.1 1.3
1.2
Documentation Detailed Design Test Case Design

1.4
Detailed Design
Review

1.5
Coding

1.6
Code inspection

1.7 1.9
1.8
Knowledge Transfer
Document Review Review Test Case Review

1.10

Packaging for
testing
1.11
Map:

Smoke Test 1.12

Task With Spec
Testing
Task Without Spec
1.13

Review
Packaging & Release
1
 Test Case Design

Task 1.3

2. Scope
This description is a frame for setting the
manner of managing and executing the test
case design.

2. References
High Level Design Review

3. Purpose
To prepare a comprehensive tests document,
both in a high level and in detailed.

4. Description
The QA should participate the development
process from its beginning.
The high level design of the test cases should
start after the PDR; it will develop along with
the proceeding of the technical detailed
design.
The test cases will be based upon the
functional and technical specifications.
This process, will be done in a close
interaction with the PM and the development
and might result in documentation updates.
It is also the PM responsibility to supply to the
QA business scenarios which will become
part of the test cases.
At this stage the “Smoke Tests” are written.

2
5. Participants List
QA Manager
QA Team
Software Development Team Leader
PM

6. Responsibility
The QA manager has the responsibility to manage this process
and write the test cases. It is the PM and development
responsibility to assist in this mission and update the documents
under their responsibility, if needed.

7. Summary
The QA manager is responsible for writing the test cases, while
interacting with PM and development.

3
 Test Case Review Description

Task 1.9

2. Scope
This description is a frame for setting the
manner of managing and executing the test
case design review.

2. References
Test Case Design - task 1.3

3. Purpose
To review and approve the test cases design.

4. Description
The test case design review is a meeting which
takes place after completing the test case
design.
The test case design specification owner, in
this case, a QA team leader, is responsible for
the summon of the review meeting.
Before the meeting, the responsible party will
distribute the relevant reference material, in
order for the participants to arrive prepared.
The meeting will include a high level
description by the QA manager and then focus
on question of the participates.
At the end of this review the “Smoke Tests” will
be approved.
After the correction of the document it will be
distributed to the participates.

4
5. Participants List
QA Manager - Manager of Review
Software Development Team Leader
PM

6. Open Issues
The test cases design review will be documented, including
raised open issues, participants remarks and made decisions.
The test case document will be changed accordingly.

7. Responsibility
The QA team leader who is the owner of the test case design
specification, is also the manager of this review.
The responsibility is for the review summon, managing the
review, and summarizing it.

8. Summary
The purpose of the review is to approve the test cases.
The QA team leader is responsible for summarizing the review.
The updated test cases will be distributed to the participants
including the report, and decisions that took place.

5
 Packaging for testing

Task 1.10
1. Scope
This description is a frame for setting the
manner of managing and executing the
Packaging for testing process.

2. References
Knowledge Transfer Review – task 1.8
Document Review – task 1.7

3. Purpose
To create an installation for QA and finally for
release.

4. Description
The packaging process is the stage that the
code from the different development
departments is turned to an installation kit.
The development manager makes sure that all
the code is placed in the right folders.
The technical writers manager prepares all the
documents (PDF’s and On-line Help)
The release person packs it and check the
installation of the product and it’s basic
functionalities.
If he encounter any problems, the relevant
code is replaced and the product is packed
again.
The packed product is send to the
development for smoke test. After the smoke
test is finished successfully the release person
moves the installation to the QA.

6
5. Participants List
Release Person
Development Manager
Software Development Engineers
Technical writers Manager
Install shield code Writer

6. Open Issues
The Engine group is part of the development but still an
autonomic group. Therefore there are sometime problems in
coordinating between the two groups before packing a build.
There should be one person that will check that both groups are
prepared for any scheduled package.

7. Responsibility
The development manager makes sure that all the code is
placed in the right folders.
The Technical writers Manager makes sure that all the
documents (PDF’s and On-line Help) are prepares
The Release person is responsible for the packing process
itself.
He should also make sure that he uses the correct install
shield code (whether he writes it or someone else does).

8. Summary
The development delivers the modules to the release person
who packs is, delivers it back to the development for “Smoke
Tests” and, after it passes, delivers it to QA.

7
 “Smoke Test”

Task 1.11

2. Scope
This description is a frame for setting the
manner of managing and executing the smoke
tests.

2. References
Packaging for testing - task 1.10

3. Purpose
To determine whether or not the each and every
build is mature and ready for QA.

4. Description
The QA will write the smoke test based on the
critical features and the system stability. The
development team leader will read the tests and
commit to this document.
If the test fails, the development will fix the
bug/s, package the new build, and perform the
smoke test again, until it passes.
The development will use the Test Director to
read the test, and will update the status of the
tests in the relevant fields.
The “Smoke Tests” is to be viewed as a
contract between the QA and the development.
The contract assures that the product has the
minimal quality for testing by the QA.

8
5. Participants List
Software Development Team Leader
Software Development Team

6. Responsibility
The QA manager has the responsibility to determine the smoke
test.
It is the development team leader responsibility to perform the
test.

7. Summary
The QA manager is responsible for determining the smoke test,
and the development team leader to perform it.

9
 Testing

Task 1.12

2. Scope
This description is a frame for performing the test
cases.

2. References
Smoke test - task 1.11

3. Purpose
To approve the quality and performances of the
product.

4. Description
The QA receives the build after smoke test with
the prepared test cases document. In case of
fixed bugs, he should close them first. Afterward,
in the first and last build, he’ll perform regression
tests, by first running the high priority test. In
other builds he will close fixed bugs and perform
only the high priority tests.
During the tests for each build, the development
will fix the appropriate bugs and create another
build, package it, and perform smoke test.
No new features will be entered into the system
from the first build deliverance to QA.
In the last planned build there will be code freeze.

10
5. Participants List
QA Manager
QA team
Software Development Team Leader

6. Responsibility
The QA manager has the responsibility to perform the test and
release a quality product.

7. Summary
The QA will test the product, development will fix the bugs and
give the QA a new build, until the product will be mature enough
for the release.

11
 Packaging and Release

Task 1.13
2. Scope
This description is a frame for setting the
manner of managing and executing the
packaging process after the testing, and the
release of the product.

2. References
Testing – task 1.12.

3. Purpose
To release demantra product.

4. Description
Last packaging: After the testing process
ends, the QA team manager informs the
Release person that the product is ready for
release.
The last packaging includes wrapping the
SQL procedures (I.e. the code inside those
procedures is no longer available for reading).
The release person packs the product and
checks that the build wasn’t spoiled due to the
wrapping of the procedures or because of the
packaging itself.
Release: the release process include the
following:
- Copying the package to the different
channels available for the companies
employees.
- Burn the code and product on backup CD’s
- Close both the development and QA folders
involved in making of the product
12
5. Participants List
Release Person
QA Manager

6. Responsibility
The QA Team Manager should approve that the testing phase
went well and that the product can be released.
The Release person is responsible for the packaging process
with the wrapped procedures and for the release process itself.

7. Summary
After the last build is ready for release, the Release person
wraps and packs the product and checks that the build wasn’t
spoiled, and then performs the actual release.

13