Information Technology Reference
In-Depth Information
Any software that will be run on customer equipment must first be reviewed
and approved by Corporate Software Quality. The project manager utilizes this
prototype to evaluate and provide input to the developer as the design evolves.
Although software is usually not distributed to users prior to beta testing, selected
end-users may also be involved. Usually, the most complex or most used parts of
the code are developed more completely in the alpha, in order to enable early
resolution of design questions.
The project manager collaborates with the developer to determine specific goals
for alpha testing and to integrate the results into evolving project plans. In-depth
software reliability testing, installation testing and documentation testing are not
done at alpha test time, as the software is only a prototype. Alpha tester feedback
forms are not used, although the developer does request feedback on specific
aspects of the software.
10.10.1.1 Setting Customer Expectations
If customers will receive alpha software, they must understand that the product
will be only minimally functional and is likely to have problems. The required
review by Corporate Software Quality checks for the most serious problems, but
customers must still be prepared for unexpected or frustrating experiences. A letter
or e-mail accompanying alpha software is strongly recommended. This letter
should make customers aware of:
• The software's limited functionality at this early stage
• The likelihood of experiencing problems
• Their mission: Find problems and provide feedback
An example Alpha Transmittal Memo is shown in Fig. 10.1 . All software and
user documentation in any lifecycle stage must include the Copyright, Ordering
information and Disclaimer Notice elements. Although software is usually not
distributed to users prior to beta testing, selected end-users may be involved in
alpha review. Usually, the most complex or most used parts of the code are
developed more completely in the alpha, in order to enable early resolution of
design questions.
10.10.1.2 Quality Team Involvement
It is understood that alpha software is not fully functional. However, Corporate
Software Quality tests all software that is to be sent to users or run on customer
equipment so that possible serious errors can be removed. Examples of such errors
are software behavior that compromises a user's system or presence of a virus.
This pre-testing of alpha software that is sent to users will protect the reputation of
software with customers.
Search WWH ::




Custom Search