In weniger als einer Minute können Sie mit dem Lesen von Competitive Engineering auf Ihrem Kindle beginnen. Sie haben noch keinen Kindle? Hier kaufen oder mit einer unserer kostenlosen Kindle Lese-Apps sofort zu lesen anfangen.

An Ihren Kindle oder ein anderes Gerät senden

 
 
 

Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Farbe:
Keine Abbildung vorhanden
 

Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage [Kindle Edition]

Tom Gilb
5.0 von 5 Sternen  Alle Rezensionen anzeigen (4 Kundenrezensionen)

Kindle-Preis: EUR 34,11 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

Kostenlose Kindle-Leseanwendung Jeder kann Kindle Bücher lesen  selbst ohne ein Kindle-Gerät  mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.

Geben Sie Ihre E-Mail-Adresse oder Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 34,11  
Taschenbuch EUR 45,96  

Kunden, die diesen Artikel gekauft haben, kauften auch

Seite von Zum Anfang
Diese Einkaufsfunktion wird weiterhin Artikel laden. Um aus diesem Karussell zu navigieren, benutzen Sie bitte Ihre Überschrift-Tastenkombination, um zur nächsten oder vorherigen Überschrift zu navigieren.

Produktbeschreibungen

Pressestimmen

"This stuff works. Competitive Engineering contains powerful tools that are both practical and simple - a rare combination. Over the last decade, I have applied Tom Gilb's tools in a variety of settings including product development, service delivery, manufacturing, site construction, IT, eBusiness, quality marketing, and management, on projects of various sizes. Thousands of engineers have been through Competitive Engineering training and Planguage workshops that I have authored. The vast majority of students immediately recognize their value and go on to use them beneficially on projects. Competitive Engineering is based on decades of practical experience, feedback, and improvement, and it shows." - Erik Simmons, Intel Corporation, Requirements Engineering Practice Lead, Corporate Quality Network "Fundamentally, the book presents a new take on best practices in systems engineering and management. The book passed my value-added test, when I realized that I was photocopying several pages for future reference, to be part of my "toolkit" of helpful tips and techniques. I particularly enjoyed reading the 10 often witty, summary principles in each chapter.Perseverance pays off with Competitive Engineering. The book is not a quick read, which Tom acknowledges. You have to carefully study some of the pages to understand the concepts being presented. The reward occurs when you glean the nuggets of wisdom from the numerous practical examples, case studies, and Planguage examples. Tom's way of presenting the CE concepts makes the book a useful addition to the systems engineer's library." - Jerry Huller, Raytheon "I found Planguage to be an interesting and noble idea for the enhancement of communication in the product development environment.Systems engineering professionals wanting another perspective on applying SE techniques to real product development and those wanting to add additional techniques/ methods to their toolbox will gain most from this book. Readers should have a fundamental knowledge of systems engineering principles and some practical product development experience to realize the full value of this work. I found the chapters describing "Impact Estimation", "Evolutionary Project Management" and "Specification Quality Control" to be specifically relevant and ripe for application to various product development environments. Overall, the book passes my acid test as a useful reference for Systems engineering professionals... Tom meets his objectives in providing a current definition of Planguage concepts and providing a handbook of fundamental SE principles ready for application with his practical experience and unique product development perspective." - Martin Coe President-Closed Loop Engineering, Technical Program Director- INCOSE Colorado ".for those professionals serious about tackling the requirements specification effort in any real project. I am excited about it. He offers his Planguage for structuring the system engineering process and gets at issues of risk, success and failure criteria and evolutionary project development in a rational way. This book is a must read, re-read and study for students and practitioners working in the murky area of mapping the problem domain to the solution domain.It is, as promised, a Handbook. Buy it, and you will use it. It will not collect dust on your bookshelf. This book is a wonderful contribution to our Software Engineering literature." - ACM SIGSOFT Software Engineering Notes, January 2006 "Competitive Engineering is an original, experience-based, stimulating, thought-provoking, entertaining, and well worth reading software engineering book." - IMPROVE, Software Process Improvement Newsletter "Tom Gilb, the father of the Evo methodology, shares his practical, real-world experience for enabling effective collaboration between developers, managers and stakeholders. Although the book describes Planguage (a specification language for systems engineering) in detail, the methodological advice alone is worth the price of the book. Evo is one of the truly underappreciated agile methodologies, and as a result, Gilb's thought-provoking work isn't as well-known as it should be, although I suspect that that will change with this book. The book describes effective practices for requirements and design specification that are highly compatible with the principles and practices of Agile Modeling, yet it goes on to address planning activities, quality and impact estimation. I suspect that this book will prove to be one of the "must read" software development books of 2006." - SD's Agile Modeling Newsletter, February 2006, By Scott W. Ambler, Ambysoft "I found the rules, principles, and process descriptions associated with the Planguage method particularly interesting and helpful." - Jayesh G. Dalal, Software Quality Professional, June-August 2006

