• ベストアンサー
※ ChatGPTを利用し、要約された質問です(原文:翻訳をお願いしたいです。コンピューター関係の書物の文章です。)

The Complexity of System Design: An Art and a Science

harimao777の回答

回答No.2

翻訳ソフトにかけてみましたら、こんな感じでした。 もし私達がシステムのすべての面を定量化し、コントロールできるならば、システム設計は相対的に簡単な問題であるでしょう。 あいにく、システム設計がアートと科学であるいくつかの実用的な理由があります。 私達はシステム・パフォーマンスのいくつかの面を定量的に測定できるけれども、1番目は、シンプルさ、スケーラビリティ、モジュール性、優雅さなど、スループットまたは応答時間、私達など、他を測定できません。 まだ、デザイナーは、これらの無形の量の間の貿易-offsのシリーズを作らなければならず、性能寸法と同じくらい多く分別および個人的な選択にアピールします。 第二に、急速な技術的な変化は強制仮定を時代遅れにすることができます。 デザイナーはデザイン制約の現在のセットに遭遇してはならないだけであるけれども、どのようにテクノロジーの未来の変化がデザインに影響するかもしれないかも予期してください。 未来は予測しづらく、デザイナーは、デザインを「未来証拠。」にすることを本能と直観に懇願しなければなりません。 3番目、すでにデザインの一部が完全な時には、市況はそのデザイン要件変化を表しているかもしれません。 最後に、国際標準 which 自身 時間の間の変化 は、やっかいなおよび任意の制約を課すことができます。 これらのファクターは、本当のライフに通常デザイナーが複雑で、仕様書で決められたより以下で、多因子の最適化問題と対侍するのを暗示しています。 これらの不確定要素の面前で、唯一の真実のパスをシステム設計に規定することが不可能です。

関連するQ&A

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 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.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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).

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 A system designer must typically optimize one or more performance metrics given a set of resource constrains. A performance metric measures some aspect of a system's performance, such as throughput, response time, cost development time, or mean time between failures(we will define these metrics more formally in Section 6.2). A resource constraint is a limitation on a resource, such as time, bandwidth, or computing power, that the design must obey.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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).

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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!

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 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.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。 A successful design cannot cost more than what the market can bear. This affects the choice of components used in building the system, the number of engineers assigned to the task, and the time available. Moreover, to achieve economies of scale, the design must be manufacturable at a reasonable cost. All these considerations affect the design.

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

    翻訳をお願いしたいです。コンピューター関係の書物の文章です。翻訳サイトのコピペはご遠慮ください。 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.