On 18 Aug 2009 11:58, max psykx <[email protected]> wrote:
2009/8/18 Lyle [email protected]>:
> Hi All,
> Just finished the chapters on software requirements. How does your
> company handle software requirements? If you take on external contracts,
> how do you elicit requirements from your clients? If your requirements
> come from internal sources, how do you get them and how do you process
them?
> Do you use any software to manage your requirements or aid in
> obtaining requirements? How do you deal with conflicting requirements or
> urging changes? Do you use UML, use case, interviewing, viewpoints, etc?
> Anything related to requirements engineering that you think is
> noteworthy or just feel like mentioning?
>
> Sorry for all the questions. Being able to map these things to real life
> accounts, always stimulates the brain to remember better :)
>
>
> Lyle
>
> _______________________________________________
> BristolBathPM mailing list
> [email protected]
> http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
The company I work for currently sits down with a client and discusses
their requirements taking notes and produces a specification which is
then agreed with the client. Things I like to see in a specification are
user work flows as this makes things easy for the client and developer to
understand. I also feel that it's important that
sorry this got sent to early.
I think that it's important that testing is considered at this stage, user
work flows also add structure and provide a workable backbone to the
testing plan. Things like acceptance testing and level of security testing
should also be agreed with the client at this stage.
Max
_______________________________________________
BristolBathPM mailing list
[email protected]
http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
