Model-driven development has become the most important new paradigm in software development and has already demonstrated considerable impact in reducing time to market and improving product quality. However, the development of high-quality systems not only requires systematic development processes but also systematic test processes.

This book is about systematic, model-driven test processes in the context of UML. As UML provides only limited means for the design and development of test artifacts, a consortium was formed by the Object Management Group (OMG) to develop a UML profile for model-driven testing the UML Testing Profile (UTP), an official OMG standard since 2005.

Written by the original members of this standardization group, this book shows you how to use UML to test complex software systems. The authors introduce UTP step-by-step, using a case study that illustrates how UTP can be used for test modeling and test specification. Youll learn how UTP concepts can be used for functional and non-functional testing, with example applications and best practices for user-interfaces and service oriented architectures. In addition, the authors demonstrate how to apply UTP using frameworks like TTCN-3 and the JUnit test framework for Java.

(more…)

The Object Primer is a straightforward, easy-to-understand introduction to agile software development (ASD) using object-oriented (OO) and relational database technologies. It covers the fundamental concepts of ASD and OO and describes how to take an agile approach to requirements, analysis, and design techniques applying the techniques of the unified modeling language (UML) 2 as well as other leading-edge techniques, including agile model–driven development (AMDD) and test-driven development (TDD) approaches.

During the 1990s OO superceded the structured paradigm as the primary technology paradigm for software development. Now during the 2000s ASD is superceding traditional, prescriptive approaches to software development. While OO and ASD are often used to develop complex systems, learning them does not need to be complicated. This book is different from many other introductory books about these topics—it is written from the point of view of a real-world developer, someone who has lived through the difficulty of learning these concepts.

This book is aimed at two primary audiences—existing developers and university/college students who want to gain the fundamental skills required to succeed on modern software development projects. Throughout this book I use the term "developer" broadly: a developer is anyone involved in the development of a software application. This includes programmers, analysts, designers, business stakeholders, database administrators, support engineers, and so on. While many people would not include business stakeholders in this, my experience is that active business stakeholder involvement is often the key determinant to the success of a software project. Business stakeholders can actively participate in requirements engineering, analysis, and sometimes, in design—it is clear to me that they should be considered developers. Call me a radical.

In this book, you will find a survey of the latest software development techniques and a wealth of knowledge to get you started on the road to agile. Those new to this community will find an overview of the critical areas of the agile software movement. This book will help you become more productive. The agile principles inside will change the way that you view software development and, ultimately, the way you build software.

(more…)

Model-driven development has become the most important new paradigm in software development and has already demonstrated considerable impact in reducing time to market and improving product quality. However, the development of high-quality systems not only requires systematic development processes but also systematic test processes.

This book is about systematic, model-driven test processes in the context of UML. As UML provides only limited means for the design and development of test artifacts, a consortium was formed by the Object Management Group (OMG) to develop a UML profile for model-driven testing – the UML Testing Profile (UTP), an official OMG standard since 2005.

Written by the original members of this standardization group, this book shows you how to use UML to test complex software systems. The authors introduce UTP step-by-step, using a case study that illustrates how UTP can be used for test modeling and test specification. You’ll learn how UTP concepts can be used for functional and non-functional testing, with example applications and best practices for user-interfaces and service oriented architectures. In addition, the authors demonstrate how to apply UTP using frameworks like TTCN-3 and the JUnit test framework for Java.

This book is the definitive reference for the only UML-based test specification language, written by the creators of that language. It is supported by an Internet site that provides information on the latest tools and uses of the profile.

(more…)

The Unified Modeling Language (UML), the standard graphical notation for modeling business and software application needs, has emerged as an effective modeling tool for database design. When used as a common modeling language for the many facets of system development, the UML can serve as a unifying framework that facilitates the integration of database models with the rest of a system design.

This pragmatic guide introduces you to the UML and leads you through the process of UML-based database modeling and design. The book presents the different types of UML diagrams, explaining how they apply to the database world, and shows how data modeling with the UML can be tied into the Rational Unified Process.

(more…)

Domain Architectures is a comprehensive catalog of the domain architectures essential to software developers using object-oriented technology and UML to solve real-life problems. Providing a unique top-down view of systems, the book also provides quick access to landmarks and references to domain architectures.

The ability to describe applications, in terms of the properties they share, offers software designers a vast new landscape for implementing software reuse. The ideal professional's handbook.

(more…)

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.

(more…)

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.

(more…)

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

(more…)

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.

(more…)

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.

(more…)