Hi Tracy,

I think you should consider preparing 2 documents:

- Business Requirements
- Feasibility Study

In the Business Requirements, itemize the following:
- What is good (function-wise) about the current system
- What is "bad" about the current system
- What needs to be added

In the Feasibility Study, provide options for satisfying the Business Requirements:
- Modify the existing app
- Purchase a solution
- Build from scratch

For each option in the Feasibility Study, outline the following:
- Benefits
- Costs (manpower, $)
- Risks (including the risk of not proceeding)

Then make a recommendation for a particular option.

At this point, you don't need to get into "low level" details like VFP tier vs C# tier, etc. ... That is the purpose of the "System Architecture" document, which is generally produced in tandem with a set of "Functional Specifications".

I think the main point is that there are some "preliminary" documents and sign-offs required before one gets down to "architecture".

(I'm currently Project Manager on a "national" ASP.NET C# n-tier Oracle project after having found myself in pretty well the same situation you are finding yourself in now :)



>I have been tasked to create a white paper for inhouse use to look at the business considerations in rewriting a major application (took 10 years to develop completely and is now in VFP9 but still has data handling code throughout accessing tables directly - no ntier development but many classes and new features have been added overtime) from VFP to C# using SQL Server 2005 as a backend. WOW.
>
>I have six weeks to complete it. A lot to consider and right now I am looking at the below options to include:
>
>Front End VFP, Middle Tier VFP, Backend SQL Server 2005
>Front End C#, Middle Tier VFP, Backend SQL Server 2005
>Front End C#, Middle Tier C#, Backend SQL Server 2005
>
>
>Right now there is no TRUE middle tier but if it is rewritten then it should be done with one to allow for the greatest options down the road for future modifications.
>
>using C# it would include options of winforms or webforms
>
>If we do this, then the company will invest in formal C# training (wow, what a terrific opportunity). Right now I only have my experience learning on my own at home).
>
>I know the benefits of using VFP data handling but there are many business cases for creating a separate dotnet frontend and even using data handling in net (yuck but it must be seriously considered). I do not have to present that information other than to list the pros and cons but will focus on the benefits and drawbacks (as a business, as developers, and from the customers perspective - sales) of each option listed above and the estimated manhours to complete each one. The original app may still exist if the rewritten one is strictly thin client. That will be determined as well. We have over a thousand customers so the need for thin and thick clients exist.
>
>Please do not respond with "WHY even consider this?" The task was assigned and I will do my best to complete it honestly and in a professional manner listing all aspects.
>
>Previous documentation and experience anyone is willing to share would be GREATLY appreciated.