Szczegóły ebooka

UML 2.0 in Action: A project-based tutorial. A detailed and practical book and eBook walk-through showing how to apply UML to real world development projects

UML 2.0 in Action: A project-based tutorial. A detailed and practical book and eBook walk-through showing how to apply UML to real world development projects

Philippe Baumann, Patrick Grassle, Henriette Baumann, Galileo Press GmbH

Ebook
Most books about UML describe it almost in its entirety. Inevitably you're left with only a superficial knowledge of the range of UML elements, without a deep and intuitive understanding of how to apply UML as a whole to real world design problems. This book doesn't set out to cover all of UML, but instead pulls together those parts of UML with immediate practical relevance and presents them as part of a coherent process for using UML in your actual development projects.This book is designed to be read while you work on a real project. After an initial review of the essentials of UML and the design process, it begins with the modeling of a business system and its business processes, in this case an airport. Then the IT system intended to serve that business process is described and analysed. Finally the integration of the system into the production environment is covered in detail. The book can be used in two ways: it can be read through as a thorough grounding in how UML really works in practice; in addition it can be used as stand alone guide to that particular aspect of your own project. Both result in an intuitive understanding of how to actually use UML.
  • UML 2.0 in Action A Project-Based Tutorial
    • Table of Contents
    • UML 2.0 in Action A Project-Based Tutorial
    • Credits
    • Preface
    • About the Authors
    • About This Book
      • What This Book Covers
      • Conventions
      • Reader Feedback
      • Customer Support
        • Errata
        • Questions
    • 1. Introduction
    • 2. Basic Principles and Background
      • 2.1 Introduction to the Case Study
      • 2.2 Models, Views, and Diagrams
        • 2.2.1 What is a Model?
        • 2.2.2 Why do we Need Models?
        • 2.2.3 Purpose and Target Group of a Model
          • Practical Tips
        • 2.2.4 Process of Analysis
          • Practical Tips
        • 2.2.5 Diagrams as Views
      • 2.3 Information Systems and IT Systems
      • 2.4 The Models of our Case Study
      • 2.5 History of UML: Methods and Notations
      • 2.6 Requirement Specification
        • 2.6.1 Guidance for Decision Making
        • 2.6.2 Verification
      • 2.7 UML 2.0
        • 2.7.1 Overview of UML 2.0
        • 2.7.2 Effects on the Business System Model
        • 2.7.3 Effects on the IT System Model
        • 2.7.4 Effects on the Systems Integration Model
        • 2.7.5 Conclusion
    • 3. Modeling Business Systems
      • 3.1 Business Processes and Business Systems
        • 3.1.1 What is a Business Process?
        • 3.1.2 Definition of the Workflow Management Coalition
        • 3.1.3 Business Systems
        • 3.1.4 Using UML to Model Business Processes and Business Systems
        • 3.1.5 Practical Tips for Modeling Business Processes
      • 3.2 One ModelTwo Views
      • 3.3 External View
        • 3.3.1 What Benefit does a Business System Provide?
          • Business Use Cases
          • Actors
        • 3.3.2 The Elements of a View
        • 3.3.3 Use Case Diagrams
          • Reading Use Case Diagrams
        • 3.3.4 Constructing Use Case Diagrams
          • Collecting Information SourcesHow am I Supposed to Know That?
          • Identifying Potential ActorsWhich Partners and Customers Use the Goods and Services of the Business System?
          • Identifying Potential Business Use CasesWhich Goods and Services can Actors Draw Upon?
          • Practical Tips
          • Connecting Business Use CasesWho Can Make Use of What Goods and Services of the Business System?
          • Describing ActorsWho or What do the Actors Represent?
          • Searching for More Business Use CasesWhat else Needs to be Done?
          • Editing Business Use CasesWhat actually has to be Included in a Business Use Case?
          • Documenting Business Use CasesWhat Happens in a Business Use Case?
          • Modeling Relationships between Business Use CasesWhat Activities are Conducted Repeatedly?
          • Verifying the ViewIs Everything Correct?
          • Practical Tips
        • 3.3.5 Activity Diagrams
          • Reading Activity Diagrams
        • 3.3.6 Constructing Activity Diagrams
          • Collect Information SourcesHow am I Supposed to Know That?
          • Find Activities and ActionsWhat has to be Done When Actors Draw upon Offered Goods and Services?
          • Connect ActionsIn Which Order are Actions Processed?
          • Refine ActivitiesDo any Other Activity Diagrams have to be Added?
          • Adopt Actors from Business Use CasesWho is Responsible for Each Action?
          • Verify the ViewIs Everything Correct?
        • 3.3.7 Sequence Diagrams
          • Reading Sequence Diagrams
        • 3.3.8 Constructing Sequence Diagrams
          • Designate Actors and Business SystemWho is Taking Part?
          • Designate InitiatorsWho Starts Interactions?
          • Describe the Message Exchange between Actors and the Business SystemWhich Messages are being Exchanged?
          • Identify the Course of InteractionsWhat is the Order?
          • Insert Additional InformationWhat Else is Important?
          • Verify the ViewIs Everything Correct?
        • 3.3.9 High-Level Sequence Diagrams
        • 3.3.10 Sequence Diagrams for Scenarios of Business Use Cases
      • The Internal View
        • 3.4.1 The Elements of the View
        • 3.4.2 Package Diagram
          • Reading Package Diagrams
        • 3.4.3 Constructing Package Diagrams
          • Develop an Initial Package Diagram of the Business SystemWhich Workers and Business Objects Make up the Business System?
          • Find Additional Organization UnitsWho Else is There?
          • Assign Workers and Business Objects to the Organization UnitsWho Belongs Where?
          • Find Additional Organization Units, Workers, or Business ObjectsWhat Else is There?
          • Verify the ViewIs Everything Correct?
        • 3.4.4 Class Diagram
          • Reading Class Diagrams
        • 3.4.5 Constructing Class Diagrams
          • Find ClassesWhich Classes Exist in the Class Diagram?
          • Create Associations Between ClassesWhich Classes Deal with Each Other?
          • Substantiate AssociationsWhat do these Relationships Mean?
          • Insert GeneralizationsCan Business Objects be Grouped?
          • Verify the ViewIs Everything Correct?
        • 3.4.6 Activity Diagram
          • Reading Activity Diagrams
        • 3.4.7 Constructing Activity Diagrams
          • Collect Information SourcesHow am I Supposed to Know That?
          • Find Activities and ActionsWhich Activities Have to be Performed so that the Goods and Services Utilized by Actors can be Provided and Delivered?
          • Adopt Actors from Business Use CasesWho is Responsible for Each Action?
          • Connect ActionsIn Which Order are Actions Processed?
          • Refine ActivitiesDo any Other Activity Diagrams Have to be Added?
          • Verify the ViewIs Everything Correct?
    • 4. Modeling IT Systems
      • 4.1 External View
        • 4.1.1 The User View or "I dont care how it works, as long as it works."
        • 4.1.2 The Elements of a View
        • 4.1.3 Use Case Diagram
          • Reading Use Case Diagrams
        • 4.1.4 Query Events and Mutation Events
        • 4.1.5 Use Case Sequence Diagram
          • Reading Use Case Sequence Diagrams
        • 4.1.6 Constructing the External View
          • Collect Information SourcesHow Am I Supposed to Know That?
          • Identify Potential ActorsWho Works with the IT System?
          • Identify Potential Use CasesWhat Can be Done With the IT System?
          • Connect Actors and Use CasesWho Can Do What with the IT System?
          • Describe ActorsWho or What do the Actors Represent?
          • Search for More Use CasesWhat Functionalities does the IT System have to Provide?
          • Edit Use CasesWhat Actually Has to be Included in a Use Case?
          • Document Use CasesWhat Happens in a Use Case?
          • Model Relationships between Use CasesWhat can be Reused?
          • Verify the ViewIs Everything Correct?
      • 4.2 Structural View
        • 4.2.1 Objects and Classes
        • 4.2.2 Generalization, Specialization, and Inheritance
        • 4.2.3 Static and Dynamic Business Rules
        • 4.2.4 Elements of the View
        • 4.2.5 Class Diagram
          • Reading Class Diagrams
        • 4.2.6 Constructing Class Diagrams
          • Identify and Model ClassesWhich Classes do We Need?
          • Identify and Model AssociationsHow Are the Classes Connected?
          • Define AttributesWhat do We Want to Know about the Objects?
          • List Required Queries and InputsWhat does the IT System Need to Deliver and Accept?
          • Formulate Queries and InputsHow Exactly Should the Display Look?
          • Conduct Information AnalysisWhich Classes, Associations, and Attributes Do We Need?
          • Consolidate Class DiagramsHow Does Everything Fit Together?
          • Verify the Class DiagramsIs Everything Correct?
      • 4.3 The Behavioral View
        • 4.3.1 The Life of an Object
        • 4.3.2. The Elements of the View
        • 4.3.3 Statechart Diagram
          • Reading Statechart Diagrams
        • 4.3.4 Constructing Statechart Diagrams
          • Identify Mutation Events Relevant for the ObjectWhat Affects the Object?
          • Group Relevant Events ChronologicallyHow Does a Normal Life Look?
          • Model States and TransitionsWhich States are There?
          • Add Actions to the Statechart DiagramWhat do Objects Do?
          • Verify Statechart DiagramIs Everything Correct?
      • 4.4 Interaction View
        • 4.4.1 Seeing What Happens Inside the IT System
        • 4.4.2 Elements of the View
        • 4.4.3 Communication Diagram
          • Reading Communication Diagrams
        • 4.4.4 Sequence Diagram
          • Reading Sequence Diagrams
        • 4.4.5 Constructing Communication Diagrams
          • Draft Query ResultWhat do We Want?
          • Identify Involved ClassesWhich Classes Do We Need?
          • Define Initial ObjectWhere Do We Start?
          • Design Event PathWhere Do We Go?
          • Amend Event PathExactly Which Objects do We Need?
          • Identify Necessary AttributesWhat Exactly Do We Want to Know?
          • Verify the Communication DiagramIs Everything Correct?
        • 4.4.6 Constructing Sequence Diagrams
          • Identify Involved ClassesWhat is Affected by Mutation Events?
          • Determine Initial ObjectWhere does the Mutation Event go First?
          • Propagate EventsHow is the Mutation Event Forwarded?
          • Specify Event ParameterWhat do Objects have to Know?
          • Verify the Sequence DiagramIs Everything Correct?
    • 5. Modeling for System Integration
      • 5.1 Terminology of System Integration
        • Interfaces
        • Messages
        • Enterprise Application Integration
        • Electronic Data Interchange
        • UN/EDIFACT
        • XML
      • 5.2 Messages in UML
      • 5.3 One ModelTwo Views
      • 5.4 Process View
        • 5.4.1 The Business System Model as Foundation
        • 5.4.2 Elements of the View
        • 5.4.3 Activity Diagrams
          • Reading Activity Diagrams
        • 5.4.4 Sequence Diagram
          • Reading Sequence Diagrams
        • 5.4.5 Constructing Diagrams in the Process View
          • Determine InterfacesBetween Which IT Systems Should Communication Take Place?
          • Identify Involved SystemsWhich IT Systems Exchange Information?
          • Identify Activities and Control FlowWhat has to be Done and Who is Responsible for It?
          • Define MessagesWhich Messages have to be Exchanged?
          • Define RulesWhat Influences Actions?
          • Verify the ViewIs Everything Correct?
      • 5.5 The Static View
        • 5.5.1 Elements of the View
        • 5.5.2 Class Diagram
          • Reading Class Diagrams
        • 5.5.3 Constructing Class Diagrams
          • Collect Information Relevant for the Business ObjectsWhat Do We Want to Read?
          • Construct Class DiagramWhat is the Structure of the Business Object?
          • Adopt Classes and Attributes from the Class Diagram of the IT SystemWhat is Present in the Class Diagram?
          • Derive Remaining Data ElementsFrom Where Do I Get the Rest?
          • Define Classes and Relationships of the Business ObjectWhich Class Relationships do We Need?
          • Verify the ViewIs Everything Correct?
        • 5.5.4 Transforming Data from the IT System to the Message "passenger list"
          • Transformation of Flight Data
          • Transformation of Passenger Data
        • 5.5.5 Transformation of UML Messages into Various Standard Formats
    • Index
  • Tytuł: UML 2.0 in Action: A project-based tutorial. A detailed and practical book and eBook walk-through showing how to apply UML to real world development projects
  • Autor: Philippe Baumann, Patrick Grassle, Henriette Baumann, Galileo Press GmbH
  • Tytuł oryginału: UML 2.0 in Action: A project-based tutorial. A detailed and practical book and eBook walk-through showing how to apply UML to real world development projects
  • ISBN: 9781847190420, 9781847190420
  • Data wydania: 2005-09-06
  • Format: Ebook
  • Identyfikator pozycji: e_3crj
  • Wydawca: Packt Publishing