Introduction. Plan the introduction to your proposal carefully.

Make sure it does all of the following things (but not necessarily in this order) that apply to your particular proposal: Indicate that the document to follow is a proposal. Refer to some previous contact with the recipient of the proposal or to your source of information about the project. Find one brief motivating statement that will encourage the recipient to read on and to consider doing the project. Give an overview of the contents of the proposal.

Now remember: you may not need all of these elements, and some of them can combine neatly into single sentences. The introduction ought to be brisk and to the point and not feel as though it is trudging laboriously through each of these elements. Take a look at the introductions in the first two example proposals listed at the beginning of this chapter, and try to identify these elements. Background on the problem, opportunity, or situation. Often occurring just after the introduction, the background section discusses what has brought about the need for the projectwhat problem, what opportunity there is for improving things, what the basic situation is. For example, management of a chain of daycare centers may need to ensure that all employees know CPR (maybe new state guidelines have been enacted about CPR certification). An owner of pine timber land in east Texas may want to get the land productive of saleable timber without destroying the ecology. (The section entitled "Need for a Wellness Program," in example proposal 1 (listed at the beginning of this chapter) is a good example of this.) It's true that the audience of the proposal may know the problem very well, in which case this section might not be needed. Writing the background section still might be useful, however, in demonstrating your particular view of the problem. And, if the the proposal is unsolicited, a background section is almost a requirementyou will probably need to convince the audience that the problem or opportunity exists and that it should be addressed. What should be in the background of the study/problem? The background of the problem is longer than the statement of the research problem itself. It is one of the determinant factors that give significant impact on research, it should explain the origins of the research question or problem, drawing on researchers preliminary reading. All cited materials should be presented with specific references, prepared according to one of the structured methods. Harvard University Extension School (2003) explained that in the background section, researcher should review what has been done already in this area of research and the way(s) in which the proposed project will differ from earlier work. Researcher should show that he/she is familiar with the major current opinions or interpretations concerning the problem he/she has chosen so that it can avoid duplicating an existing or outdated research. The background sections aim is not only to provide simply a general overview of the topic but also to demonstrate that a specific problem has been identified and to show its relationship to the research. The background of the problem should be: (i) Directed specifically to the research problem and must indicate the carefully documented views of experts; (ii) Well organized, others research should be considered in a systematic fashion, according to topic, date, perspective, or some other logical means; (iii) Able to establish the focus of researchers own research in relation to prior scholarship; and (iv) Detailed with relevant examples that illustrate how researchers approach to the subject will illuminate it. Woodall (n.d) had explained that the normal length of research background is recommended around 3 (three) to 5 (five). It should sketch the background leading to the present application, critically evaluate existing knowledge, and specifically identify the gaps that the project is intended to fill. Griffin (n.d) described that in the background of the research, the researcher should present relevant literature that supports the need for his/her project. Research articles, books, educational and government statistics are just a few sources that should be used here. This section can include brief overviews of articles covered in the literature review that support the need for the project.

BASICS OF PROBLEM DEFINITION Characteristics of Problems - Engineers are problem solvers. - Problems are problems only when we are aware of them. Crisis ---> Solution - Problems are often confused with solutions -- leads to advocacy and early commitment, ownership, actions to save face. - Don't accept the original problem statement a person may believe that a demon causes his leg to hurt this is a symptom of the problem perhaps it is actually a broken leg. - Problems are problems because they have no easy answers if they did, they would be already solved. - Solutions often become problems -- i.e. the automobile. - Problems and values change over time. What was a good solution once doesn't work any more. - Problems are total; solutions, disciplines seldom are. - A problem is a problem if you believe it to be one. - Anticipate and broaden your view of the problem. What are the relevant factors? Usually very many Technical Social Economic Components of Problem Definition Describe System: - What is the function of the system? - Size of things -- constraints? Dimensions, weight. - Environment -- weather, temperature, moisture. - Skills, ability. - People -- what particular types? - Systems -- higher and lower level system goals, interfaces - Flows -- how do pieces fit together, what activities are there and how are they related? - Components -- what are the parts and what is their purpose? Goals: - What are critical factors, characteristics of an ideal system? - What is the goal of your design? - How do you measure performance of the system? - What is wrong with the current system? In relation to your goals? - Economics -- costs, value, prices, cash flow Environment: - The Market -- who uses it, what are their characteristics? - The Competition -- what systems currently exist? Good points? Bad points? - "Need to Know" list -- what do you have to know to work on the problem? - Weather -- cold, warm, rain, dry, humid - People -- size, strength, skills, literacy, handicaps, sight, hearing. - Materials -- strength, transport, soils, sources, durability, workability. - Emergencies -- fire, flood, wind, safety, security, crime. - Procedures -- construction process, labor relations, management, payments, schedules, sequences. Problem Solving Methods There are three basic methods to solve problems 1) The Good Idea Approach. You are somehow inspired and have a "good idea" which you attempt to develop and defend against all criticism. This approach often leads to failure since there is usually a closed mind to other ideas. Bad news is ignored until it is too late. 2) The Scientific Method. Begin by stating a theory or hypothesis. Collect data and analyze it to determine if the theory/hypothesis is true or false. Not really a relevant method for design problems since it involves the search for truth rather than the search for an answer. 3) The Systems Approach. Three separate activities: problem definition, development of alternatives, and evaluation. Don't define problems as solutions; i.e. build a better mousetrap. Dont reject alternatives prematurely. Dont evaluate until problem and alternatives are clearly defined