Kurzbeschreibung

Competitive Engineering documents Tom Gilb's unique, ground-breaking approach to communicating management objectives and systems engineering requirements, clearly and unambiguously.

Competitive Engineering is a revelation for anyone involved in management and risk control. Already used by thousands of project managers and systems engineers around the world, this is a handbook for initiating, controlling and delivering complex projects on time and within budget. The Competitive Engineering methodology provides a practical set of tools and techniques that enable readers to effectively design, manage and deliver results in any complex organization - in engineering, industry, systems engineering, software, IT, the service sector and beyond.

Elegant, comprehensive and accessible, the Competitive Engineering methodology provides a practical set of tools and techniques that enable readers to effectively design, manage and deliver results in any complex organization - in engineering, industry, systems engineering, software, IT, the service sector and beyond.

* Provides detailed, practical and innovative coverage of key subjects including requirements specification, design evaluation, specification quality control and evolutionary project management
* Offers a complete, proven and meaningful 'end-to-end' process for specifying, evaluating, managing and delivering high quality solutions
* Tom Gilb's clients include HP, Intel, CitiGroup, IBM, Nokia and the US Department of Defense

Produktinformation


Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Kundenrezensionen

4 Sterne
0
3 Sterne
0
2 Sterne
0
1 Sterne
0
5.0 von 5 Sternen
5.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
5 von 5 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Professionelle Software-Entwickler, System-Ingenieure und alle, die sich letztlich im ernsthaften Wettbewerb befinden kommen nicht an den Ideen vorbei, die in diesem Buch präsentiert werden. Dieses Buch ist für mich in vielerlei Hinsicht wie ein Augenöffner gewesen. Speziell Tom Gilbs Sicht auf Qualität und messbare Qualitätsmerkmale ist nahezu einzigartig. Die in diesem Buch präsentierten Regeln, Prozeduren und Prinzipien sind von unschätzbarem Wert im professionellen Umfeld. Sie spiegeln die in über 30(!) Jahren gesammelte Erfahrung in internationalen Großunternehmen wie z.B. Sun Microsystems, IBM, HP, Intel und Nokia wider. Als Sun Microsystems Mitarbeiter in der StarOffice Entwicklung kann ich bestätigen, dass der Inhalt dieses Buches einen nachhaltigen Einfluß auf die Arbeitsweise in der StarOffice Entwicklung hatte!
Ich möchte allerdings eine Warnung aussprechen. Dieses Buch ist nicht als Einschlaflektüre geeignet. Um den Inhalt dieses Buches zu erschließen, bedarf es Zeit und Konzentration. Der Gewinn ist allerdings enorm.
War diese Rezension für Sie hilfreich?
2 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Tom packt aus: Ein Buch mit Durchblick 11. Februar 2006
Format:Taschenbuch
Tom Gilb, den ich persoenlich kenne, stellt mit diesem buch (s)einen systematischen Ansatz fuer die effektive und effiziente entwicklung von produkten vor. kernelement seines ansatzes ist "planguage", ein formalisiertes, aber einfaches schema, mit dem praezise die fuer eine produktentwicklung notwendigen informationen erzeugt, verwaltet und kommuniziert werden koennen. damit stellt tom die kommunikation innerhalb einer produktentwicklung genau dahin, wo sie hingehoert: ins zentrum. "planguage" ist aber kein leerer formalismus, sondern hilft einem team dabei intelligent die notwendigen informationen zu verknuepfen. gerade hierbei schafft es tom nicht auf der rein technischen oder qualitaetssihcernden ebene stehen zu bleiben, sondern die wirtschaftlichen abwaegungen einzubeziehen. einfache und mit vielen weisheiten versehene regeln helfen auf kurs zu bleiben. absolut empfehlenswert fuer erfahrene ingenieure, entwickler und projektleiter, die ihre produktentwicklungen systematisieren wollen.
War diese Rezension für Sie hilfreich?
1 von 1 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Hier fällt mir zur Einleitung ein bekannter Witz ein:
Bill Gates und sein neu eingestelltes Mathe-Genie irren nach einen Flugzeugabsturz durch die Steppe Afrikas, als plötzlich ein Löwe auf Sie zustürzt. Das Mathe-Genie errechnet, dass er egal was er macht, spätestens in 17.4 sek vom Löwe angefallen wird und breitet sich darauf vor seinem Schöpfer zu begegnen. Verdutzt beobachtet er aber seinen Chef, der sich in den vermeidlichen letzten Sekunden seines Lebens die Stiefel auszieht. Darauf er: "Was soll das? Wir können nicht entkommen! Wir können nicht schneller laufen als der Löwe!" - Darauf Bill: "Ich muss auch nicht schneller laufen als der Löwe. Ich muss nur schneller laufen als DU!"

