UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

\While in geometry attempts to square the circle never succeeded, the UML has achieved it: states canbeimplementedasclasses. "{\Wehavemade much progressfrom thetime cloudswere used. " The Uni ed Modeling Language is described as a language for \specifying, - sualizing, constructing, and documenting the artifacts of software systems" and for business modeling (OMG UML V1. x documents). The UML reffects some of the best experiences in object-oriented modeling, thus it has the potential to become a widely-used standard object-oriented modeling language. As a generally-applicable standard the UML has to be both—exible (ext- sible, adaptable, modia ble) and precise. Flexibility is needed if the UML is to be used in a variety of application domains. Tailoring of UML syntax and adaptation of UML semantics to system domains is highly desirable. Incor- rating domain-specic concepts into the language will yield modeling languages that more e ectively support system development in these domains. Tailoring may involve determining a subset of the UML that is applicable to the domain, extending or modifying existing language elements, or den ing new language elements. One can envisage UML variants that are tailored to specic domains, for example, UML for real-time systems, multimedia systems, and for intern- based systems. Furthermore, one can also de ne UML variants that determine levels of sophistication in the use of the UML.

"1111332389"
UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

\While in geometry attempts to square the circle never succeeded, the UML has achieved it: states canbeimplementedasclasses. "{\Wehavemade much progressfrom thetime cloudswere used. " The Uni ed Modeling Language is described as a language for \specifying, - sualizing, constructing, and documenting the artifacts of software systems" and for business modeling (OMG UML V1. x documents). The UML reffects some of the best experiences in object-oriented modeling, thus it has the potential to become a widely-used standard object-oriented modeling language. As a generally-applicable standard the UML has to be both—exible (ext- sible, adaptable, modia ble) and precise. Flexibility is needed if the UML is to be used in a variety of application domains. Tailoring of UML syntax and adaptation of UML semantics to system domains is highly desirable. Incor- rating domain-specic concepts into the language will yield modeling languages that more e ectively support system development in these domains. Tailoring may involve determining a subset of the UML that is applicable to the domain, extending or modifying existing language elements, or den ing new language elements. One can envisage UML variants that are tailored to specic domains, for example, UML for real-time systems, multimedia systems, and for intern- based systems. Furthermore, one can also de ne UML variants that determine levels of sophistication in the use of the UML.

109.99 In Stock
UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

UML'99 - The Unified Modeling Language: Beyond the Standard: Second International Conference, Fort Collins, CO, USA, October 28-30, 1999, Proceedings

Paperback(1999)

$109.99 
  • SHIP THIS ITEM
    Not Eligible for Free Shipping
  • PICK UP IN STORE
    Check Availability at Nearby Stores

Related collections and offers


Overview

\While in geometry attempts to square the circle never succeeded, the UML has achieved it: states canbeimplementedasclasses. "{\Wehavemade much progressfrom thetime cloudswere used. " The Uni ed Modeling Language is described as a language for \specifying, - sualizing, constructing, and documenting the artifacts of software systems" and for business modeling (OMG UML V1. x documents). The UML reffects some of the best experiences in object-oriented modeling, thus it has the potential to become a widely-used standard object-oriented modeling language. As a generally-applicable standard the UML has to be both—exible (ext- sible, adaptable, modia ble) and precise. Flexibility is needed if the UML is to be used in a variety of application domains. Tailoring of UML syntax and adaptation of UML semantics to system domains is highly desirable. Incor- rating domain-specic concepts into the language will yield modeling languages that more e ectively support system development in these domains. Tailoring may involve determining a subset of the UML that is applicable to the domain, extending or modifying existing language elements, or den ing new language elements. One can envisage UML variants that are tailored to specic domains, for example, UML for real-time systems, multimedia systems, and for intern- based systems. Furthermore, one can also de ne UML variants that determine levels of sophistication in the use of the UML.


Product Details

ISBN-13: 9783540667124
Publisher: Springer Berlin Heidelberg
Publication date: 11/12/1999
Series: Lecture Notes in Computer Science , #1723
Edition description: 1999
Pages: 726
Product dimensions: 6.10(w) x 9.17(h) x 0.06(d)

Table of Contents

Invited Talk 1 (Abstract).- Architecting Web-Based Systems with the Unified Modeling Language.- Software Architecture.- Extending Architectural Representation in UML with View Integration.- Enabling the Refinement of a Software Architecture into a Design.- Using the UML for Architectural Description.- UML and Other Notations.- Viewing the OML as a Variant of the UML.- A Comparison of the Business Object Notation and the Unified Modeling Language.- Formalizing the UML Class Diagram Using Object-Z.- Formalizing Interactions.- A Formal Approach to Collaborations in the Unified Modeling Language.- A Formal Semantics for UML Interactions.- Panel 1.- UML 2.0 Architectural Crossroads: Sculpting or Mudpacking?.- Meta-Modeling.- Core Meta-Modelling Semantics of UML: The pUML Approach.- A Metamodel for OCL.- Tools.- Tool-Supported Compression of UML Class Diagrams.- A Pragmatic Approach for Building a User-Friendly and Flexible UML Model Repository.- Components.- Modeling Dynamic Software Components in UML.- Extending UML for Modeling Reflective Software Components.- UML Extension Mechanisms.- Nine Suggestions for Improving UML Extensibility.- A Classification of Stereotypes for Object-Oriented Modeling Languages.- First-Class Extensibility for UML — Packaging of Profiles, Stereotypes, Patterns.- Process Modeling.- UML-Based Fusion Analysis.- Using UML for Modelling the Static Part of a Software Process.- Framework for Describing UML Compatible Development Processes.- Invited Talk 2.- On the Behavior of Complex Object-Oriented Systems.- Real-Time Systems.- UML-RT as a Candidate for Modeling Embedded Real-Time Systems in the Telecommunication Domain.- Modeling Hard Real Time Systems with UML The OOHARTS Approach.- UML Based Performance Modeling Framework for Object-OrientedDistributed Systems.- Constraint Languages.- Defining the Context of OCL Expressions.- Mixing Visual and Textual Constraint Languages.- Correct Realizations of Interface Constraints with OCL.- Analyzing UML Models 1.- Generating Tests from UML Specifications.- Formalising UML State Machines for Model Checking.- Panel 2.- SDL as UML: Why and What Panel.- Coding 1.- UML Behavior: Inheritance and Implementation in Current Object-Oriented Languages.- UML Collaboration Diagrams and Their Transformation to Java.- Analyzing UML Models 2.- Towards Three-Dimensional Representation and Animation of UML Diagrams.- Typechecking UML Static Models.- Precise Behavioral Modeling.- Analysing UML Use Cases as Contracts.- Closing the Gap between Object-Oriented Modeling of Structure and Behavior.- Static Modeling.- Black and White Diamonds.- Interconnecting Objects via Contracts.- How Can a Subsystem Be Both a Package and a Classifier?.- Applying the UML.- Using UML/OCL Constraints for Relational Database Design.- Towards a UML Extension for Hypermedia Design.- Why Unified Is not Universal.- Sequence Diagrams.- Timed Sequence Diagrams and Tool-Based Analysis — A Case Study.- Timing Analysis of UML Sequence Diagrams.- Coding 2.- The Normal Object Form: Bridging the Gap from Models to Code.- Modeling Exceptional Behavior.- Panel 3.- Advanced Methods and Tools for a Precise UML.
From the B&N Reads Blog

Customer Reviews