Uml Explained - Couverture souple

UML Explained is an approachable, non-technical introduction to the Unified Modeling Language (UML), the standard graphical notation for modeling the elements, structure, and behaviors of object-oriented software systems.

Assuming no prior knowledge of the UML, object-oriented design, or programming fundamentals, this book fully explains basic concepts and terminology such as objects, classes, and use cases. It shows how the UML integrates with an iterative and incremental process. Numerous sample UML diagrams and a running example throughout the book help you understand how to apply the UML to real-world software development. Also included is a comprehensive glossary of important terms.

You will learn about such essentials as:

• The importance of visual modeling
• How the UML identifies objects and classes
• Capturing requirements and defining use cases with the UML
• How to extend the UML and enhance visual models
• Modeling the details of object behavior with activity diagrams and statechart diagrams
• Component and deployment diagrams

Whether you are a non-technical professional who needs to understand software development activities within the workplace or a system designer who has never worked with the UML before, UML Explained is the perfect place to start.

There are dozens of Unified Modeling Language (UML) books, but virtually all of them assume their readers have significant experience with modeling or object-oriented development. Not this one. Written by the co-author of the best selling UML Distilled, this book is utterly authoritative -- and it's also the simplest, least technical guide to UML ever written. With it, every participant in the modeling process can learn to master UML, starting from scratch. Begin by understanding the real value of modeling in software development and other endeavors, and how UML was explicitly designed to support iterative and incremental processes. Watch a project team use UML to identify the real-world objects associated with their business problem; capture scenarios that describe user actions and system responses ("use cases"); and define a system's functional requirements. Learn how UML helps teams identify relationships amongst objects that must be implemented to address a system's requirements. Next, use UML to describe business and process workflows; to determine how all of a system's objects will work together; and to specify how a distributed software system will actually be built.