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" <at*******@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
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.