James Robertson

Tom DeMarco

Tim Lister

Steve McMenamin

Suzanne Robertson

Peter Hruschka

This is the digital version of the printed book (Copyright © 2008). Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies . . . Most developers, testers, and managers on IT projects are pretty good at recognizing patterns of behavior and gut-level hunches, as in, “I sense that this project is headed for disaster.” But it has always been more difficult to transform these patterns and hunches into a usable form, something a team can debate, refine, and use. Until now. In Adrenaline Junkies and Template Zombies, the six principal consultants of The Atlantic Systems Guild present the patterns of behavior they most often observe at the dozens of IT firms they transform each year, around the world. The result is a quick-read guide to identifying nearly ninety typical scenarios, drawing on a combined one-hundred-and-fifty years of project management experience. Project by project, you’ll improve the accuracy of your hunches and your ability to act on them. The patterns are presented in an easy-reference format, with names designed to ease communication with your teammates. In just a few words, you can describe what’s happening on your project. Citing the patterns of behavior can help you quickly move those above and below you to the next step on your project. You’ll find classic patterns such as these: News Improvement Management by Mood Ring Piling On Rattle Yer Dags Natural Authority Food++ Fridge Door and more than eighty more! Not every pattern will be evident in your organization, and not every pattern is necessarily good or bad. However, you’ll find many patterns that will apply to your current and future assignments, even in the most ambiguous circumstances. When you assess your situation and follow your next hunch, you'll have the collective wisdom of six world-class consultants at your side.

Understanding Patterns of Project Behavior

Adrenaline Junkies and Template Zombies

Gernot Starke

Knigge für Softwarearchitekten

Derek Hatley

Imtiaz Pirbhai

This is the digital version of the printed book (Copyright © 2000). Derek Hatley and Imtiaz Pirbhai—authors of Strategies for Real-Time System Specification—join with influential consultant Peter Hruschka to present a much anticipated update to their widely implemented Hatley/Pirbhai methods. Process for System Architecture and Requirements Engineering introduces a new approach that is particularly useful for multidisciplinary system development: It applies equally well to all technologies and thereby provides a common language for developers in widely differing disciplines. The Hatley-Pirbhai-Hruschka approach (H/H/P) has another important feature: the coexistence of the requirements and architecture methods and of the corresponding models they produce. These two models are kept separate, but the approach fully records their ongoing and changing interrelationships. This feature is missing from virtually all other system and software development methods and from CASE tools that only automate the requirements model. System managers, system architects, system engineers, and managers and engineers in all of the diverse engineering technologies will benefit from this comprehensive, pragmatic text. In addition to its models of requirements and architecture and of the development process itself, the book uses in-depth case studies of a hospital monitoring system and of a multidisciplinary groundwater analysis system to illustrate the principles. Compatibility Between the H/H/P Methods and the UML: The Hatley/Pirbhai architecture and requirements methods—described in Strategies for Real-Time System Specification—have been widely used for almost two decades in system and software development. Now known as the Hatley/Hruschka/Pirbhai (H/H/P) methods, they have always been compatible with object-oriented software techniques, such as the UML, by defining architectural elements as classes, objects, messages, inheritance relationships, and so on. In Process for System Architecture and Requirements Engineering, that compatibility is made more specific through the addition of message diagrams, inheritance diagrams, and new notations that go with them. In addition, state charts, while never excluded, are now specifically included as a representation of sequential machines. These additions make definition of the system/software boundary even more straightforward, while retaining the clear separation of requirements and design at the system levels that is a hallmark of the H/H/P methods—not shared by most OO techniques. Once the transition to software is made, the developer is free to continue using the H/H/P methods, or to use the UML or any other software-specific technique.

Process for System Architecture and Requirements Engineering

Chris Rupp

"Agility kompakt" zeigt eine alternative Sicht auf die Schwerpunkte in der Software- und Systementwicklung. Agilität richtet die Wertvorstellungen stärker auf die Zusammenarbeit von Menschen, auf mehr direkte Kommunikation, Ergebnisorientierung und rasches Feedback. Prozesse und Werkzeuge dürfen nicht fehlen, rücken aber in den Hintergrund. Das Buch regt Sie an, aus dem Alltag der Software-Entwicklung aufzusehen und Ihre eigenen Praktiken im Licht agiler Grundsätze zu überprüfen. Lesen Sie, wie sich diese geänderten Wertvorstellungen auf alle Projektbeteiligten auswirken – von Auftraggebern und Kunden über die Projektleitung bis hin zu Analytikern, Designern und Programmierern. Neu in der 2. Auflage: aktueller Stand der agilen Methoden und Hilfestellung für eine angemessene Mischung aus Agilität und Disziplin für Ihre Projekte.

Tipps für erfolgreiche Systementwicklung

Agility kompakt

Steven McMenamin

Understanding and Improving the Culture at Work

Happy to Work Here

Software Architektur kompakt gibt Ihnen alles, was Sie zu einem reibungslosen und schnellen Start in das Thema benötigen. Lernen Sie Systeme zukunftssicher, flexibel und transparent zu konstruieren. Sie finden hier sofort einsetzbare und erprobte Muster und Vorlagen zur Erstellung praxistauglicher IT-Architekturen. Das Buch liefert allen relevanten Projektbeteiligten maßgeschneiderte Antworten zu Entwurfsentscheidungen, Systemstruktur und Implementierung.

- angemessen und zielorientiert

Software-Architektur kompakt

Wir alle wollen schlanke, effektive Geschäftsprozesse und optimale IT-Unterstützung. Wir finden für jedes Problem eine Lösung – wenn wir uns nur genau darauf einigen könnten, was unser Problem ist. Das Verstehen von Problemen und das Formulieren von Anforderungen, was wir gerne anders hätten, ist das Thema dieses Buches. Viele verschiedene Begriffe werden dafür verwendet (Business Analysis, Systemanalyse, Requirements Engineering, ...) und viele Berufsbezeichnungen für die Beteiligten. Dieses Buch zeigt einen integrierten Ansatz zum Umgang mit Anforderungen. Es stellt Ihnen Methoden, Notationen und viele pragmatische Tipps (Best Practices) zur Verfügung, mit denen Anforderungen effektiv zwischen Auftraggebern und Auftragnehmern behandelt werden können – von Entdeckungstechniken über Dokumentationstechniken, Prüftechniken bis hin zu Verwaltungstechniken.

Produkte und Prozesse nachhaltig verbessern

Business Analysis und Requirements Engineering

Peter Hruschka

Books

Your next favorite book is out there