RE: Requirements Clarification

Subject: RE: Requirements Clarification
From: <Jan -dot- Arnopolin -at- thomsonreuters -dot- com>
To: <klhra -at- yahoo -dot- com>, <jillemo -at- gmail -dot- com>, <neilson -at- windstream -dot- net>
Date: Tue, 28 Jul 2009 10:34:04 -0500

At my location, functional specs include (business) use cases. Before
the functional specs are written, management has already, in theory,
agreed to the modifications to our software set.


Jan Arnopolin
Technical Writer
Hubbard One
Thomson Reuters

Phone: +1 312 873-6784
Fax: +1312 873-6801
jan.arnopolin@@thomsonreuters.com
www.hubbardone.com



-----Original Message-----
From:
techwr-l-bounces+jan -dot- arnopolin=thomsonreuters -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+jan -dot- arnopolin=thomsonreuters -dot- com -at- lists -dot- techwr-l
.com] On Behalf Of Keith Hood
Sent: Thursday, July 23, 2009 11:01 AM
To: Jill Mohan; Peter Neilson
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Requirements Clarification


I think there is some reason to believe the wikipedia article needs
work. It says that functional requirements and use cases are the same
thing. Not according to what I've been told.

The way I've always understood it, a functional requirement describes
some capability that the software must have, such as being able using IM
to communicate. A functional requirement is a document that is related
only to the software itself. It would tell the reader what the software
must be able to do and, where relevant, set parameters needed for
operation. For example, a requirement that the software communicate by
using IM may also specify which port the IM should use, and specify
timeout limits.

A use case is a document that relates to interactions between some part
of the software and a user. It describes actions that are taken by the
software and the user in response to each other. Usually a human user,
but a use case can also set rules about what is done when there is
activity between different parts of the system. A use case sets rules
about the behavior of the software, so where an FR sets WHAT the
software can do, a use case set HOW it does things.

That's the way I've always understood it. Your mileage may vary.


--- On Thu, 7/23/09, Peter Neilson <neilson -at- windstream -dot- net> wrote:

> From: Peter Neilson <neilson -at- windstream -dot- net>
> Subject: Re: Requirements Clarification
> To: "Jill Mohan" <jillemo -at- gmail -dot- com>
> Cc: techwr-l -at- lists -dot- techwr-l -dot- com
> Date: Thursday, July 23, 2009, 11:15 AM Your work is already done:
>
> http://en.wikipedia.org/wiki/Software_Requirements_Specification
>
> The assumption here is that the information in Wikipedia is true,
> complete, and useful.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Free Software Documentation Project Web Cast: Covers developing Table
> of Contents, Context IDs, and Index, as well as Doc-To-Help
> 2009 tips, tricks, and best practices.
> http://www.doctohelp.com/SuperPages/Webcasts/
>
> Help & Manual 5: The complete help authoring tool for individual
> authors and teams. Professional power, intuitive interface.
> Write
> once, publish to 8 formats. Multi-user authoring and version control!
> http://www.helpandmanual.com/
>
> ---
> You are currently subscribed to TECHWR-L as klhra -at- yahoo -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> http://lists.techwr-l.com/mailman/options/techwr-l/klhra%40yahoo.com
>
>
> 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
> http://www.techwr-l.com/ for more resources and info.
>
> Please move off-topic discussions to the Chat list, at:
> http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
>



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.
http://www.doctohelp.com/SuperPages/Webcasts/

Help & Manual 5: The complete help authoring tool for individual authors
and teams. Professional power, intuitive interface. Write once, publish
to 8 formats. Multi-user authoring and version control!
http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as
jan -dot- arnopolin -at- thomsonreuters -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit
http://lists.techwr-l.com/mailman/options/techwr-l/jan.arnopolin%40thoms
onreuters.com


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
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.
http://www.doctohelp.com/SuperPages/Webcasts/

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
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 http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


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
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


References:
Re: Requirements Clarification: From: Peter Neilson
Re: Requirements Clarification: From: Keith Hood

Previous by Author: Re: Re: How do you ensure the quality of translations?
Next by Author: Re: job-hunt weirdness (Gene Kim-Eng)
Previous by Thread: Re: Requirements Clarification
Next by Thread: Re: Requirements Clarification


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


Sponsored Ads