Sciweavers

3547 search results - page 487 / 710
» Pseudo-Exhaustive Testing for Software
Sort
View
MSR
2006
ACM
16 years 18 days ago
Tracking defect warnings across versions
Various static analysis tools will analyze a software artifact in order to identify potential defects, such as misused APIs, race conditions and deadlocks, and security vulnerabil...
Jaime Spacco, David Hovemeyer, William Pugh
ICECCS
1998
IEEE
168views Hardware» more  ICECCS 1998»
15 years 11 months ago
The Architecture Tradeoff Analysis Method
This paper presents the Architecture Tradeoff Analysis Method (ATAM), a structured technique for understanding the tradeoffs inherent in design. This method was developed to provi...
Rick Kazman, Mark H. Klein, Mario Barbacci, Thomas...
173
Voted
UML
2005
Springer
16 years 4 days ago
Specifying Precise Use Cases with Use Case Charts
Use cases are a popular method for capturing and structuring software requirements. The informality of use cases is both a blessing and a curse. It enables easy application and lea...
Jon Whittle
CF
2005
ACM
15 years 8 months ago
Grid result checking
Result checking is the theory and practice of proving that the result of an execution of a program on an input is correct. Result checking has most often been envisioned in the fr...
Cécile Germain-Renaud, Dephine Monnier-Raga...
WSC
1998
15 years 8 months ago
Emulation of a Material Delivery System
Emulation is the process of exactly imitating a real system. Recent advances in simulation technology make it possible to emulate real world control systems by using a system'...
Todd LeBaron, Kelly Thompson