Modeling software tools with ICON

This paper describes a new software test automation tool, a powerful new programming language, and the software development process that resulted when these tools were combined. A small development team of software developers and potential customers devised the unconventional process to meet a short...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
1. Verfasser: Fonorow, O. R.
Format: Tagungsbericht
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:This paper describes a new software test automation tool, a powerful new programming language, and the software development process that resulted when these tools were combined. A small development team of software developers and potential customers devised the unconventional process to meet a short deadline. The process produced an operational prototype or model of the entire software system that customers were able to use during the time it was being developed. The first model of the Buster™ automated testing system was conceived, designed, and implemented ahead of schedule in less than six months, complete with many features and components. The Buster system provides a test-information subsystem with facilities for multi-project test sharing, per-project test storage and planning, and test downloading for lab use. A separate test execution facility is also included that features test-result logging, a results database, and per-session I/O recording. The customer, AT&T 3B4000 System Test, reports that system soak tests that had taken three weeks now can be completed in one week, using Buster. The software modeling technique that was used to create the Buster test system is a new idea that can be used to produce reliable low-cost software in many applications. Unlike more conventional software engineering approaches, including rapid prototyping, the model can be used by customers as it is slowly evolved into a finished product. The model is used to embody and test designs and identify missing requirements before making large investments in production level code and documentation. In addition, software modeling makes it possible to develop comprehensive system test suites long before production level software is available. The process is composed of three major components: brainstorming and team building with customers, high-level language engineering, and automated software testing.
DOI:10.5555/55823.55844