Quantcast

requirements Articles

Stop “Gathering” IT Requirements

Over the years, I’ve come to the conclusion that one of the most destructive notions circulating inside technical groups involves “gathering requirements.” For decades, virtually everyone in the industry has accepted that the first phase of every IT project should be to gather requirements from business users. At least in theory, it should be the point of departure for all our efforts. (Of course, it’s also the phase of the project that’s most often skipped.) So now that our success rate for IT projects has risen to the still-dismal level of about 25%, perhaps we should question some of this time-honored wisdom.

Web Services Reliable Messaging
· 1

Unless the message exchanges of Web services are made reliable, organizations will not be able to trust them for deployment in industrial-strength business. In this paper, Prasad Yendluri, Principal Architect at webMethods, explains why there is a need for a reliable messaging solution that is independent of the underlying transport protocol used to transmit the messages, and gives an analysis of emerging Web services reliable messaging standards and the work done in this space previously by RosettaNet, BizTalk, and ebXML that forms the basis for the advancements in the Web services domain.

Calculating ROI on your Investment in Requirements Management Tools

There’s no question that a commercial Requirements Management tool is very useful; but, can it pay for itself at your company? In this article we’ll look at a model to help you calculate ROI on Requirements Management tools.

10 Tips to Gather Business Requirements

Definition: Differentiate between client and customer: client is someone who would like your help in creating a product or service for someone; a customer is the person who pays for some service or product.

Use Case Management with Rational Rose and Rational RequisitePro
  1. How do you organize your use cases?
  2. Can you tell in which release a particular use case is implemented?
  3. How do you know that the entire system functionality is tested?
  4. Which tests are affected by a change in a use case?

If the inability to answer these questions has caused you frustration, schedule setbacks, or the delivery of products that have missed the mark, read on.

Requirements for Effective Boards Beyond Fine Tuning

As CEO, you’re accountable for results whether your board helps or hinders you in working toward them. Ensuring that key requirements are met, requirements that affect how well equipped board members are to work together, will provide a sound foundation from which the strategic leadership and fulfillment of role and responsibilities will more likely occur. These requirements go beyond fine tuning they are essential.