Welcome to webch.org

How to Use a Sample Written Proposal (sample written proposal) Writing a proposal is not an easy feat. For many, it is one of the most difficult things they will ever do in their entire lives. However, there is help for those who are confused about the proposal writing process. A sample written proposal can be used as a guide for the confused writer, and can help them with the process of writing their own proposal. Proposals usually have seven components, which include the Table of Contents, Mission Statement, Abstract, Statement of Need, Project Rationale Incorporating Literature Review, Project Narrative, and Attachments. All of these features can be found in sample proposals, which provide writers with an example of how these sections should be organized. A table of contents is used to provide a comprehensive guide to the proposal, so that readers are able to find what they need and find areas of importance within the proposal. A sample written proposal is an excellent guide to writing a mission statement. A mission statement should be 50 words or less, and states the mission of the project. The statement is used to clarify and state the project’s primary goal, and allows the reader to instantly understand what the writer is proposing without reading the entire proposal. The second section of a proposal is the abstract. It is vital to a proposal that an abstract is well-written, and initial proposal reviews or “first cuts” are often based on the abstract. The abstract of a proposal should be written after the mission statement, and should be changed over time, as the proposal develops further. Most proposal drafters will see that abstracts should be clear and understandable to all readers, including lay readers, and should be suitable for publication. Proposal abstracts should be written in third person, and should include objectives, methods to be employed, and the possible impact of the proposed project. Statement of need is the next part of a proposal. Many writers could benefit from a sample proposal when writing this section, because some drafters tend to write about more than one problem, or present their problem incorrectly. The Statement of need is the section where the drafter presents the problem that must be solved. In this section, drafters should avoid circular logic in the development of their statement of need, as it decrees that the lack of a solution is the problem. It is important to use logical progression in the statement of need, and the proposer must prove that they have an understanding of the problem. The statement should be closed with a discussion of what else is being done to solve the problem, and lead into the narrative with a description of how your idea is different and essentially better than all others. The Project Rationale Incorporating Literature Review is the next section of a proposal. All samples written proposals will have this section, as proposals must incorporate a theoretical basis with a discussion of literature. The rationale for the project should come from evidence found in the relevant literature. A sample written proposal will show drafters how to develop this section and show them how all proposals should incorporate current research into their projects. The project narrative is the sixth section of the proposal, which has six main sections. Some organizations require different proposal narratives, so in this aspect, it may be better to obtain sample proposals from several different organizations. The six sections of the project narrative section of a proposal include goals and objectives, proposed activities, facilities, resources, and project management, evaluation, outreach and dissemination, and sustainability. The final section of a proposal is the attachments’ section. Generally, attachments include the bibliography, letters of support/endorsement, and letters of publication. Drafters can also benefit from a sample written proposal when creating this section, as it will provide an example of how the section should be organized and incorporated in the overall proposal. Writing a proposal is an extensive project, and sample proposals can be used to reduce pressure while providing the proper form needed for an excellent proposal.

