￥11,709 税込

ポイント: 117pt (1%) 詳細はこちら

無料配送 6月8日-13日にお届け
詳細を見る

お届け先を選択

通常3～4日以内に発送します。在庫状況について

￥￥11,709 () 選択したオプションを含めます。最初の月の支払いと選択されたオプションが含まれています。詳細

出荷元

桃空堂

出荷元

桃空堂

販売元

桃空堂

（1件の評価）

販売元

桃空堂

（1件の評価）

支払い方法

お客様情報を保護しています

支払い方法

お客様情報を保護しています

Amazonはお客様のセキュリティとプライバシーの保護に全力で取り組んでいます。Amazonの支払いセキュリティシステムは、送信中にお客様の情報を暗号化します。お客様のクレジットカード情報を出品者と共有することはありません。また、お客様の情報を他者に販売することはありません。詳細はこちら

詳細はこちら

すべて見る

￥1,427 税込

▼ 東京より発送 ▼ 紙面：見返しに字消印・シール等による消し跡・数頁に鉛筆等の書込みあり▼ 全体的に若干使用感・スレキズ・薄ヤケ・薄汚れ少々 ▼ 東京より発送 ▼ 紙面：見返しに字消印・シール等による消し跡・数頁に鉛筆等の書込みあり▼ 全体的に若干使用感・スレキズ・薄ヤケ・薄汚れ少々一部を表示

配送料 ¥350 6月1日-2日にお届け（14 時間 44 分以内にご注文の場合）
詳細を見る

お届け先を選択

残り1点ご注文はお早めに在庫状況について

￥￥11,709 () 選択したオプションを含めます。最初の月の支払いと選択されたオプションが含まれています。詳細

選択した拡張機能は、この出品者では利用できません。詳細

${cardName}は選択した出品者では利用できません

${maxQuantity}より大きい数量の場合は${cardName}は使用できません。

この商品は、ノースブックセンター（不備・不具合があれば返品・返金対応致します）が販売、発送します。

Amazonの他の出品者

新品＆中古品 (21)件の出品：￥1,427 + ￥350 配送料

画像はありません

選択したカラーの画像がありません。
カラー：

このビデオを見るには、次をダウンロード Flash Player

著者をフォローする

Evaluating Software Architectures: Methods and Case Studies (SEI Series in Software Engineering) ハードカバー – イラスト付き, 2001/10/22

英語版 Mark Clements, Paul Kazman, Rick Klein (著)

4.3 20個の評価

すべての形式と版を表示

このページの読み込み中に問題が発生しました。もう一度試してください。

