物件導向軟體之架構(Object-Oriented Software Construction)探討

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

The potential benefits of using models are significantly greater in software than in other engineering disciplines because of the potential for a seamless link between models and the systems they represent. Unfortunately, models have rarely produced anticipated benefits. The key lies in resolving pragmatic issues related to the artifacts and culture of the previous generation of software technologies.

/pdf/the-pragmatics-of-model-driven-development-4cef6shd68.pdf

The pragmatics of model-driven development

Hawaii International Conference on System Sciences

[서평]「Component Software」 - Beyond Object-Oriented Programming -

The "architecture" of a software system refers to its highest-level modular decomposition and the interrelationship patterns between its modules. An architecture serves as a blueprint for implementation and also as the chief determinant of a system's ability evolve. Consequently, there is an increased interest in methods for specifying and validating software architectures. One such method is based on the ROOM mode ling language which combines the object paradigm with mode ling abstractions devised specifically for distributed real-time software. To overcome the treacherous "architectural decay" phenomenon, whereby, over time, software diverges increasingly from its specification, ROOM formally constrains the implementation to its architectural specification. This is achieved primarily through full automated code generation, a technique that is panicularly challenging in real-time applications where stringent performance and memory requirements are the norm.

Real-time object-oriented modeling

Real-time software systems encountered in telecommunications, aerospace, and defense often tend to be very large and extremely complex. It is crucial in such systems that the software has a well-defined architecture. This not only facilitates construction of the initial system, it also simplifies system evolution. We describe a set of modeling constructs that facilitate the specification of complex software architectures for real-time systems. These constructs are derived from field-proven concepts originally defined in the ROOM modeling language. Furthermore, we show how they can be represented using the industry-standard Unified Modeling Language (UML) by using the powerful extensibility mechanisms of UML.

Using UML for Modeling complex real-time systems

/pdf/using-uml-for-modeling-complex-real-time-systems-2ldaf5m2y9.pdf

Using UML for Modeling Complex Real-Time Systems

Part I: Basics - Knowledge Representation - Ontologies - Semantic Web - Model Driven Architecture - Modeling Spaces.- Part II: Model Driven Architecture and Ontologies - Software Engineering Approaches for Ontology Development - MDA-Based Ontology Infrastructure - Ontology Definition Metamodel - Ontology UML Profile - Mappings of MDA Based Languages and Ontologies.- Part III: Application - Using UML Tools for Ontology Modeling - MDA Based Ontology Platform: AIR - Ontology Examples.

Bran Selic

Papers

The pragmatics of model-driven development

Real-time object-oriented modeling

Using UML for Modeling complex real-time systems

Using UML for Modeling Complex Real-Time Systems

Model Driven Architecture and Ontology Development