oder
Loggen Sie sich ein, um 1-Click® einzuschalten.
oder
Mit kostenloser Probeteilnahme bei Amazon Prime. Melden Sie sich während des Bestellvorgangs an. Erfahren Sie mehr
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Farbe:
Keine Abbildung vorhanden

 
Den Verlag informieren!
Ich möchte dieses Buch auf dem Kindle lesen.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Agile Documentation: A Pattern Guide to Producing Lightweigth Documents for Software Projects: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) [Englisch] [Taschenbuch]

Andreas Ruping
3.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)
Preis: EUR 28,90 kostenlose Lieferung. Siehe Details.
  Alle Preisangaben inkl. MwSt.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Auf Lager.
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
Lieferung bis Freitag, 21. Juni: Wählen Sie an der Kasse Morning-Express. Siehe Details.

Kurzbeschreibung

10. November 2010 Wiley Software Patterns Series
Software documentation forms the basis for all communication relating to a software project. To be truly effective and usable, it should be based on what needs to be known. Agile Documentation provides sound advice on how to produce lean and lightweight software documentation. It will be welcomed by all project team members who want to cut out the fat from this time consuming task. Guidance given in pattern form, easily digested and cross-referenced, provides solutions to common problems.
 
Straightforward advice will help you to judge:
* What details should be left in and what left out
* When communication face-to-face would be better than paper or online
* How to adapt the documentation process to the requirements of individual projects and build in change
* How to organise documents and make them easily accessible
* When to use diagrams rather than text
* How to choose the right tools and techniques
* How documentation impacts the customer
 
Better than offering pat answers or prescriptions, this book will help you to understand the elements and processes that can be found repeatedly in good project documentation and which can be shaped and designed to address your individual circumstance. The author uses real-world examples and utilises agile principles to provide an accessible, practical pattern-based guide which shows how to produce necessary and high quality documentation.

Hinweise und Aktionen

  • Studienbücher: Ob neu oder gebraucht, alle wichtigen Bücher für Ihr Studium finden Sie im großen Studium Special. Natürlich portofrei.



