<--- Back to Details
First PageDocument Content
Software engineering / Package diagram / Stereotype / Enterprise Architect / Class diagram / Classifier / Diagram / Object diagram / Package / Unified Modeling Language / UML diagrams / Data modeling
Date: 2013-07-22 11:30:56
Software engineering
Package diagram
Stereotype
Enterprise Architect
Class diagram
Classifier
Diagram
Object diagram
Package
Unified Modeling Language
UML diagrams
Data modeling

Add to Reading List

Source URL: sparxsystems.com.au

Download Document from Source Website

File Size: 192,06 KB

Share Document on Facebook

Similar Documents

Windows Registry / Package diagram / Package

Enterprise Architect User Guide Series Reuseable Asset Service (RAS)

DocID: 1pj22 - View Document

United States Department of Homeland Security / United States Department of Justice / Unified Modeling Language / ISO/IEC 11179 / Metadata registry / National Information Exchange Model / Diagram / UML tool / Object Process Methodology / Package diagram / Class diagram / Object diagram

UML Approach to Modeling NIEM Exchanges - Analyzing Requirements

DocID: 1pfCU - View Document

Unified Modeling Language / UML tool / Class diagram / Eclipse / Diagram / Package diagram / Element / Profile / Object Process Methodology / Rodin tool / Executable UML

Project ISTRODIN “Rigorous Open Development Environment for Complex Systems” RODIN Deliverable D31

DocID: 1oOc0 - View Document

Unified Modeling Language / Diagrams / ISO standards / Class diagram / Object Process Methodology / UML tool / Entityrelationship model / YEd / Package diagram

Preprint. The final version of this paper will appear in the Proc. of ESEMHow Humans merge UML-Models Rainer Lutz, David W¨urfel and Stephan Diehl Department of Computer Science University of Trier

DocID: 1oNwM - View Document

Software engineering / Class diagram / Object Process Methodology / Engineering / Computing / Package diagram / Data model / Diagrams / Mathematical diagram

Enabling multi-stakeholder cooperative modelling in automotive software development and implications for model driven software development Frank Grimm

DocID: 1nOXV - View Document