• ベストアンサー
  • すぐに回答を!

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

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

noname#112516
noname#112516

共感・応援の気持ちを伝えよう!

  • 英語
  • 回答数2
  • 閲覧数38
  • ありがとう数13

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

  • ベストアンサー
  • 回答No.1

前後のコンテクストがないのでちょっとあってるかどうか不安ですがやってみます... 「ひどい設計基準であるような市場必需品はひどいものである。ある会社は今設計されている製品は前の製品との下位互換性がなければならないと決断するかもしれないし、もしくは製品が特定のOSをつかったり、ある一定の基準をサポートしてなければならないとするかもしれない。 これらの必要不可欠な政治的決断が設計の枠組みを決める。 市場必需品はまたその設計プロジェクトに費やされる人的費用の量も左右するかもしれない。 よくあるようなインタフェースの基礎をなすシステムを犠牲にしてまで、GUI構築にたくさんの時間が費やされることを思うと驚きです。」 下手ですいません。Market requirementsというのがうまく訳せませんでした。 おそらく最後の一文がこの文の主張だと思います。

共感・感謝の気持ちを伝えよう!

その他の回答 (1)

  • 回答No.2

No.1です。backward-compatibileの訳を間違えました。 下位互換ではなく”後方互換”でした。すいません。

共感・感謝の気持ちを伝えよう!

関連するQ&A

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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