|
|
Use Cases for Maximizing Project Success This article will teach you to: understand how use cases can be used on non-oo projects, employ solid techniques to develop "good" use cases, leverage use cases to increase user accountability for requirements completeness, and how to apply measurement benefits to use case deployment.
|
Carol Dekkers, Quality Plus Technologies Inc
|
|
|
Gathering Requirements in a Low-Process Environment Knowing the requirements for a system means understanding the problem to be solved. If the problem isn't understood, the solution can't address it. Not taking time for requirements discovery at the beginning will cost far more time and money in the end. This paper explains requirements gathering techniques.
|
Elisabeth Hendrickson, Quality Tree Software, Inc.
|
|
|
Testing and Implicit Requirements: Expanding the Unwritten Specification Testers should be encouraged to test against and report deviations from implicit specifications. There is a Universal Implicit Specification that is based on
fundamental principles. These principles are: the system will not lie, the system will impose no gratuitous keyholes or other constraints, and the system won’t do anything that’s just plain stupid.It’s worthwhile to identify, elaborate, and make explicit the fundamental principles and
common manifestations of deviations from these principles.
|
Scott Meyers, Aristeia.com
|
|
|
STAREAST 2003: Rapid Web Testing in a High-Velocity Environment This paper discusses implementing METS (Minimal Essential Testing Strategy) for your test team. METS is a strategy to help get the essential testing for your project done within the time frame allowed. Step by step instructions for using this methodology are included.
|
Greg Paskal, Kinko's
|
|
|
How to Test Without Testable Requirements This paper discusses why testing without requirements can create a problem for your project. Testing without the proper requirements can lead to less reliable software results and more software failures.
|
Mark Taylor, Analex Corporation
|
|
|
Requirements-Based Testing: An Overview In this article, the author discusses how to deliver more function, in less time, and with fewer resources while maintaining a high level of quality. He details how poorly written requirements can lead to major system errors. This paper also explains why good requirements are a critical part of any successful project.
|
Gary Mogyorodi, BIT, Inc.
|
|
|
Applications-Centric Testing of System-Level Components Testing system-level components such as the Java API for XML-Based Remote Procedure Calls is a challenging task. Employing use-case techniques from the Unified Modeling Language (UML), Vinay Pai describes a novel approach for testing such components. His team developed use cases for a realistic application that would use the components, then developed test case designs from those use cases. The resulting test suite uncovered more than 200 defects in eight months, and exceeded code coverage goals by almost 50 percent. Learn the details of this approach and recommendations for transitioning to application-centric testing for your system-level components.
|
Vinay Pai and Arun Gupta, Sun Microsystems
|
|
|
Testing from Use Cases Using Path Analysis Technique Use cases are an industry-standard method of specifying user interaction with the system, and hence have become part of the requirements definition phase of many software projects. They're used to derive, construct, and validate interfaces, classes, relationships, and processes in an application. This session introduces participants to a testing methodology called, use case path analysis. This technique has proven to be an extremely powerful way to create accurate, realistic test cases based on the use cases. Usable in any environment, with any tool set, use case path analysis not only saves time and money, it also helps you to control risk.
|
Naresh Ahlowalia, Object System Group
|
|
|
Effective Testing for Java-based Web Software This presentation addresses the following: What is Java software, anyhow? How do you test Java? How do you build testable Java applets/applications?
|
Sam Guckenheimer, Rational Software
|
|
|
Software Inspection: Taking a Step Forward to Completion n
|
Neela Majumder, Intel Corporation
|
