|
Spring 2008 |
|
METHODOLOGY FOR SOLVING THERMODYNAMICS PROBLEMS A
major goal of this textbook is to help you learn how to solve engineering
problems that involve thermodynamic principles. It is extremely important for
you to study the examples and solve problems, for mastery of the
fundamentals comes only through practice. To
maximize the results of your efforts, it is necessary to develop a systematic
approach. You must think carefully about your solutions and avoid the temptation
of starting problems in the middle by selecting some seemingly
appropriate equation, substituting in numbers, and quickly ‘‘punching
up’’ a result on your calculator. Such a haphazard problem-solving approach
can lead to difficulties as problems become more complicated. Accordingly, we
strongly recommend that problem solutions be organized using the five steps in
the box below, which are employed in the solved examples of this text. The
problem solution format used in this text is intended to guide your
thinking, not substitute for it. Accordingly, you are cautioned to avoid the
rote application of these five steps, for this alone would provide few benefits.
Indeed, as a particular solution evolves you may have to return to an earlier
step and revise it in light of a better understanding of the problem. For
example, it might be necessary to add or delete an assumption, revise a sketch,
determine additional property data, and so on. The
solved examples provided in the book are frequently annotated with various
comments intended to assist learning, including commenting on what was learned,
identifying key aspects of the solution, and discussing how better results might
be obtained by relaxing certain assumptions. Such comments are optional in your
solutions. In
some of the earlier examples and end-of-chapter problems, the solution format
may seem unnecessary or unwieldy. However, as the problems become more
complicated you will see that it reduces errors, saves time, and provides a
deeper understanding of the problem at hand. RECOMMENDED
STRUCTURE FOR PROBLEM SOLVING: Known:
State briefly in your own words
what is known. This requires that you read the problem carefully and think about it. Find:
State concisely in your own words
what is to be determined. Schematic and GivenData: Draw a sketch of the system to be considered. Decide whether a closed system or control volume is appropriate for the analysis, and then carefully identify the boundary. Label the diagram with relevant information from the problem statement. Record all property values you are given or anticipate may be required for subsequent calculations. Sketch appropriate property diagrams (see Sec. 3.2), locating key state points and indicating, if possible, the processes executed by the system. The
importance of good sketches of the system and property diagrams cannot be
overemphasized. They are often instrumental in enabling you to think clearly
about the problem. Assumptions:
To form a record of how you model
the problem, list all simplifying
assumptions and idealizations made to reduce it to one that is manageable.
Sometimes this information can also be noted on the sketches of the previous
step. Analysis:
Using your assumptions and
idealizations, reduce the appropriate governing equations and relationships to
forms that will produce the desired results. It
is advisable to work with equations as long as possible before substituting
numerical data. When the equations are reduced to final forms, consider them to
determine what additional data may be required. Identify the tables, charts, or
property equations that provide the required values. Additional property diagram
sketches may be helpful at this point to clarify states and processes. When
all equations and data are in hand, substitute numerical values into the
equations. Carefully check that a consistent and appropriate set of units is
being employed. Then perform the needed calculations. Finally, consider whether the magnitudes of the numerical values are reasonable and the algebraic signs associated with the numerical values are correct. |