The Impact of Standards on Design| OKWAVE

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Standard force the design to conform to some widely agreed-upon requirements that may or may not be appropriate for that particular design. Though standards are essential to allow interoperability and can reduce costs by promoting competition, poorly designed standards severely restrict the design space. Worse yet, an underspecified standard may lead to faulty implementations that are not even interoperable. A good example of a bad standard is the Q.2931 standard for signaling in ATM networks. The standard is unnecessarily complex, and therefore hard to implement and hard to modify. Yet, to succeed in the marketplace, switch manufacturers have to obey it, thus slowing the rate at which ATM networks spread.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Besides constraints on these five resources, two major constraints are purely social :standards and market requirements. Standard force the design to conform to some widely agreed-upon requirements that may or may not be appropriate for that particular design. Though standards are essential to allow interoperability and can reduce costs by promoting competition, poorly designed standards severely restrict the design space. Worse yet, an underspecified standard may lead to faulty implementations that are not even interoperable. A good example of a bad standard is the Q.2931 standard for signaling in ATM networks. The standard is unnecessarily complex, and therefore hard to implement and hard to modify. Yet, to succeed in the marketplace, switch manufacturers have to obey it, thus slowing the rate at which ATM networks spread.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Besides constraints on these five resources, two major constraints are purely social :standards and market requirements. Standard force the design to conform to some widely agreed-upon requirements that may or may not be appropriate for that particular design. Though standards are essential to allow interoperability and can reduce costs by promoting competition, poorly designed standards severely restrict the design space. Worse yet, an underspecified standard may lead to faulty implementations that are not even interoperable. A good example of a bad standard is the Q.2931 standard for signaling in ATM networks. The standard is unnecessarily complex, and therefore hard to implement and hard to modify. Yet, to succeed in the marketplace, switch manufacturers have to obey it, thus slowing the rate at which ATM networks spread.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Besides constraints on these five resources, two major constraints are purely social :standards and market requirements. ・Standard force the design to conform to some widely agreed-upon requirements that may or may not be appropriate for that particular design. Though standards are essential to allow interoperability and can reduce costs by promoting competition, poorly designed standards severely restrict the design space. Worse yet, an underspecified standard may lead to faulty implementations that are not even interoperable. A good example of a bad standard is the Q.2931 standard for signaling in ATM networks. The standard is unnecessarily complex, and therefore hard to implement and hard to modify. Yet, to succeed in the marketplace, switch manufacturers have to obey it, thus slowing the rate at which ATM networks spread. ・Market requirements, like poorly designed standards, are unfortunate realities. A company may decide that products being designed must be backward-compatible with a previous product, or that they must use a particular operating system, or that they must support some set of standards. These essentially political decisions set the framework for a design. Market requirements may also determine the amount of human effort that can be expended on a design project. It is remarkable how much time is spent on building graphical user interfaces, sometimes at the expense of the system underlying the interface!

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 If we could quantify and control every aspect of a system, then system design would be a relatively simple matter. Unfortunately there are several practical reasons why system design is both an art and a science. First, although we can quantitatively measure some aspects of system performance, such as throughput or response time, we cannot measure others, such as simplicity, scalability, modularity, and elegance. Yet a designer must make a series of trade- offs among these intangible quantities, appealing as much to good sense and personal choice as performance measurements. Second, rapid technological change can make constraint assumptions obsolete. A designer must not only meet the current set of design constraints, but also anticipate how future changes in technology might affect the design. The future is hard to predict, and a designer must appeal to instinct and intuition to make a design "future-proof." Third, market conditions may dictate that design requirements change when part of the design is already complete. Finally, international standards, which themselves change over time, may impose irksome and arbitrary constraints. These factors imply that, in real life, a designer is usually confronted with a complex, underspecified, multifactor optimization problem. In the face of these uncertainties, prescribing the one true path to system design is impossible.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Market requirements, like poorly designed standards, are unfortunate realities. A company may decide that products being designed must be backward-compatible with a previous product, or that they must use a particular operating system, or that they must support some set of standards. These essentially political decisions set the framework for a design. Market requirements may also determine the amount of human effort that can be expended on a design project. It is remarkable how much time is spent on building graphical user interfaces, sometimes at the expense of the system underlying the interface!

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 The last constraint, scaling, is different from the others in that it constrains, not resources, but design elements. A centralized design, that is, a design that incorporates a single point of storage or control, is limited to the storage or processing capacity of the central point. Thus, an arbitrarily scalable design must minimize its use of centralized elements. This forces such designs to use distributed algorithms for control and coordination. Of course, a distributed system has its own problems, such as communication overhead and complex interconnection. Scaling is hard to measure, and arguments about whether a design can scale verge on the religious. Nevertheless, history shows that a system must scale well if it is to succeed.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 The last constraint, scaling, is different from the others in that it constrains, not resources, but design elements. A centralized design, that is, a design that incorporates a single point of storage or control, is limited to the storage or processing capacity of the central point. Thus, an arbitrarily scalable design must minimize its use of centralized elements. This forces such designs to use distributed algorithms for control and coordination. Of course, a distributed system has its own problems, such as communication overhead and complex interconnection. Scaling is hard to measure, and arguments about whether a design can scale verge on the religious. Nevertheless, history shows that a system must scale well if it is to succeed.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Market requirements, like poorly designed standards, are unfortunate realities. A company may decide that products being designed must be backward-compatible with a previous product, or that they must use a particular operating system, or that they must support some set of standards. These essentially political decisions set the framework for a design. Market requirements may also determine the amount of human effort that can be expended on a design project. It is remarkable how much time is spent on building graphical user interfaces, sometimes at the expense of the system underlying the interface!

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 System design is important not only in computer systems, but also in other areas, such as automobile design. For example, a car designer might try to maximize the reliability of a car(measured in the mean time between equipment failures) that costs less than $10,000 to build. In this example, the mean time between failures measures performance, and the resource constraint is money. In real life, of course, designs must try to simultaneously optimize many, possibly conflicting metrics (such as reliability, performance, and recyclability) while satisfying many constraints (such as the price of the car and the time allowed for the design).

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 By explicitly identifying performance metrics and resource constraints, a system designer ensures that the design space is well defined, the solution is feasible, and the design is efficient. She can then trade unconstrained resources for constrained ones to maximize the design's utility at the least cost. Continuing with our example, a system designer might use the PC's surplus computational power to compress data as much as possible, to best exploit the limited capacity of the transmission link. A well-designed system maximizes achievable performance while still satisfying the resource constraints.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Nevertheless, it is still, possible to identify some principles of good design that have withstood the test of time and are applicable in a variety of situations. In Section6.2, we will study some common resources, so that the reader can get some intuition in identifying them in real systems. We will then build up, in Section6.3, a set of tool to help us trade freely available (unconstrained) resources for scarce (constrained) ones. Properly applied, these tools allow us to match the design to the constraints at hand. Finally, in Section6.4, we will outline a methodology for performance analysis and tuning. This methodology helps pinpoint problems in a design and build a more efficient and robust system.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Consider a building that has two floors, with an escalator to carry people from one floor to the other. Ignoring queuing delays, the response time for a passenger is the mean time taken by the escalator to ascend or descend one floor. The throughput (bandwidth) is the mean number of passengers that can be loaded or per second. Suppose that an average of five people step on the escalator in one second, and that the escalator takes an average of 10 seconds to go up one floor. The response time for a passenger, therefore, is 10 seconds, and the throughput of the escalator is 5 passengers/second. Thus, the degree of parallelism, which is the mean number of passengers carried simultaneously, is 5*10=50. To see this, mark a passenger with a daub of red paint as she steps on the escalator. In the ten seconds that she takes to reach the top, we expect that fifty more passengers boarded the escalator. Thus, when she steps off, the escalator carries an average of fifty passengers, which is its degree of parallelism.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Labor is the human effort required to design and build a system. No amount of money can compensate for the lack of trained labor. Given a labor constraint, a designer must decide which parts of the design need the most work, and which can be ignored. Unfortunately, the labor constraint is one of the least understood and ignored constraints on engineering design.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 In any system, some resources are less constrained than others. We call the most constrained resource in a system(or the binding constraint) its bottleneck. System performance improves if and only if we devote additional resources to a bottlenecked resource. Conversely, decreasing the amount of an unconstrained resource does not adversely affect performance. When we relieve one bottleneck, however, it is possible for another resource to become a bottleneck. Thus, we must remove the bottlenecks one by one until all the resources are equally constrained. We call such a system a balanced system. A balanced system is optimal, in that we fully utilize every component. However, in practice, we rarely achieve balanced systems. Rapid changes in technology, market constraints, and customer expectations mean that a system's components are almost constantly in flux, with the bottleneck moving from place to place in the system.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Assume that we want to increase the speed with which we can store data on a tape drive attached to a computer through an I/O bus. The three components affecting the speed are the CPU, the I/O bus, and the tape-drive write mechanism. Measurements may show that the slowest component in the system is the tape drive. Then, no matter how fast the CPU or the I/O bus, system performance will not improve unless the tape drive's performance improves. Suppose we now replace the drive with a faster one. Then, we may find that the I/O bus is too slow to match the tape drive. The bottleneck resource, therefore, is now the I/O bus. We must improve the I/O bus to match the drive speed, perhaps, by using a different I/O bus technology (of course, this might require us to change the tape drive to be compatible with the new bus!). This process continues until we meet the performance target or run out of time or money. Ideally, the I/O bus, drive, and CPU will simultaneously reach their maximum performance, so that the system is balanced.

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Time can constrain a design in many ways. For example, a user may require a task to complete before a given time, or may want to limit the time taken for a packet to travel from a source to a destination. At a different level, there may be a time constraint on how long it can take to design and build a system (time-to-market). Or, we may want to maximize the mean time between failures. We now study some standard ways to measure the use of time in a system.

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 Consider an airline reservation system, where agents from any part of the world can make a reservation for seats on any flight on any airline. One design for this system is to send all reservation requests to a single central computer. This design is simple, but has two problems. First, if the central computer crashes, every agent is affected. Second, as the number of agents increases, we need to expand the capacity of the central computer. However, the number of reservation requests, particularly during peak travel periods, may increase beyond the capacity of the largest computer that we can build or buy. Then, the response time suffers, and system performance degrades. We can solve this problem by replacing the central computer with a set of regional reservation center that coordinate among themselves to maintain a consistent view of the system state(such as whether a night is full or not). Then, as the number of reservation requests increases, we can just add another reservation center. We must, however, pay for this with a communication overhead for coordination, and a complex network to interconnect the regional reservation centers.

