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

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.

Today, information-technology business analysts are often working on object-oriented (OO), Unified Modeling Language (UML) projects, yet they have a long way to go to exploit the technology beyond the adoption of use cases (just one part of the UML). This book explains how, as an IT business analyst, you can pull together all of the UML tools and fully utilize them during your IT project. Rather than approaching this topic theoretically, you will actually learn by doing: A case study takes you through the entire book, helping you to develop and validate the requirements for an IT system step by step. Whether you are a new IT business analyst; an experienced analyst, but new to the UML; a developer who is interested in expanding your role to encompass IT business-analysis activities; or any other professional tasked with requirements gathering or the modeling of the business domain on a project, you'll be trained and mentored to work efficiently on UML projects in an easy-to-understand and visual manner. This new edition has been completely updated for UML 2.2, and includes coverage of all the relevant new BABOK 2 knowledge areas. The new edition also covers various lifecycle approaches (non-empirical, empirical, waterfall, iterative, and agile) and their impact on the way project steps are carried out.

The development of an information system comprises three iterative and incremental phases: analysis, design and implementation. This book describes the methods and techniques used in the analysis and design phases.

"This book manages to convey the practical use of UML 2 in clear and understandable terms with many examples and guidelines. Even for people not working with the Unified Process, the book is still of great use. UML 2 and the Unified Process, Second Edition is a must-read for every UML 2 beginner and a helpful guide and reference for the experienced practitioner." --Roland Leibundgut, Technical Director, Zuehlke Engineering Ltd. "This book is a good starting point for organizations and individuals who are adopting UP and need to understand how to provide visualization of the different aspects needed to satisfy it. " --Eric Naiburg, Market Manager, Desktop Products, IBM Rational Software This thoroughly revised edition provides an indispensable and practical guide to the complex process of object-oriented analysis and design using UML 2. It describes how the process of OO analysis and design fits into the software development lifecycle as defined by the Unified Process (UP). UML 2 and the Unified Process contains a wealth of practical, powerful, and useful techniques that you can apply immediately. As you progress through the text, you will learn OO analysis and design techniques, UML syntax and semantics, and the relevant aspects of the UP. The book provides you with an accurate and succinct summary of both UML and UP from the point of view of the OO analyst and designer. This book provides Chapter roadmaps, detailed diagrams, and margin notes allowing you to focus on your needs Outline summaries for each chapter, making it ideal for revision, and a comprehensive index that can be used as a reference New to this edition: Completely revised and updated for UML 2 syntax Easy to understand explanations of the new UML 2 semantics More real-world examples A new section on the Object Constraint Language (OCL) Introductory material on the OMG's Model Driven Architecture (MDA) The accompanying website provides A complete example of a simple e-commerce system Open source tools for requirements engineering and use case modeling Industrial-strength UML course materials based on the book

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)

Thousands of software projects are doomed because they're based on a faulty understanding of the business problem that needs to be solved. Requirements Analysis: From Business Views to Architectureis the solution. David C. Hay brings together the world's best requirements analysis practices from two key viewpoints: system development life cycle and architectural framework. Hay teaches you the complete process of defining an architecture - from a full understanding of what business people need to the creation of a complete enterprise architecture.