What's special for .net developing in gathering user requirement?

[athos]

Hi All,

Believe you have sound experience in development, however, before
coding, when a project just started and is in User Requirement
gathering, what special points shall we pay attention to, if the
project is going to be done in .net?

maybe it's a little bit abstract? well, i'd like to call it a little
bit general...

any ideas guys?

Thanks.

 

[John Timney \( MVP \)]

None. Your requirements capture should focus on whats trying to be achieved
only. The technical choice should be made as a result of trying to identify
a technical solution to the requirement, if a technical solution is the
right choice, simple process change can sometimes be the solution.

Dont get caught in the trap of trying to mould a requirement around a
preferred technical solution - its the bain of bad design.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

 

[athos]

Dear John,

Thanks for your kind reply. Actually, my company just assigned me to
summarize some guidelines for project developing in .net, not only the
coding stage, but for the whole life circle, while I'm a little bit
lost so seeking for help here.

I just modified my question and post it here

http://groups.google.com/group/micr...a5c38/11ed40f3c4bc346a?hl=en#11ed40f3c4bc346a

could you pls to share some ideas there? thanks.

yours,
athos