If you want to use Visio to create enterprise software, this is the book for you.

The integration of Visual Studio .NET Enterprise Architect and Visio for Enterprise Architects provides a formidable tool. Visio offers powerful diagramming capabilities, including such things as creating UML models, mapping out databases with Entity Relationship diagrams, and aiding the development of distributed systems. Its integration with Visual Studio .NET Enterprise Architect means that C# or Visual Basic .NET code can be generated from the UML diagrams, and Visual Studio .NET projects can be reverse engineered to UML models.

For the developer already familiar with UML and looking to get the best out of Visio, the Visual Studio .NET and Visio for Enterprise Architects combination is weakly documented, and the quality information needed to realize the time-saving features of Visio just does not seem to be available, until now.

This book presumes that you are already familiar with the basic concepts of UML notation — this book will not teach you UML. Instead, this book will take you forward into the Visio environment, showing you how to make the most of its software related features.

Use Case Driven Object Modeling with UML–Theory and Practice shows how to drive an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. In addition to a comprehensive explanation of the foundations of the approach, the book makes extensive use of examples and provides exercises at the back of each chapter.

This book leads by example. It demonstrates common analysis and design errors, shows how to detect and fix them, and suggests how to avoid making the same errors in the future. The book also encourages you to examine its UML examples and to search for specific errors. You'll get clues, then later receive the answers during "review sessions" toward the end of the book.

After a quick introduction to the design process Catalysis, this book moves on to carefully defining objects, their attributes, operations, and collaborations. (Generally, Catalysis objects and components are "decoupled" so that they can work more independently, leading to easier reuse and customization.)

The authors then turn to modeling and design, using a spreadsheet program as their example. Next, the authors discuss component-based design, where projects are assembled with components. The book closes with an effective tour of the actual Catalysis design process, illustrated with a case study for a video-rental store. All design documents, written in the Unified Modeling Language (UML), are provided along with some useful expert advice on creating better design documents and components.

Judging from the evidence here, the Catalysis design method can offer some real advantages for today's software, which often must evolve to meet unforeseen requirements (international markets or new platforms such as the Web). Designed according to the principles outlined in the book, components and designs can offer a higher level of reuse. Even if you do not actually adopt the Catalysis process, this authoritative and admirably clear book offers a wealth of design expertise for anyone interested in being more productive with objects and UML

The Unified Modeling Language (UML) is the standard modeling language for software and systems development. This statement alone is a pretty conclusive argument for making UML part of your software repertoire, however it leaves some questions unanswered. Why is UML unified? What can be modeled? How is UML a language? And, probably most importantly, why should you care?

Systems design on any reasonably large scale is difficult. Anything from a simple desktop application to a full multi-tier enterprise scale system can be made up of hundredsand potentially thousandsof software and hardware components. How do you (and your team) keep track of which components are needed, what their jobs are, and how they meet your customers' requirements? Furthermore, how do you share your design with your colleagues to ensure the pieces work together? There are just too many details that can be misinterpreted or forgotten when developing a complex system without some help. This is where modelingand of course UMLcomes in.

Component-based software development regards software construction in terms of conventional engineering disciplines where the assembly of systems from readily-available prefabricated parts is the norm. Because both component-based systems themselves and the stakeholders in component-based development projects are different from traditional software systems, component-based testing also needs to deviate from traditional software testing approaches.

Gross first describes the specific challenges related to component-based testing like the lack of internal knowledge of a component or the usage of a component in diverse contexts. He argues that only built-in contract testing, a test organization for component-based applications founded on building test artifacts directly into components, can prevent catastrophic failures like the one that caused the now famous ARIANE 5 crash in 1996. Since building testing into components has implications for component development, built-in contract testing is integrated with and made to complement a model-driven development method. Here UML models are used to derive the testing architecture for an application, the testing interfaces and the component testers. The method also provides a process and guidelines for modeling and developing these artifacts.

Attacks against computer systems can cause considerable economic or physical damage. High-quality development of security-critical systems is difficult, mainly because of the conflict between development costs and verifiable correctness.
Jürjens presents the UML extension UMLsec for secure systems development. It uses the standard UML extension mechanisms, and can be employed to evaluate UML specifications for vulnerabilities using a formal semantics of a simplified fragment of UML. Established rules of security engineering can be encapsulated and hence made available even to developers who are not specialists in security. As one example, Jürjens uncovers a flaw in the Common Electronic Purse Specification, and proposes and verifies a correction.
With a clear separation between the general description of his approach and its mathematical foundations, the book is ideally suited both for researchers and graduate students in UML or formal methods and security, and for advanced professionals writing critical applications.

"Enterprise Modeling and Computing with UML" bridges two fields that are closely related, but 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. "Enterprise Modeling and Computing with UML" shows both the potential and the limit of using UML in an enterprise modeling context and a broad spectrum of ideas for aligning the development of information systems with the management of an enterprise.

The purpose of large-scale software architecture is to capture and describe practical representations to make development teams more effective.
In this book the authors show how to utilise software architecture as a tool to guide the development instead of capturing the architectural details after all the design decisions have been made.

    * Offers a concise description of UML usage for large-scale architecture
    * Discusses software architecture and design principles
    * Technology and vendor independent

Introduced in 1997, the Unified Modeling Language (UML) has rapidly been accepted throughout the software industry as the standard graphical language for specifying, constructing, visualizing, and documenting software-intensive systems. The UML provides anyone involved in the production, deployment, and maintenance of software with a standard notation for expressing a system’s blueprint. The UML covers conceptual things, such as business processes and system functions, as well as concrete things, such as programming-language classes, database schemas, and reusable software components.

In The Unified Modeling Language User Guide, the original developers of the UML, Grady Booch, James Rumbaugh, and Ivar Jacobson, provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning. Starting with a conceptual model of the UML, the book progressively applies the UML to a series of increasingly complex modeling problems across a variety of application domains. This example-driven approach helps readers quickly understand and apply the UML. For more advanced developers, the book includes a learning track focused on applying the UML to advanced modeling problems.

Fully updated to cover Rational Rose 2002, this third edition of Quatrani’s classic besteller, retains the highly effective and simple approach to visual modeling
Thoroughly updated and fully compliant with Rational Rose 2002, the latest release of the industrys most popular software modeling tool.
Simplified, useful case study helps the reader understand the core concepts of modeling and how to use UML effectively.
Foreword by Grady Booch. The third edition of this popular book retains the practical approach to teaching visual modeling techniques and the industry standard Unified Modeling Language. Author Terry Quatrani, the Rose Evangelist from Rational Software Corporation, still uses the simplified case study (a course registration system for a fictional university) that has taught thousands of readers how to analyze and design an application using UML, and how to implement the application using Rational Rose. The screen shots and Rational Rose instructions have been updated to reflect the release of Rational Rose 2002. After a short history of the evolution of UML and a guide to the basic terms of software engineering, the book introduces the concept of requirements, use cases, and class diagrams. Further chapters move toward defining an architecture and even refining the design within the incremental methodology of Rational Rose.
Terry Quatrani is the Rose Evangelist at Rational Software Corporation, and author of the first two editions of this book. She is responsible for successfully training and transitioning Fortune 500 companies to object technology. Prior to joining Rational, she worked for General Electric, where she worked with Jim Rumbaugh and was one of the founding consultants of the GE Advanced Concepts Center.