Large application

3000 pages,

Are you rebuilding the microsoft domain?

If not I would question the need for 3000 separate pages.  How have you come to the conclusion that the project has the need to incorporate 3000 pages?

I would strongly urge for you and your team to do some proper analysis and identify what it is your hoping to achieve then break this down into manageable chunks. Speculating that you need 3000 pages upfront without having any idea how your going to achieve it is for a start very worrying.

Delivering a large project on a waterfall delivery is a massive no go. Look into iterative development and the tools that help you achieve this. But please sit down with the people that are driving this project and spend a good few weeks working out what your trying to deliver.

3000 pages!!!

Are you rebuilding the microsoft domain?

If not I would question the need for 3000 separate pages.  How have you come to the conclusion that the project has the need to incorporate 3000 pages?

I would strongly urge for you and your team to do some proper analysis and identify what it is your hoping to achieve then break this down into manageable chunks. Speculating that you need 3000 pages upfront without having any idea how your going to achieve it is for a start very worrying.

Delivering a large project on a waterfall delivery is a massive no go. Look into iterative development and the tools that help you achieve this. But please sit down with the people that are driving this project and spend a good few weeks working out what your trying to deliver.

Hi,

That application was originally implemented in asp and vb script.

It is working quite well and is well designed.

The only thing that we are trying tp do is to migrate it to .net.

I am prety sure the design is good!

Thanks,

Daniel.

Ok,

If you are sure about this then great.

I would look to break down the project into separate iterations, that is actual small deliverable work packages. This helps to focus the minds rather than a long drawn out 6 months/1 year release cycle. keep the iterations to around 4 weeks and ensure each iteration is well tested and signed off. This gives your employers peice of mind also as they can see a well oiled product forming and new functionality being delivered on a regular basis. I am sure through the 3000 pages there is much similar functionality that you can wrap into user controls or separate services. An iterative development plan will help you refactor peices of functionality as you come across similar areas or work. As I mentioned before type "TDD" and "Agile" into google and look at best practise. To start with look here http://en.wikipedia.org/wiki/Agile_software_development.

If your working with a large RDBMS then maybe look at a code generator for your DAL. Read up on llblgen and codesmith, maybe these tools can ease the development burden.

Good Luck