RE: Requirements

Subject: RE: Requirements
From: "Evans, Diane L (Rosetta)" <diane_evans -at- merck -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Mon, 13 Aug 2007 07:28:15 -0700

> Do you think that developers should be involved in this process?

Requirements are my life -- it is what I do best.

You need to understand that there are many types of requirements. I
perform validation testing from the user requirements. For example, the
user might have a requirement "I want to start the car with a key." The
user doesn't care how that happens; the developers would need to figure
out how to make the key interface with the car's starter. If the car
starts with a key, the requirement is met.

Should the developers have been in the initial requirements-gathering
process? Only if they will add value to the discussion. Suppose the
user wants a new type of car. You know that they might have
requirements such as, "I want a car with wheels that swivel to make
parallel parking easy." You would want a developer in this discussion
that would say, "We can do that, but it will add xxx time to the
development and xxx to the final cost."

I have both types of requirements meetings. If we are just updating an
existing application, I am most likely meeting with the users alone. If
we are creating an entirely new system, the lead developer is invited
along to add some sanity to the users' desires.

Diane Evans
Requirements Analyst
Rosetta Inpharmatics

Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Requirements: From: Jim Barrow

Previous by Author: RE: Page size in Word
Next by Author: RE: LinkedIn's value
Previous by Thread: Re: Requirements
Next by Thread: Re: Requirements

What this post helpful? Share it with friends and colleagues:

Sponsored Ads