This is a project to write a technical paper for a proof of concept Exchange 2010 deployment. Below see the items that will be covered. I will be working very closely with the individual selected to write this paper. I am a very technical person, but just need help with the writing. I require excellent communication as I will be providing input as well. All work must be original, and in APA format. I have had issues with writers from India, (sorry, but true) so if you are not top notch, don't even bid. I will not pay for work that is not completed. I will require sample writings to verify competency and English grammar skills. I will provide detailed instructions for the project as requested, I also have samples of what it must look like.
Writing a Summary
Provide a summary (about three to five pages) of your proposed technical project-which is Microsoft Exchange 2010 Proof of Concept. The summary, however, includes coverage of all sections in the
Writing a Review of Other Work
In this section (about two to three pages), you will review other work that is relevant to your technical project.
Perhaps there are case studies of similar projects, comparisons of various solutions, or related articles. For
example, if you are planning a network security project, you might choose to summarize articles that describe
the business case for improved security, comparisons of various hardware and software products that are
possible alternatives for your project, and case studies that relate to the project you are planning.
Writing a Rationale and Systems Analysis
This section (about two to three pages) discusses the reasons for implementing the project described in your
proposal; they may consist of both business and technical reasons. It also summarizes the systems analysis that
you have done for your technical project.
Writing Goals and Objectives
List the goals and objectives (five to eight pages) of your technical project. Describe each in detail and explain
how the project will help to attain them. You should note that goals and objectives are not necessarily
technical in nature. Some of them will reflect business or organization goals. You should also discuss how you
would recognize reaching the goals and objectives.
Explain in five to eight pages what types of deliverables your project will provide. For example, you could
explain that your project will include some sort of formal report. It will likely also include a technical IT
product and a user's manual or other documentation.
Writing Plan and Timelines
Include in your proposal a projected timeline for your technical project, with milestones.
Remember that these are estimates made before you even begin the technical project. It is not uncommon for
project plans to require revision once the project is underway.