Technical Writing: What is it? (technical writing) Technical writing is one of the most difficult forms of writing. To be a technical writer you need to be able to convey a technical message in a concise and effective manner. Technical documents must be created using comprehensive and precise information in a brief and understandable style. You will need the ability to be able to correspond with technical experts and have the understanding of all technical terminology. You are the middleman between the designers, engineers, or scientists and the audience of the technical writings. You have to have the ability to under stand what they are saying and the turn it into something that can be understood by someone else. Simply put it is writing that designs, creates, and upkeeps any kind of technical data such as user manuals, how to guides, and online help just to name a few. To be able to achieve a career in technical writing you must be able to write complex data in a straightforward, easy to understand and articulate fashion. You must be able to word step by step instructions in a way that seems effortless to a consumer. While doing technical writing one of the most important aspects of your job will be creating for an intended audience. So not only must you understand and convey what you are writing, you must understand whom you are writing it for. In most cases, you are generally trying to explain complex technical information to the average person. But with the diversity in the world today and having such a vast potential audience you must understand the meaning of the words you use and what they could mean to someone else. Some technical writing projects may also include magazine and newspaper articles. These articles will probably be focused on new technologies and products. In some cases this may be in the form of an advertisement. Or it could just be an introduction to a new product saying hey this is what we have and this is what it a can do. Although a formal education is always a plus, if you have experience and successful past ventures in technical writing it isn’t always necessary. Knowledge into the multiple components needed for technical writing is required. They key components to what you must know is an in depth knowledge many software programs. These applications can include Visio, Quadralay Web Works Publisher, Microsoft Word, and HTML script writing. Proper formatting, style, and organization of writings are what make them easy to follow. Correct wording, clear sentences, and easy terminology make your technical writings easy the read and comprehend. If you are employed as a technical writer with a company, you will most likely be working with a team of other writers. You writings will be reviewed for content efficiency as well as any grammar and spelling errors. Depending on the structure of the team they may be working on the same project as you or they may be working on separate projects. Either way the team is assembled as a support group to help make your technical writing be as accurate, effective, and as simple as it can be. To succeed in technical writing these are the simple rules to follow. Keep it as simple as possible; no one wants to read four pages to find a simple one word answer. Understand the people you are talking to and what you are telling them. If you don’t understand, neither will they. Make sure you get your work proofread or read it aloud to make sure it makes sense. You know what you are trying to say, but your reader does not. You are the carrier for getting information from point A to Point B.

Web Hosting - Bandwidth and Server Load, What's That? Two key performance metrics will impact every web site owner sooner or later: bandwidth and server load. Bandwidth is the amount of network capacity available, and the term actually covers two different aspects. 'Bandwidth' can mean�the measure of network capacity for web traffic back and forth at a given time. Or, it sometimes is used to mean the amount that is allowed for some interval, such as one month. Both are important. As files are transferred, emails sent and received, and web pages accessed, network bandwidth is being used. If you want to send water through a pipe, you have to have a pipe. Those pipes can vary in size and the amount of water going through them at any time can also vary. Total monthly bandwidth is a cap that hosting companies place on sites in order to share fairly a limited resource. Companies monitor sites in order to keep one site from accidentally or deliberately consuming all the network capacity. Similar considerations apply to instantaneous bandwidth, though companies usually have such large network 'pipes' that it's much less common for heavy use by one user to be a problem. Server load is a more generic concept. It often refers, in more technical discussions, solely to CPU utilization. The CPU (central processing unit) is the component in a computer that processes instructions from programs, ordering memory to be used a certain way, moving files from one place to the next and more. Every function you perform consumes some CPU and its role is so central (hence the name) that it has come to be used as a synonym for the computer itself. People point to their case and say 'That is the CPU'. But, the computer actually has memory, disk drive(s) and several other features required in order to do its job. Server load refers, in more general circumstances, to the amount of use of each of those other components in total. Disk drives can be busy fetching files which they do in pieces, which are then assembled in memory and presented on the monitor, all controlled by instructions managed by the CPU. Memory capacity is limited. It's often the case that not all programs can use as much as they need at the same time. Special operating system routines control who gets how much, when and for how long, sharing the total 'pool' among competing processes. So, how 'loaded' the server is at any given time or over time is a matter of how heavily used any one, or all, of these components are. Why should you care? Because every web site owner will want to understand why a server becomes slow or unresponsive, and be able to optimize their use of it. When you share a server with other sites, which is extremely common, the traffic other sites receive creates load on the server that can affect your site. There's a limited amount you can do to influence that situation. But if you're aware of it, you can request the company move you to a less heavily loaded server. Or, if the other site (which you generally have no visibility to) is misbehaving, it's possible to get them moved or banned. But when you have a dedicated server, you have much more control over load issues. You can optimize your own site's HTML pages and programs, tune a database and carry out other activities that maximize throughput. Your users will see that as quicker page accesses and a more enjoyable user experience.