UML 2.0 in a nutshell
System developers have used modeling languages for decades to specify, visualize, construct, and document systems. The Unified Modeling Language (UML) is one of those languages. UML makes it possible for team members to collaborate by providing a common language that applies to a multitude of diffe...
| Autor principal: | |
|---|---|
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, California :
O'Reilly Media
2005.
|
| Edición: | First edition |
| Colección: | In a nutshell (O'Reilly & Associates)
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627128506719 |
Tabla de Contenidos:
- UML 2.0 in a Nutshell; Preface; How to Use This Book; Typographic Conventions; Safari Enabled; Comments and Questions; Acknowledgments; From Neil; 1. Fundamentals of UML; 1.2. Background; 1.3. UML Basics; 1.3.2. Business Process Modeling; 1.4. UML Specifications; 1.5. Putting UML to Work; 1.6. Modeling; 1.6.2. Views; 1.6.3. Notes; 1.6.4. Classifiers and Adornments; 1.7. UML Rules of Thumb; 2. Class Diagrams; 2.2. Attributes; 2.2.2. Attributes by Relationship; 2.2.3. Derived Attributes; 2.2.4. Attribute Multiplicity; 2.2.4.2. Uniqueness; 2.2.4.3. Collection types; 2.2.5. Attribute Properties
- 2.2.6. Constraints2.2.7. Static Attributes; 2.3. Operations; 2.3.1.2. Postconditions; 2.3.1.3. Body conditions; 2.3.1.4. Query operations; 2.3.1.5. Exceptions; 2.3.2. Static Operations; 2.4. Methods; 2.5. Abstract Classes; 2.6. Relationships; 2.6.2. Association; 2.6.2.2. Naming an association; 2.6.2.3. Multiplicity; 2.6.3. Aggregation; 2.6.4. Composition; 2.6.5. Generalization; 2.6.6. Association Classes; 2.6.7. Association Qualifiers; 2.7. Interfaces; 2.8. Templates; 2.9. Variations on Class Diagrams; 2.9.2. Database Schemas; 3. Package Diagrams; 3.2. Visibility
- 3.3. Importing and Accessing Packages3.4. Merging Packages; 3.5. Variations on Package Diagrams; 3.5.2. Use Case Packages; 3.5.3. Directed Dependency Graphs; 4. Composite Structures; 4.1.2. Ports; 4.1.2.2. Realizing port implementations; 4.1.2.3. Multiple connectors; 4.1.2.4. Port multiplicity; 4.1.2.5. Port typing; 4.1.3. Structured Classes and Properties; 4.2. Collaborations; 4.3. Collaboration Occurrences; 5. Component Diagrams; 5.2. Component Views; 5.2.1.2. Interface dependencies; 5.2.1.3. Component compartments; 5.2.2. White-Box View; 5.2.2.2. Classifier dependencies
- 5.2.2.3. Ports and connectors5.2.3. Component Stereotypes; 6. Deployment Diagrams; 6.1.2. Manifestations; 6.2. Nodes; 6.2.1.2. Explicit services; 6.2.2. Devices; 6.2.3. Communication Paths; 6.3. Deployment; 6.3.2. Deployment Specifications; 6.4. Variations on Deployment Diagrams; 7. Use Case Diagrams; 7.2. Actors; 7.2.2. System Boundaries; 7.2.3. Using Actors to Identify Functionality; 7.3. Advanced Use Case Modeling; 7.3.2. Use Case Inclusion; 7.3.3. Use Case Extension; 7.4. Use Case Scope; 8. Statechart Diagrams; 8.2. States; 8.2.2. Submachine States; 8.2.3. Transitions
- 8.2.3.2. Signal symbols8.2.3.3. Transitions and composite states; 8.2.4. Activities; 8.3. State Machine Extension; 8.4. Protocol State Machines; 8.5. Pseudostates; 8.6. Event Processing; 8.6.2. Deferred Events; 8.7. Variations on Statechart Diagrams; 9. Activity Diagrams; 9.1.1.2. Object flows; 9.1.1.3. Connectors; 9.2. Tokens; 9.3. Activity Nodes; 9.3.2. Object Nodes; 9.3.3. Pins; 9.3.4. Control Nodes; 9.3.4.2. Decision and merge nodes; 9.3.4.3. Fork and join nodes; 9.3.4.4. Final nodes; 9.4. Advanced Activity Modeling; 9.4.2. Exception Handling; 9.4.3. Expansion Regions; 9.4.4. Looping
- 9.4.5. Streaming
