hello there,
i am from the research community working on testing strategies for
projects that are usually long-term. i am curious to know how it is
done in the industry where some applications are small and have
really short development spans, but demand high quality standards.
what kind of quality/testing strategy is appropriate for a project
that is characterized thus:
- - has a very short development span (1-2 weeks)
- - has fluid requirements. they are solid enough at the start of the
project to start design and perhaps even test planning and coding,
but are prone to change because of a dynamic business domain of the
client
- - the product is more like a web-application where user skills may
fall all over the spectrum and luxuries like UAT are impossible
- - only minor changes are allowed once the product is online
- --
Praveen KALLAKURI
Research Assistant (Software Engineering)
Comp. Sci. & Eng. Research Facility
University of Nebraska - Lincoln
http://cse.unl.edu/~pkallaku
praveen@unlserve.unl.edu
Fingerprint: 0148 002F 3E97 C404 965E 4ACC EFC1 A650
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
iQB1AwUBPx62PgSOhI6OETvlAQFo8gL+J7TVhK5KVgpV5n2caOZs8+JLbDhaT3eR
Y9681HHXE0ORjac2bB5UTbXLpBxynQIeQSHel8ttfu+gXVojT0kKck3obFUmqqb3
Z2zZ57Stf3CokWEO6EZpVexFDNWboyBM
=J0jv
-----END PGP SIGNATURE-----