Written by the three pioneers behind the Unified Modeling Language (UML) standard, The Unified Modeling Language Reference Manual provides an excellent real-world guide to working with UML. This title provides expert knowledge on all facets of today's UML standard, helping developers who are encountering UML on the job for the first time to be more productive. The book begins with a history of UML, from structured design methods of the '60s and '70s to the competing object-oriented design standards that were unified in 1997 to create UML. For the novice, the authors illustrate key diagram types such as class, use case, state machine, activity, and implementation. (Of course, learning these basic diagram types is what UML is all about. The authors use an easy-to-understand ticket-booking system for many of their examples.) After a tour of basic document types, The Unified Modeling Language Reference Manual provides an alphabetical listing of more than 350 UML terms. Entries range from a sentence or two to several pages in length. (Class, operation, and use case are just a few of the important terms that are covered.) Though you will certainly need to be acquainted with software engineering principles, this reference will serve the working software developer well. As the authors note, this isn't UML for Dummies, but neither is it an arcane academic treatise. The authors succeed in delivering a readable reference that will answer any UML question, no matter how common or obscure. --Richard Dragan

The unified modelling language reference manual

We have integrated the feature modeling of Feature-Oriented Domain Analysis (FODA) into the processes and work products of the Reuse-Driven Software Engineering Business (RSEB). The RSEB is a use case driven systematic reuse process: architecture and reusable subsystems are first described by use cases and then transformed into object models that are traceable to these use cases. Variability in the RSEB is captured by structuring use case and object models using explicit variation points and variants. Traditional domain engineering steps have been distributed into the steps of the architectural and component system development methods of the RSEB. But the RSEB prescribes no explicit models of the essential features that characterize the different versions. Building on our experience in applying FODA and RSEB to the telecom domain, we have added explicit domain engineering steps and an explicit feature model to the RSEB to support domain engineering and component reuse. These additions provide an effective reuse oriented model as a 'catalog' capability to link use cases, variation points, reusable components and configured applications.

Integrating feature modeling with the RSEB

Consequently, public security and defense organizations can see the real-time locations of various people, units, and equipment in their GIS system, thanks to Global Positioning System (GPS) technology, while getting updates from SAP ERP with details about the current status and capabilities of those units, also updated in real-time as needed using enterprise services. With this bundle, users can create, maintain, and edit the relationships of organizational units (referred to in enterprise SOA terms as ) in public security and defense organizations (such as, for instance, Functional Units brigades, companies, and platoons), deployed or otherwise. In addition, they can read, change, and update the attributes of positions, personnel, and materials within these units.

Information system integration

"Per Kroll and Philippe Kruchten are especially well suited to explain the RUP...because they have been the central forces inside Rational Software behind the creation of the RUP and its delivery to projects around the world."--From the Foreword by Grady BoochThis book is a comprehensive guide to modern software development practices, as embodied in the Rational Unified Process, or RUP. With the help of this book's practical advice and insight, software practitioners will learn how to tackle challenging development projects--small and large--using an iterative and risk-driven development approach with a proven track record.The Rational Unified Process Made Easy will teach you the key points involved in planning and managing iterative projects, the fundamentals of component design and software architecture, and the proper employment of use cases. All team members--from project managers to analysts, from developers to testers--will learn how to immediately apply the RUP to their work. You will learn that the RUP is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes.Key topics covered include: How to use the RUP to develop iteratively, adopt an architecture-centric approach, mitigate risk, and verify software quality Tasks associated with the four phases of the RUP: Inception, Elaboration, Construction, and Transition Roles and responsibilities of project managers, architects, analysts, developers, testers, and process engineers in a RUP project Incrementally adopting the RUP with minimal risk Common patterns for failure with the RUP--and how to avoid themUse this book to get quickly up to speed with the RUP, so you can easily employ the significant power of this process to increase the productivity of your team.0321166094B03062003

The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP

This book looks at why ethnographic approaches are popular in the design of computing devices for the workplace, for the home and elsewhere. It presents a history of ethnography, both as it was practiced before computer science picked it up and since, most especially in the CSCW and HCI domains. The focus of the book is on the practical relationship between theory and practice, a relationship that is fundamental to successful design.

Fieldwork for Design: Theory and Practice

Foreword by James Martin Foreword by Dan L. Jonson Preface 1: Business engineering * Introduction * What is business engineering? * Why do we need business engineering? * What does the new company look like? * Business engineering, business (process) reengineering, and business improvement * Risk management * The future of business engineering in the corporate world * Summary * References 2: What is business modelling? * Introduction * What is a model? * What is a business model? * What does a business model look like? * A few words about the traditional way of modelling * Why do we need business modelling? * Who should have a business model, and why? * Working to develop a business model * Summary * References 3: What is object orientation? * Introduction * Object-oriented models * What is an object? * Objects are linked * Objects can form from aggregates * Objects belong to a class * One class can inherit other classes * A summary * Why is object orientation necessary? * Object orientation as a platform for the future * Object-oriented business modelling * Summary * References 4: Object-oriented business engineering - an overview * Introduction * Object-oriented business engineering in context * Business reengineering overview * The reengineering directive * Envisioning * The objective specification * Reversing the existing business * Engineering the new business * Installing the new process * Iteration * Business Improvement * Summary * References 5: Architecture * Introduction * What must you be able to express in a business model? * Internal and external models of business * The use-case model * The object model * Use case versus objects * Associations between use cases * More about use cases * Subsystems * Summary * References 6: Reversing the existing business * Introduction * Why reverse engineering? * Overview * Building a use-case model * Building an object model * Analyzing the result * Summary * References 7: Forward business engineering * Introduction * Building a use-case model * Object modeling * Interaction diagrams * Information system development * Verifying the new business * Summary * References 8: An example * Introduction * What do we want to change * What kind of organization do we have now? * New business processes * An object model of the new business * Work-flow descriptions * Summary * References 9: Building the supporting information system * Introduction * What is software development? * The software-development business-system objects * System development and business development * Procuring the new information-system support * Summary * References 10: Managing object-oriented business engineering * Introduction * Tailoring the method * Project organization and management * Project staffing * Organization staffing * Reviews * Summary * References 11: Scaling up to large businesses * Introduction * Two use-case models at different abstraction levels * Business system areas * Layered business models * Summary Glossary Index

Agneta Jacobson

Papers

The Object Advantage: Business Process Reengineering With Object Technology