翻訳お願いします

以下の英文の翻訳をしていただけるかた、お願いできますでしょうか。部分的におかしなところがありましたら意訳でもかまいません。よろしくお願いします。 Your moon is in Scorpio, his in Aquarius, Your emotional natures and needs are different. This can be resolved, through learning to accept each other. However, you are both quite fixed in your own ways and are not always receptive to changing unless it is on your own terms. Emotions are a powerful force in your life and you can become obsessed with a feeling or a desire, and yet you are practical, restrained too. You find it hard to forget an forgive. While this man will seem a little more detached. Inwardly you are stormy, full of turmoil that doesn’t always show outwardly, while he is calm and collected both inside and outwardly. Your intensity may be met in a cool, dispassionate, highly rational way. He will seem to need the relationship, the future less than you, but it is not so, he will always keep coming back.

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の文章です。 Consider a building that has two floors, with an escalator to carry people from one floor to the other. Ignoring queuing delays, the response time for a passenger is the mean time taken by the escalator to ascend or descend one floor. The throughput (bandwidth) is the mean number of passengers that can be loaded or per second. Suppose that an average of five people step on the escalator in one second, and that the escalator takes an average of 10 seconds to go up one floor. The response time for a passenger, therefore, is 10 seconds, and the throughput of the escalator is 5 passengers/second. Thus, the degree of parallelism, which is the mean number of passengers carried simultaneously, is 5*10=50. To see this, mark a passenger with a daub of red paint as she steps on the escalator. In the ten seconds that she takes to reach the top, we expect that fifty more passengers boarded the escalator. Thus, when she steps off, the escalator carries an average of fifty passengers, which is its degree of parallelism.

The Impact of Standards on Design

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

質問者が選んだベストアンサー

関連するQ&A

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

日本史の転換点？：赤穂浪士、池田屋事件、禁門の変に見る武士の忠義と正義

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイト

翻訳お願いします

卒論に使用するため、翻訳をお願いしたいです。コンピューター関係の書物の

注目のQ&A

カテゴリ

あなたにピッタリな商品が見つかる！ OKWAVE セレクト

専門家に質問してみよう