Unter diesen Tenor könnte man Tom Gilbs Werk "Competitive Engineering" zusammenfassen, der postuliert - 'Wir müsssen nicht überall die modernste Technologie, die höhste Prozessreife und sämtliche Standards etablieren, um erfolgreich zu sein. Wir müssen (sollten) nur einfach überall ein Schritt weiter sein als unsere Konkurrenz!'

Am Besten gefiel hierbei mir sein 'Doughnut' Diagramm, dass illustriert - wenn System eine bestimmte Performance überschreitet, befindet man sich sogar im 'Survival Level'!! Denn auf dem Olymp gibt es leider nur sehr wenige Kunden. - "Nur die Besten arbeiten mit den Besten zusammen, jemand der zweitklasssig ist, wird sogar nur mit Leuten zusammenarbeiten, die drittklassig sind!" (ehem. Mircosoft Mitarbeiter). Die Elite ist selten und es werden Aufwendungen betrieben, die in keinen Verhältnis zur Wertschöpfung stehen, entweder weil zuviel oder zu wenig ('Survival Level' Resource).
Lesen Sie weiter... ›
War diese Rezension für Sie hilfreich?
2 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Tom Gilb ist ein anerkannter Software Engineering Guru. Sein Buch "Software Metrics" (1976) war die Grundlage für Level 4 des Capability Maturity Models (CMM). Was er schreibt, sollten wir Systemingenieure und Softwareentwickler unbedingt kennen! Viele gescheiterte Softwareprojekte sind ein Beweis, dass unsere Arbeit alles andere als einfach ist. In "Competitive Engineering" stellt Tom Gilb die komplett ausgearbeiteten und in der Praxis erprobten Prinzipien und Methoden vor, mit denen wir das Risiko bei der Systementwicklung minimieren und den Nutzen für den Kunden maximieren können.
Überspitzt formuliert: wenn man sich an die Prinzipien aus "Competitive Engineering" hält, ist es gar nicht mehr so einfach, ein Projekt gegen die Wand zu fahren.
Genauso leicht wie ein Roman liest sich "Competitive Engineering" von Tom Gilb natürlich nicht, ganz im Gegenteil. Aber: wer sich um diese Lektüre drücken will, sollte mindestens sein Buch "Principles of Software Engineering Management" lesen, um einen Einblick in seine Gedankenwelt zu erhalten!
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.9 von 5 Sternen  14 Rezensionen
8 von 8 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Systems Engineering for Competitive Advantage 24. Oktober 2005
Von C. Haskins - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Competitive Engineering (CE) presents an updated contribution from Tom Gilb to the topics of systems engineering, software engineering and agile project execution. As a handbook, this work does not require the reader to have read prior works, although one is frequently invited to visit his website for additional information. From the title page, the reader receives an open invitation to enter into dialogue with [...].