{"desktop_buybox_group_1":[{"displayPrice":"￥11,709","priceAmount":11709.00,"currencySymbol":"￥","integerValue":"11,709","decimalSeparator":null,"fractionalValue":null,"symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"T0kKWtFs3Y67vkFoXzp0c2TV0ZV%2FiZrTJeEMfmLv4B1ERL%2BWYrt7%2BuNQnKcCCNSL9RRzc8TzunmwaCH8DmB4AsxNZ6jfYFmzuiGdWAodGzoxCaDjluulYQ6Xbmjk6deHSG5PVl4aDFvoVb6bOkk4tAlCZPsCqf%2BLQrQnyVWI5YRvOPrjVbrInY%2B%2Boch%2FGxoC","locale":"ja-JP","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}, {"displayPrice":"￥1,427","priceAmount":1427.00,"currencySymbol":"￥","integerValue":"1,427","decimalSeparator":null,"fractionalValue":null,"symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"T0kKWtFs3Y67vkFoXzp0c2TV0ZV%2FiZrTv7YRGW2vWs%2F110zjTyuR%2F1p9t7PbPlu8wbR3AXAZKrgKTK4cAyA44xozK2lH737U5I9UI5mPNcFgBBOT5mawsV1UFb99mRnz5jO%2F4x41o79fvx8O770Q%2F8f8B0Cehvm4jGFK8COOMrOwO2cl%2BTH%2BRg%3D%3D","locale":"ja-JP","buyingOptionType":"USED","aapiBuyingOptionIndex":1}]}

購入オプションとあわせ買い

The foundation of any software system is its architecture. Using this book, you can evaluate every aspect of architecture in advance, at remarkably low cost -- identifying improvements that can dramatically improve any system's performance, security, reliability, and maintainability. As the practice of software architecture has matured, it has become possible to identify causal connections between architectural design decisions and the qualities and properties that result downstream in the systems that follow from them. This book shows how, offering step-by-step guidance, as well as detailed practical examples -- complete with sample artifacts reflective of those that evaluators will encounter. The techniques presented here are applicable not only to software architectures, but also to system architectures encompassing computing hardware, networking equipment, and other elements. For all software architects, software engineers, developers, IT managers, and others responsible for creating, evaluating, or implementing software architectures.

この商品に関する問題を報告する

本の長さ

368ページ
言語

英語
出版社

Addison-Wesley Professional
発売日

2001/10/22
寸法

24.33 x 16.64 x 2.24 cm
ISBN-10

020170482X
ISBN-13

978-0201704822
すべての詳細を表示

商品の説明

著者について

Paul Clements is a senior member of the technical staff at the SEI, where he works on software architecture and product line engineering. He is the author of five books and more than three dozen papers on these and other topics.

Rick Kazman is a senior member of the technical staff at the SEI. He is also an Associate Professor at the University of Hawaii. He is the author of two books, editor of two more, and has written more than seventy papers on software engineering and related topics.

Mark Klein is a senior member of the technical staff at the SEI. He is an adjunct professor in the Masters of Software Engineering program at Carnegie Mellon and a coauthor of A Practitioner's Handbook for Real-time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems (Kluwer Academic Publishers, 1993).

020170482XAB01162003

登録情報

出版社 ‏ : ‎ Addison-Wesley Professional; 第1版 (2001/10/22)
発売日 ‏ : ‎ 2001/10/22
言語 ‏ : ‎ 英語
ハードカバー ‏ : ‎ 368ページ
ISBN-10 ‏ : ‎ 020170482X
ISBN-13 ‏ : ‎ 978-0201704822
寸法 ‏ : ‎ 24.33 x 16.64 x 2.24 cm

Amazon 売れ筋ランキング: - 780,820位洋書 (洋書の売れ筋ランキングを見る)
- - 455位Software Engineering Methodology
- - 691位Computer Systems Analysis & Design
- - 854位Object-Oriented Design

カスタマーレビュー:
4.3 20個の評価

著者について

著者をフォローして、新作のアップデートや改善されたおすすめを入手してください。

Paul Clements
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう
著者ページでもっと見る
Rick Kazman
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう
著者ページでもっと見る

カスタマーレビュー

5つのうち4.3つ

20グローバルレーティング

星3つ

0%

星2つ

0%

星1つ

9%

評価はどのように計算されますか?

この商品をレビュー

カスタマーレビューを書く

他の国からのトップレビュー

すべてのレビューを日本語に翻訳

Dr. Gernot Starke

Foundation of ATAM (a method for software architecture evaluation)

2006年10月27日にドイツでレビュー済み

Amazonで購入

The authors, members of the highly respected SEI staff, compiled their experience on their own ATAM method into this practical book, which supersedes a huge number of SEI whitepapers and articles on ATAM.

If you plan to evaluate software architectures: Get the book, read and digest it and you will surely learn a lot to ease your task. You'll not learn everything, though! ATAM, as all evaluation methods, strongly relies on experience, both technical and business-related!

ATAM concentrates only on "documented" architectures, it does not take code or running software into account - which imho seriously lacks practicality.

The book gives some examples for evaluations - but those imho do not provide advice for your own evaluations, especially when it comes to scenario generation - maybe the author improve this in a future edition :-)

In my own reviews and audits I usually complement ATAM by other evaluation techniques, like code-inspections, document-reviews, interviews, risk-assessments or the like.

Sumamry: MUST-read for everybody who's involved in methodical architecture evaluation and review, whereas the ATAM method does imho not cover everythig you'll need for such tasks.

8人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

Kathirvel

Looks like a library copy

2021年7月10日にインドでレビュー済み

Amazonで購入

while ordering it's mentioned as a new book. But I received a very old book. It looks like a library copy and a very old edition.

レビューを日本語に翻訳する

wiredweird

Depends on what you want.

2004年7月1日にアメリカ合衆国でレビュー済み

Amazonで購入

What this book does, it does very well. It presents three techniques for reviewing the suitability of a software architecture. The presentation style is clear, complete, and reasonably frank about the problems an architecture evaluator is likely to encounter.
The oldest of the three techniques presented is SAAM, the Software Architecture Analysis Model. It's primary goal is to determine how well a system's structure addresses the technical requirements of the application, and its probable success at addressing future changes of requirements.
ATAM, the Architecture Tradeoff Analysis Method, descends from SAAM but is far more complete. It starts upstream of the requirements, at the business model behind the application, then moves forward methodically through the top-level design. At each step, reviewers update the list of technical risks and non-risks (relatively safe items). ATAM is open-ended, in the sense that the project's own goals define the specific measures of quality that apply - it doesn't force-fit every project onto one Procrustean axis of measure.
If ATAM is SAAM grown large, then ARID (Active Reviews for Intermediate Design) is SAAM scaled down. Where ATAM and SAAM address strategic issues about complete systems, ARID incorporates tactical information about specific design issues. It's not as narrow as standard design review techniques, but not as broad as an architecture review.
ATAM is the main focus of the book, with more pages than SAAM and ARID combined. All three are described in full detail, however. The authors identify the specific skill sets, roles, and responsibilities that must be involved at each step. They present checklists for eliciting the kinds of information needed, even specifics of meeting agendas and meeting room equipment.
That creates my second impression of this book: I was very disappointed. This book is for meeting organizers, and deals very little with technical specifics. That is not at all what I hoped for. It is not the fault of the book that it fails to meet my expectations. In my present work, however, the authors present just about nothing to enhance my project's technical content.
This is a process book. It seems to be a good one. It takes what works in other design review methodologies, then expands that to the highest level of the software project. It gives enough detail that you can tune specifics of the process to specifics of your project. Still, it's just a process book.

19人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

Paul Fowler

Viable methods for evaluating software, however, starting to show its age...

2016年1月20日にアメリカ合衆国でレビュー済み

Amazonで購入

It could be updated. It is on a 12th printing, and some of the content is showing its age. However, on the whole it provides a viable set of methods for evaluating software architectures from SEI - that is the purpose, after all. I recommend reading this book before the "green book" which is the Documenting Software Architectures book, only because that is the order in which they appear to have been authored. If you read this book second, some of the architectural style information which needs updating will annoy you. If you have to choose between the two books, I would recommend the Green Book.

1人のお客様がこれが役に立ったと考えています

レビューを日本語に翻訳する

Bazmundi

Core technique for architecture tradeoffs

2014年4月1日にアメリカ合衆国でレビュー済み

Amazonで購入

Use of basic tools for trading off different aspects of an architecture are a necessary part of a software engineer's skill set. Good solid work comes from SEI and this book is no exception.

レビューを日本語に翻訳する

レビューをすべて見る

Amazon Advertising 商品の露出でお客様の関心と反応を引き出す	Audible（オーディブル）「聴く」読書会員なら聴き放題	アマゾンウェブサービス（AWS）クラウドコンピューティングサービス	Amazonアウトレット訳あり商品をお手頃価格で販売

Amazonビジネス（法人購買）請求書払い法人価格・数量割引	AmazonGlobal 65か国/地域以上への海外配送がより簡単に	Shopbop 世界中の厳選されたファッションアイテム

著者をフォローする

Evaluating Software Architectures: Methods and Case Studies (SEI Series in Software Engineering) ハードカバー – イラスト付き, 2001/10/22

購入オプションとあわせ買い

商品の説明

著者について

登録情報

著者について

Paul Clements

Rick Kazman

カスタマーレビュー

この商品をレビュー

上位レビュー、対象国： 日本

他の国からのトップレビュー

上位レビュー、対象国：日本