requirements

Articles

Assuming the Worst about Requirements

Requirements are under suspicion. Read between the lines of software and project management journalism and you'll hear nearly everyone lamenting the sad state of requirements. Managers plan only eight percent of project time for requirements. Developers worry about Zen-like requirements that lack sufficient detail to produce serviceable code. Testers think they have to backfill requirements. So, what were the analysts doing?

Becky Winant
A Look at Application Prototyping with easyPilot

This application tool allows non-programmers to produce working prototypes of Windows, or Web-based, database-driven applications. Read on to find out how this new tool makes protoyping a viable part of the IT software development process.

Bill Walton
Are You Listening?

Chances are you won't be able to deliver on everything your customer wants. Asking good questions at the beginning of a project can help you determine where your customer wants to go. Although you may not be able to give them everything they want, if you are able to deliver the top ten things on a list of fifty items you've still delivered value. Keeping the lines of communication open is essential to helping you achieve your project goal.

Esther Derby's picture Esther Derby
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
Taking the Mystery out of Requirements

Ambiguity, false assumptions, theories, and red herrings. These basic elements of a good mystery story are also encountered in software requirements gathering. And just as the detective has his bag of tricks for solving the mystery, you can learn a few things about uncovering elusive requirements in this column from Becky Winant.

Becky Winant
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
Rethinking Requirements

In my travels, I see many different views about what
requirements are, and how to deal with them. There are more and less useful ways to view
requirements. I believe many people could be thinking about
requirements in a more useful way, which would help
them build better software more effectively.

Brian Lawrence, Coyote Valley Software
From Failure to Success: Using Testing and Requirements Management

A multi-million dollar project on the verge of failure was given one last effort to create a winning team who could establish a definitive process around requirements management, automated testing, and quality assurance. Within six months, this team was able to successfully modify the existing software and deliver a product with zero defects that customers were able to use. Discover how requirements management can assist your organization in building a foundation for successful software development.

Tony O'Neill, Eli Lilly and Company

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.