Tom writes from a long practical background and with confidence that the Planguage Methods really work - if one is willing to give them a chance. However, this is not a new tyranny of methodology, but rather a rich tool set that can be adopted and adapted by a team or an organization.

The essential elements of Planguage are requirements specification (Chapters 2-6); Impact Estimation (Chapter 9), a technique unsurpassed in its ability to track the progress of a project toward achieving critical objectives; and evolutionary project management (Chapter 10), first introduced by Gilb in 1988. Specification Quality Control (Chapter 8) builds upon his earlier work on Inspections, see Gilb and Graham 1993. Chapter 7 discusses the design engineering process with cautionary advice about avoiding the trap of letting design specifications masquerade as requirements.

The book comes with a "friendly warning" that the ideas are presented in a very compact style. To ease the assimilation process, Tom includes a list of top 10 principles in each chapter. These pages, along with the "Twelve Tough Questions" in section 1.2, are worth the price of the book - but you may still want to read the supporting material for concrete suggestions about how to implement these principles. The book is also rich in diagrams and summary tables.

The objection most often levied by doubting readers is the uncompromising emphasis on quantification. Those who persevere should experience the benefits illustrated by the case studies that are an integral part each chapter. The title page of each chapter lists the key concepts that follow. One quarter of the book is comprised of the Context Glossary, which provides contextual definitions for those who struggle with the proliferation and occasionally contradictory use of terms in other literature.

CE is for anyone SERIOUS about improving communications within their development environment and thereby reaping the benefits of Competitive Engineering.
6 von 6 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Best Practices in Systems Engineering and Management 6. April 2006
Von Charles J. Huller - Veröffentlicht auf Amazon.com
Format:Taschenbuch
My interest in the topic of competitive engineering (CE) was piqued several years ago when I heard very favorable comments about Tom Gilb's tutorial on that subject at the INCOSE 2002 Symposium in Las Vegas.

The book's subtitle is "A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage". The term "Planguage" is central to an understanding of the book. Planguage, which is derived from a union of "plan" and "language", is the methodology for implementing CE. Much of the book is devoted to describing the generalized processes, rules, and vocabulary of Planguage. Tom notes, "Planguage should be viewed as a powerful way to develop and implement strategies that will help your projects to deliver the required competitive results." Fundamentally, the book presents a new take on best practices in systems engineering and management.

The book is useful on several levels. For organizations without a formal or documented process, tailoring of Planguage would jump start the process at a high level of maturity. For organizations that have achieved CMMI level 3 status, Planguage by itself is not as useful. However, many of the ideas of CE-the Planguage methods-are worth considering for enhancement of existing organizational processes. Tom states that CE is "about technological management, risk control, and breakthrough improvement in complex business systems, projects, and processes." CE is a believable approach for delivering complex projects on time and within budget.

The book passed my value-added test, when I realized that I was photocopying several pages for future reference, to be part of my "toolkit" of helpful tips and techniques. I particularly enjoyed reading the 10 often witty, summary principles in each chapter. Two examples are:

* The Principle of `Storage of Wisdom': "If your people are not all experienced or geniuses, You need to store their hard-earned wisdom in your defined process. Capture wisdom for reuse, Fail to write it, that's abuse!"

* The Principle of `The early bird catches the worm': "Your customers will be happier with an early long-term stream of their priority improvements, than years of promises, culminating in late disaster."

About 30% of the book is the Planguage Concept Glossary, which Tom views as a central contribution of the book. I focused my attention on the other, more interesting, parts of the book, which describe the main CE/Planguage methods of Requirement Specification (RS), Design Engineering (DE), Impact Estimation (IE), Specification Quality Control (SQC), and Evolutionary Project Management (EVO, also known as Evo). RS describes an approach for identifying all types of requirements while avoiding ambiguity and also planning for change. Functional and performance requirements are distinguished. DE deals with identifying, choosing, and prioritizing the order in which design ideas are implemented and delivered. In conjunction with Evo, DE selects the design ideas most likely to provide a significant benefit for early delivery.

SQC is an eminently practical approach for evaluating the quality of any technical document via sampling measurements. An hour of SQC early in a project can save almost 10 hours of rework. SQC also provides a means to assess the success of process improvement efforts. IE provides a realistic method for evaluating-in quantitative terms-the effectiveness of designs in meeting both the requirements, especially critical performance attributes, and the resource budgets.

