I came to gather the requirements for a website migration project from asp to asp.net. I want to know what kind of requirements i need to capture? What i am doing is, i am studying the existing website and planning the requirements based on the understanding.
No additional functionalities are required from client. Is i am in the right way or not? Is it the right way to capture the requirements for .net site. Can anybody guide me in capturing requirements?
asp is a totally different technology from asp.net.
it is better to understand the existing system from functionality perspective, Understand the new asp.net features and provide equivalent features and controls.
Some questions to ask from a technical perspective:
Should it be a MVC app or Webforms app?
Should we use master pages?
Should themes be used?
What kind of authentication, role membership and user profiles should be used?
Should Microsoft AJAX be used or JQuery AJAX or someother ajax framework?
What kind of validation logic should be used? - Validator controls or jQuery validation or custom build validation framework?
What kind of custom controls / ui should be created to improve the user experience?
In the database layer, do we go in for entity framework, LINQ to SQL, ADO.net (existing), or some other ORM framework?
What kind of automated testing tools should be used?
getsatish
Member
5 Points
1 Post
regd the gathering the requirements
Dec 01, 2005 11:12 AM|LINK
I came to gather the requirements for a website migration project from asp to asp.net. I want to know what kind of requirements i need to capture? What i am doing is, i am studying the existing website and planning the requirements based on the understanding. No additional functionalities are required from client. Is i am in the right way or not? Is it the right way to capture the requirements for .net site. Can anybody guide me in capturing requirements?
Thanks,
Satish.
CdJerry
Member
4 Points
2 Posts
Re: regd the gathering the requirements
Mar 13, 2011 12:35 AM|LINK
This is what I use: http://allthingscs.blogspot.com/2011/03/documenting-software-architectural.html
vijayst
All-Star
16558 Points
3216 Posts
Microsoft
Re: regd the gathering the requirements
Apr 17, 2011 09:07 AM|LINK
asp is a totally different technology from asp.net.
it is better to understand the existing system from functionality perspective, Understand the new asp.net features and provide equivalent features and controls.
Some questions to ask from a technical perspective:
Should it be a MVC app or Webforms app?
Should we use master pages?
Should themes be used?
What kind of authentication, role membership and user profiles should be used?
Should Microsoft AJAX be used or JQuery AJAX or someother ajax framework?
What kind of validation logic should be used? - Validator controls or jQuery validation or custom build validation framework?
What kind of custom controls / ui should be created to improve the user experience?
In the database layer, do we go in for entity framework, LINQ to SQL, ADO.net (existing), or some other ORM framework?
What kind of automated testing tools should be used?
http://liteblog.codeplex.com