For Programmers: Free Programming Magazines  


Home > Archive > Software Engineering > January 2007 > Separating standard from non-standard requirements (documentation)









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Separating standard from non-standard requirements (documentation)
mzehle@googlemail.com

2007-01-10, 8:09 am

Hi,

I am looking for a solution to separate standard requirements from non
standard requirements.
We use a Lotus Notes application to store reqs. for the standard
software we produce. Since we have more than one customer the reqs.
begin to differ and I need to find a clever way for the analysts to
docment in the Notes application which is standard an which not. The
documents sometimes contain embedded tables with data that dieffers
from customer to customer so the solution is not simply creating two
documents for each customer.

Thanks for your help.

Martin

Alexei Polkhanov

2007-01-11, 7:06 pm

You can organize your requirements management process better if you use
something like Borland Caliber or DOORS. Just to give you an idea ...

- Alexei.

mze...@googlemail.com wrote:
> Hi,
>
> I am looking for a solution to separate standard requirements from non
> standard requirements.
> We use a Lotus Notes application to store reqs. for the standard
> software we produce. Since we have more than one customer the reqs.
> begin to differ and I need to find a clever way for the analysts to
> docment in the Notes application which is standard an which not. The
> documents sometimes contain embedded tables with data that dieffers
> from customer to customer so the solution is not simply creating two
> documents for each customer.
>
> Thanks for your help.
>
> Martin


Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2010 codecomments.com