Problem with duplication while designing fw.

[Illusion0Reality]

I have observed some problems while designing a fw.
If we have a huge application which have 200 pages to be automated. This automation is divided for 3 resources.

The problem with this is - there are almost 40-50 pages are common for all these resources, I mean overlapping of pages.
What is the best way to avoid this - Before starting the fw. So, we can avoid redundancy and also avoid rework.

If QTP, then I will assign tasks like:
1. One resource should work on Generic functions writing.
2. Second resource should work on Page related functions writing and Object Repository construction.
3. Third one may co-ordinate,  and help others.

Please advise.

[softwaretestingforum]

I would say discuss, discuss and discuss.

My experience with failed and delayed automation says that it is lack of foreseeing what causes all these issues. I don't advocate writing long documents which no one would read but to try to decide in advance on needs of -

Automation components which would be reused all along, and need to developed first.
Automation components which would use those reusable components, as real development of this stage needs to wait till you are not done with step 1.

By and large your approach looks viable to me. Always take some time to review it from time to time.

[Illusion0Reality]

Thanks for the valuable advice Tarun !

Yes, communication is more important than anything else.