CD-ROM contains: Java and XML implementations of ideas and models described in the appendix.

UML (Unified Modeling Language) ist ein leistungsfähiges Tool für die Entwurfsplanung von objektorientierten Computersystemen. Mit seiner Hilfe kann der Zeitaufwand für die Software-Entwicklung enorm reduziert werden. Entsprechend groß ist daher nicht nur die Nachfrage nach UML für firmeninterne Systementwicklung sondern auch nach praktischer Anleitung für den richtigen Einsatz von UML. Dies ist der Nachfolgeband des sehr erfolgreichen Titels "UML Toolkit" von Eriksson und Penker. Er konzentriert sich auf die brandaktuellen komponenten-orientierten Konzepte und erklärt, wie man OCL (Object Constraint Language) von UML für Business Rules und Business Views einsetzt. Dokumentiert sind 27 hilfreiche Business Patterns. (cat06/99)

This book presents a variant of UML that is especially suitable for agile development of high-quality software. It adjusts the language UML profile, called UML/P, for optimal assistance for the design, implementation, and agile evolution to facilitate its use especially in agile, yet model based development methods for data intensive or control driven systems. After a general introduction to UML and the choices made in the development of UML/P in Chapter 1, Chapter 2 includes a definition of the language elements of class diagrams and their forms of use as views and representations. Next, Chapter 3 introduces the design and semantic facets of the Object Constraint Language (OCL), which is conceptually improved and syntactically adjusted to Java for better comfort. Subsequently, Chapter 4 introduces object diagrams as an independent, exemplary notation in UML/P, and Chapter 5 offers a detailed introduction to UML/P Statecharts. Lastly, Chapter 6 presents a simplified form of sequence diagrams for exemplary descriptions of object interactions. For completeness, appendixes A–C describe the full syntax of UML/P, and appendix D explains a sample application from the E-commerce domain, which is used in all chapters. This book is ideal for introductory courses for students and practitioners alike.

Diagramming and process are important topics in today’s software development world, as the UML diagramming language has come to be almost universally accepted. Yet process is necessary; by themselves, diagrams are of little use. Use Case Driven Object Modeling with UML - Theory and Practice combines the notation of UML with a lightweight but effective process - the ICONIX process - for designing and developing software systems. ICONIX has developed a growing following over the years. Sitting between the free-for-all of Extreme Programming and overly rigid processes such as RUP, ICONIX offers just enough structure to be successful.

XML is rapidly becoming the standard platform for delivering e-Business information and integrating e-Business systems. XML developers desperately need mature software development processes and tools for developing effective applications. David Carlson fills the gap, showing exactly how to leverage the worldwide UML standard for modeling complex systems in advanced XML development. In Modeling XML Applications with UML, he presents the first comprehensive framework for modeling communications in any B2B software system. Carlson presents in-depth coverage of UML-based analysis, design, and modeling of XML content within e-Business environments. The book includes detailed coverage of using UML to support the creation of new XML-based B2B vocabularies and industry portals that reflect the requirements of several key stakeholder communities, including consumers, business analysts, web application specialists, system integration specialists, and content developers. Carlson presents several B2B use cases, and then decomposes them into scenarios illustrated with class diagrams, sequence diagrams, and activity diagrams showing how XML fits into an overall e-Business solution. Each chapter concludes with "steps for success" that distill UML's general principles into specific recommendations for action.

"This book bridges two fields that, although closely related, are often studied in isolation: enterprise modeling and information systems modeling. The principal idea is to use a standard language for modeling information systems, UML, as a catalyst and investigate its potential for modeling enterprises"--Provided by publisher.

This book provides you with a collection of best practices, guidelines, and tips for using the Unified Modeling Language (UML) for business analysis. The contents have been assembled over the years based on experience and documented best practices. Over sixty easy to understand UML diagram examples will help you to apply these ideas immediately. If you use, expect to use, or think you should use the Unified Modeling Language (UML) or use cases in your business analysis activities, this book will help you: communicate more succinctly and effectively with your stakeholders including your software development team, increase the likelihood that your requirements will be reviewed and understood, reduce requirements analysis, documentation, and review time. The first three chapters explain the reasons for utilizing the UML for business analysis, present a brief history of the UML and its diagram categories, and describe a set of general modeling guidelines and tips applicable to all of the UML diagram types. Each of the next thirteen chapters is dedicated to a different UML diagram type: Use Case Diagrams Activity Diagrams Interaction Overview Diagrams Class Diagrams Object Diagrams State Machine Diagrams Timing Diagrams Sequence Diagrams Communication Diagrams Composite Structure Diagrams Component Diagrams Deployment Diagrams Package Diagrams The next two chapters explain additional diagram types that are important for business analysts and that can be created using UML notation: Context Diagrams using Communication diagram notation Data Models using Class diagram notation These chapters are followed by a chapter that describes criteria for selecting the various diagram types. The final chapter presents a case study.