Abstract
Testing is an important part of the software application development process. To achieve quality software deliverables and to avoid costly redevelopment of program code or repair of bad data, testing must be performed throughout the software development life cycle. This paper discusses a software engineering process to produce a software test plan based upon the {open_quotes}IEEE (Institute of Electrical and Electronics Engineers) Software Engineering Standards Collection{close_quotes} guidelines and corporate guidelines. Demonstrated examples of the software testing process involving interactive graphical user interface software and standard ASCII forms-based text are provided. Sandia National Laboratories has a Software Quality Assurance Department which provides corporate guidelines, in addition to recommending the use of IEEE processes. Both corporate guidelines and a specific subset of the IEEE guidelines were applied to the software development projects discussed herein. The rationale for applying a specific subset of the IEEE guidelines for each of the software development projects will be given. The development of the test procedures in the INGRES/WINDOWS 4GL environment (graphical user interface) as well as in the INGRES/ABF environment (Applications-By-Forms, ASCII Text) are presented and contrasted. The documentation of the testing process and results are explained.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.