Produktinformation

  • Taschenbuch: 246 Seiten
  • Verlag: Wiley; Auflage: 1. Auflage (10. November 2010)
  • Sprache: Englisch
  • ISBN-10: 0470856173
  • ISBN-13: 978-0470856178
  • Größe und/oder Gewicht: 18,9 x 1,5 x 23,6 cm
  • Durchschnittliche Kundenbewertung: 3.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)
  • Amazon Bestseller-Rang: Nr. 201.840 in Englische Bücher (Siehe Top 100 in Englische Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

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

Produktbeschreibungen

Pressestimmen

"...many (Test Documents) would benefit from this treatment..." (Professional Tester, October 03)

Synopsis

Software documentation forms the basis for all communication relating to a software project. To be truly effective and usable, it should be based on what needs to be known. Agile Documentation provides sound advice on how to produce lean and lightweight software documentation. It will be welcomed by all project team members who want to cut out the fat from this time consuming task. Guidance given in pattern form, easily digested and cross-referenced, provides solutions to common problems. Straightforward advice will help you to judge: What details should be left in and what left out When communication face-to-face would be better than paper or online How to adapt the documentation process to the requirements of individual projects and build in change How to organise documents and make them easily accessible When to use diagrams rather than text How to choose the right tools and techniques How documentation impacts the customer Better than offering pat answers or prescriptions, this book will help you to understand the elements and processes that can be found repeatedly in good project documentation and which can be shaped and designed to address your individual circumstance.

The author uses real-world examples and utilises agile principles to provide an accessible, practical pattern-based guide which shows how to produce necessary and high quality documentation.


Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Einleitungssatz
Before we plunge into the actual patterns, I'd like to take a brief look at the projects from which the patterns in this book were mined. Lesen Sie die erste Seite
Mehr entdecken
Wortanzeiger
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Eine digitale Version dieses Buchs im Kindle-Shop verkaufen

Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen. Weitere Informationen

Kundenrezensionen

5 Sterne
0
4 Sterne
0
2 Sterne
0
1 Sterne
0
3.0 von 5 Sternen
3.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
0 von 3 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Not what I thought, but OK 23. Dezember 2009
Format:Taschenbuch
I had hoped to get some ideas on how to manage the documentation process for the handbooks of a software that is developed using agile processes. However, this is not what this book is about as it clearly states in its foreword. Instead it focuses on principles (or patterns) for project documentation in the development teams.

The book is structured clearly and it's easy to identify sections of interest and skip the rest.

I don't think it is a must-have book, but it gives some good ideas how to concentrate on the important things for development documentation.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 3.6 von 5 Sternen  7 Rezensionen
7 von 8 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Documentation, But not very agile 28. Oktober 2007
Von Ken - Veröffentlicht auf Amazon.com
Format:Taschenbuch|Von Amazon bestätigter Kauf
Ruping did a good job of covering the topic of software documentation, albeit somewhat generically, i.e. not that specific to software development. He quotes a lot of others in his book and identifies that the goal (of agile documenting) is 'light-weight but sufficient'. If you're working on developing a system for documenting software development (or really any other technical project) this would make a good reference, but start at the back of the book. He uses patterns in his book as his technique to cover the topic. They are recognized problems and solutions, and he lists all of them in the back of the book in thumbnail form. The middle of the book provides the elaboration. The first part of the book is his professional history (sorry Ruping, but not that interesting), and his how-to-use-the-book section.
The problem I had with the book is that I didn't see anything new and innovating. I didn't have an `ah-ha' moment where I finally understood the real principles behind 'agile' documentation. I didn't find this book 'agile' at all. I also did not agree with all of his solutions, most seemed cliché. But again, if you're looking for a reference on the topic of technical documentation - this is not bad.
3 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Great concept 7. Mai 2008
Von Daniel Baker - Veröffentlicht auf Amazon.com
Format:Taschenbuch|Von Amazon bestätigter Kauf
As a tech communicator with long experience in various engineering environments, I am enthused about the concepts espoused here. We need to write "documentation" the way we like to read "documentation"; it needs to have the content needed particularly by us, in the style we need, and concise and to the point when our need begs for that. We need to look toward long term relevance and up-to-dateness - of all technical information, especially technical reference information, and it is more likely to be so if it is concise and focused to start with. We are all scanners, doing stuff or acquiring information in a hurry, doing tasks in a hurry. Another book told about how a new guy on a project was given a thick document about the project. Two days later, he had a headache; couldn't get the picture. If he were given an agile-ly written doc, he would have gotten the picture. Ginny Redish (Letting Go of the Words) is another great one along the same thinking.

ONE distractor: He wrote the book with a bit of his own fluff. Maybe to give the book a slight bit of thickness. Could have been more to the point. An engineer I used to work with used to say "paid by the pound".
2 von 2 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Disappointing, but ok for the intended reader 14. November 2012
Von J. Birkinshaw - Veröffentlicht auf Amazon.com
Format:Taschenbuch|Von Amazon bestätigter Kauf
As a professional technical writer I was hoping to find insights on how to do my job in an Agile development environment, as my experience is in the slower-moving "waterfall" types of development. The book clearly says early on, but you couldn't tell from the description online, that it's really more about the design documentation that the development and test people will need to use among themselves. I wish I'd had a chance to borrow and skim for 10 minutes, I would have saved my money.

Given what it is, it's a good primer for developers to use for specs and so on. If those are well-done, the end-user docs are much easier to craft, so I'd recommend it to the intended audience.
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
 


Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   
Ähnliche Foren


Lieblingslisten


Ähnliche Artikel finden


Ihr Kommentar


Datenschutzerklärung von Amazon.de Versandbedingungen von Amazon.de Umtausch- & Rücknahme bei Amazon.de