Evo focuses on early, frequent delivery of project results via a series of high-value, small evolutionary steps. An ideal Evo approach would divide the project into a series of cycles. Each cycle would consume 2-5% of the total financial budget and 2-5% of the total project time-while delivering some measurable, required results to the stakeholders. The next cycle is selected to deliver the best stakeholder value for its cost (highest ratio of value to cost, or highest ratio of performance to cost). Although an ideal approach can't always be realized, Tom provides some convincing examples to argue that there is always a solution to making a project evolutionary (small steps with critical deliveries first).

Perseverance pays off with Competitive Engineering. The book is not a quick read, which Tom acknowledges. You have to carefully study some of the pages to understand the concepts being presented. The reward occurs when you glean the nuggets of wisdom from the numerous practical examples, case studies, and Planguage examples. Tom's way of presenting the CE concepts makes the book a useful addition to the systems engineer's library.
6 von 6 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A brilliant guide to complex systems development 13. August 2005
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format:Taschenbuch
A brilliant guide to complex systems development

Reviewer: Romilly Cocking from London, UK

This wonderful book explains how to deliver complex systems within time and budget, with a level of quality that will earn you a "wow!"

The book defines the five core processes of Competitive Engineering: Requirement Specification, Design Engineering, Specification Quality Control, Impact Estimation, and Evolutionary Project Management. It includes plenty of practical advice and lots of real-world examples. At the back you'll find a detailed glossary that contains precise definitions and detailed explanations of hundreds of the key concepts used in the book.

I loved the style, which is clear, practical and precise. I found it a demanding but very worthwhile read, not least because of the high density of ideas per chapter. There are things to think hard about on almost every page. Gilb's decades of practical experience in complex systems development are evident throughout the book.

Strongly recommended.
3 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Requirements Engineering Tamed 17. November 2005
Von L. Bernstein - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Tom Gilb's book, Competitive Engineering, is for those professionals serious about tackling the requirements specification effort in any real project. I am excited about it. He offers his Planguage for structuring the system engineering process and gets at issues of risk, success and failure criteria and evolutionary project development in a rational way. This book is a must read, re-read and study for students and practioners working in the murky area of mapping the problem domain to the solution domain. It provides suggested metrics, examples and ways of looking at problems. His "Twelve Tough Questions" listed on page 8 gets you focused and sets the stage for a well-written `how-to' book on separating user wants from their needs and setting the stage for potentially successful software projects. He makes failure part of the process on page 40. I loved his process diagram with the vertical right positioned arrow. It is a nice touch that reminds us that these processes are non-linear and contain feedback loops at every turn.

It is, as promised, a Handbook. Buy it, and you will use it. It will not collect dust on your bookshelf. This book is a wonderful contribution to our Software Engineering literature. It will be the basis for our CS 564 Requirements Engineering Course at Stevens Institute of Technology. Gilb shows us that software technology is maturing and his deep understanding of the field clearly emerges in his writing. So I urge you to click into your cart, now.
3 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen A massive source of ideas 13. August 2005
Von Matthew Leitch - Veröffentlicht auf Amazon.com
Format:Taschenbuch
There are people who suggest approaches to project management and design that seem more sophisticated or more grounded in generally accepted theory than Tom Gilb's. Tom's edge is that his ideas just work.

Competitive Engineering covers a huge range of topics clearly and with many detailed, helpful examples to show exactly what the techniques look like in practice.

My particular favourite is the section on design ideas. So much writing on systems engineering discusses design as if you can somehow analyse your way to the final design. I've always found that ideas are needed so the section on generating and sifting ideas is true to life and helpful to me.

The more you learn about Tom's methods the easier it is to see where so many organisations are going wrong.

Most people realise that getting benefits from systems projects is important but "benefits management" tends to be too superficial and too late to do much good. In Competitive Engineering Tom starts with the benefits to stakeholders and just never lets go.

This is a collection of techniques that work, put together into an overall, cohesive approach based on Tom's decades of consulting and invention.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   


Ähnliche Artikel finden