Software requirements and acceptance testing

Authors:
Pei Hsia;David Kung;Chris Sell
Affiliations:
Department of Computer Science and Engineering, University of Texas at Arlington, Box 19015, Arlington, Texas 76019–0015, USA E‐mail: {hsia, kung}@cse.uta.edu;Department of Computer Science and Engineering, University of Texas at Arlington, Box 19015, Arlington, Texas 76019–0015, USA E‐mail: {hsia, kung}@cse.uta.edu;Lockheed/Martin, Fort Worth, TX 76101, USA
Venue:
Annals of Software Engineering
Year:
1997

Citing 20
Cited 8

Software system testing and quality assurance

Software system testing and quality assurance
Verification and validation of real-time software

Verification and validation of real-time software
System Testing Aided by Structured Analysis: A Practical Experience

IEEE Transactions on Software Engineering - Special issue on COMPSAC 1982 and 1983
The complete guide to software testing

The complete guide to software testing
Storyboard prototyping: a new approach to user requirements analysis

Storyboard prototyping: a new approach to user requirements analysis
Software requirements: objects, functions, and states

Software requirements: objects, functions, and states
Object-oriented modeling and design

Object-oriented modeling and design
The use of scenarios in design

ACM SIGCHI Bulletin
Formal Approach to Scenario Analysis

IEEE Software
The chaining approach for software test data generation

ACM Transactions on Software Engineering and Methodology (TOSEM)
A simulation from combat systems development and acceptance testing

WSC' 90 Proceedings of the 22nd conference on Winter simulation
Testing Computer Software

Testing Computer Software
Software Verification and Validation: Realistic Project Approaches

Software Verification and Validation: Realistic Project Approaches
Art of Software Testing

Art of Software Testing
Standardized Development of Computer Software

Standardized Development of Computer Software
Quality Assurance for Computer Software

Quality Assurance for Computer Software
Quantifying Software Validation: When to Stop Testing?

IEEE Software
Prototyping as a tool in the specification of user requirements

ICSE '81 Proceedings of the 5th international conference on Software engineering
Test plan generation using formal grammars

ICSE '79 Proceedings of the 4th international conference on Software engineering
The automatic generation and execution of function test plans for electronic switching systems

Proceedings of the software quality assurance workshop on Functional and performance issues

API documentation with executable examples

Journal of Systems and Software
Automating test generation for discrete event oriented embedded systems

Journal of Intelligent and Robotic Systems
Research methods in computing: what are they, and how should we teach them?

ITiCSE-WGR '06 Working group reports on ITiCSE on Innovation and technology in computer science education
Security Attack Testing (SAT)-testing the security of information systems at design time

Information Systems
Verifying Software Requirements Based on Answer Set Programming

KSEM '09 Proceedings of the 3rd International Conference on Knowledge Science, Engineering and Management
An overview on test generation from functional requirements

Journal of Systems and Software
A DSML for mobile phone applications testing

Proceedings of the 10th Workshop on Domain-Specific Modeling
Behavior modeling technique based on EFSM for interoperability testing

ICCSA'05 Proceedings of the 2005 international conference on Computational Science and Its Applications - Volume Part III

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper we 1) review industry acceptance testing practices and 2) present a systematic approach to scenario analysis and its application to acceptance testing with the aim to improve the current practice. It summarizes the existing practice into categories and identifies the serious weakness. Then, a new approach based on the formal scenario analysis is presented. It is systematic, and easily applicable to any software or system. A simple, yet realistic example is used to illustrate its effectiveness. Finally, its benefits and its applicability are summarized.