ote that at this stage the goal is to descri be the functional elemen ts of the produt without implying a specific technol ogical working pr in ciple for the product concept. For example, Exhibit 7-4(b) includes the subfunction "iso
late nail." Th i s subfunction is expressed in such a way that it does not imply any particular physical solution concept,
suchas indexing the coil of nails into a slot or breaking a nail sideways off of the stick. The team should consider each subfunction in turn and ask whetherit is expressed in a way that does not imply a particular phys i cal solution principle.
There is no single correct way of creating a f u nction diagram and no singl e correct functional decomposition of a product. A helpful way to create the diagram is to quick l y create several drafts and then work to refine them into a single diagram that the team is comfortable with. Some useful techniques for getting started are:
• Create a function diagram of an existing product.
• Create a function diagram based on an arbitrary product con cept al ready generated by the team or based on a known subfunction technology. Be sure to general i ze the dia gram to the appropriate level of abstraction.
• Follow one of the flows (e. g., material) and determine wh at operations are required .
The details of the other flows can be derived by thinking about their connections to the initial flow.
Note that the function diagram is typically not un i que. Tn particular, subfunctions can often be ordered in different ways to produce d i fferent function diagrams. Also note that in some applications the material , energy, and signal flows are difficult to identify. In these cases, a simple list of the subfunctions of the product, without c01mections between them , is often sufficient.
Functional decomposition is most applicable to technical prod u cts, but i t can also be applied to simple and apparently nontechnica l products. For example, an ice cream scoop has material flow of ice cream be i ng separated, formed, transported, and deposited. These subfunctions could form the basis of a problem decomposition .
Functional decomposition is only one of several possible ways to divide a problem into simpler subproblems. Two other approaches are:
• Decomposition by sequence of user actions: For example, the nailer probl em mi gh t be broken down into three user actions: moving the tool to the gross nailing position, positioning the tool precisely, and triggering the tool. This approach is often useful for products with very simple technical functions involving a lot of user interaction.
• Decomposition by key customer needs: For the nailer, this decomposition might include the following subproblems: fires nails in rapid succession, is lightweight, and has a large nail capacity. This approach is often useful for products in which form, and not worki ng principles or technology, is the primary problem. Examples of such products incl ude toothbrushes (assuming the basic brush concept is retained) a n d storage containers.
ote that at this stage the goal is to descri be the functional elemen ts of the produt without implying a specific technol ogical working pr in ciple for the product concept. For example, Exhibit 7-4(b) includes the subfunction "iso late nail." Th i s subfunction is expressed in such a way that it does not imply any particular physical solution concept, suchas indexing the coil of nails into a slot or breaking a nail sideways off of the stick. The team should consider each subfunction in turn and ask whetherit is expressed in a way that does not imply a particular phys i cal solution principle.There is no single correct way of creating a f u nction diagram and no singl e correct functional decomposition of a product. A helpful way to create the diagram is to quick l y create several drafts and then work to refine them into a single diagram that the team is comfortable with. Some useful techniques for getting started are:• Create a function diagram of an existing product.• Create a function diagram based on an arbitrary product con cept al ready generated by the team or based on a known subfunction technology. Be sure to general i ze the dia gram to the appropriate level of abstraction.• Follow one of the flows (e. g., material) and determine wh at operations are required .The details of the other flows can be derived by thinking about their connections to the initial flow.Note that the function diagram is typically not un i que. Tn particular, subfunctions can often be ordered in different ways to produce d i fferent function diagrams. Also note that in some applications the material , energy, and signal flows are difficult to identify. In these cases, a simple list of the subfunctions of the product, without c01mections between them , is often sufficient.Functional decomposition is most applicable to technical prod u cts, but i t can also be applied to simple and apparently nontechnica l products. For example, an ice cream scoop has material flow of ice cream be i ng separated, formed, transported, and deposited. These subfunctions could form the basis of a problem decomposition .Functional decomposition is only one of several possible ways to divide a problem into simpler subproblems. Two other approaches are:• Decomposition by sequence of user actions: For example, the nailer probl em mi gh t be broken down into three user actions: moving the tool to the gross nailing position, positioning the tool precisely, and triggering the tool. This approach is often useful for products with very simple technical functions involving a lot of user interaction.• Decomposition by key customer needs: For the nailer, this decomposition might include the following subproblems: fires nails in rapid succession, is lightweight, and has a large nail capacity. This approach is often useful for products in which form, and not worki ng principles or technology, is the primary problem. Examples of such products incl ude toothbrushes (assuming the basic brush concept is retained) a n d storage containers.
การแปล กรุณารอสักครู่..
