Tutorials
All Tutorials
UML Tutorials
UML 2.1 Tutorial
UML Tutorial - Part 1 Intro
UML Tutorial - Part 2 Intro
The Business Process Model
The Component Model
The Dynamic Model
The Logical Model
The Physical Model
The Use Case Model
UML Database Modeling
Enterprise Architect Tutorials
Creating Strategic Models
Diagram Filters
BPEL: Step by Step Guide
Resource Management
Testing Management
Traceability
RTF Documentation
Use Case Metrics
Structured Use Case Scenarios
Video Demonstrations
All Videos
Getting Started
Requirements Management
Modeling & Productivity Tools
Code Engineering and the Debug Workbench
Version Control
Integration (Eclipse, Visual Studio, TFS)
UML Tutorial - Structure
UML Tutorial - Behavior
The Business Process Model
Deployment of EA
MDA Overview
Rich-Text (RTF) Reporting
Version Control Integration
Requirements Management
White Papers & E-Books
Roles
Business Analyst
Database Administrator
Deployment & Rollout
Developer
Project Manager
Software Architects
Software Engineer
Technology Developer
Testers
Baseline Diagram Comparison
Conduct a visual diagram comparison between your current diagram and a previous baseline .
Personal Information Window
See how the Personal Information Window in Enterprise Architect can help you organize your daily tasks and workflow.
Working Sets
As you perform work on your model, you open various windows, diagrams and views. Working Sets allow you to return to these same views in a later work session.
Business Rules
A car rental system is used to illustrate how to generate executable business rules using Enterprise Architect.
Menu Customization
Quickly and easily suppress individual menu items or entire categories of commands to create custom menu layouts.
Floating and Dockable Windows
Save the position and layout of Floating and Dockable Windows using a Working Set in the Personal Information Window.
Build and Debug a Java Application
Set up Enterprise Architect to build and debug a Java Application, using a VEA sample project.
Sequence Diagrams
Learn how to create a simple Sequence diagram. The video also illustrates how to bring your Sequence diagram to life using model simulation.
HTML Report Generation
This brief introduction illustrates how to automatically generate a HTML Report using Enterprise Architect.
Basic Use Case Demonstration
A guide to constructing a Use Case model in under 30 seconds, including use cases, notes and issues.
Traceability within Enterprise Architect
This video examines Traceability and discusses how to use Enterprise Architect to conduct an Impact Analysis.
Requirements Reporting
A brief overview of requirements reporting in Enterprise Architect. Topics include document generation in web and RTF formats, report customization and virtual documents, including Model and Master documents.
Requirements Traceability
An examination of requirements traceability in Enterprise Architect. Topics include traceability views, tracing to external artifacts, conducting an impact analysis, viewing the Relationship Matrix and using Enterprise Architect's Auditing capabilities.
Requirements Modeling
A brief overview of requirements modeling in Enterprise Architect. Topics include requirements capture and definition, custom properties, tabular editing, auto-naming and screen prototypes.
Installing EA
An introductory walk through and discussion of Enterprise Architect in the Software Development Lifecycle.
Enterprise Architect 7.5 Overview
An overview of Enterprise Architect features released with version 7.5.
Introduction to Enterprise Architect
An introductory walk through and discussion of Enterprise Architect in the Software Development Lifecycle.
Brief Overview
The 10 minute guide to Enterprise Architect, from Requirements Management and Business Process Modeling to MDA and Code Engineering.
The XSD Generation facility converts a UML class model to a W3C XML Schema (XSD). This allows Data Modelers to start working at a conceptual level in UML, leaving the tedious aspects of XSD creation to EA. The schema generation can then be customized if necessar
To use the schema generation facility you will require the following:
XSDDataTypes Package: This package contains classes representing XSD primitive data types. This package is available as an XMI file. To import the file as a UML Package, use EA's XMI import facility which is available from the menu item: Project | Import/Export | Import Package from XMI.
UML Profile for XML: This resource file contains the stereotyped classes which allow the schema generation to be customized. The UML Profile for XML can be imported into a model using the Resource View (see Importing Profiles for details on importing UML profiles into EA).
Steps to Generate XSD:
Select the package to be converted to XSD by right-clicking on the package in the Project Browser.
Select Project | Generate XML Schema from the main menu.
Set the desired output file using the Filename field.
Set the desired xml encoding using the Encoding field.
Click on the Generate button to generate the schema.
The progress of the schema generator will be shown in the Progress edit box.
Using @DataSourceDefinition to configure a DataSource
This annotation requires that a data source implementation class (generally from a JDBC driver JAR) be present on the class path (either by including it in your application, or deploying it as a top-level JAR and referring to it via MANIFEST.MF's Class-Path attribute) and be named explicitly.
this annotation bypasses the management layer and as such it is recommended only for development and testing purposes
Defining a Managed DataSource
Installing a JDBC driver as a deployment
Installing the JDBC Driver
deployment or as a core module
managed by the application server (and thus take advantage of the management and connection pooling facilities it provides), you must perform two tasks. First, you must make the JDBC driver available to the application server; then you can configure the data source itself. Once you have performed these tasks you can use the data source via standard JNDI injection.
recommended way to install a JDBC driver into the application server is to simply deploy it as a regular JAR deployment. The reason for this is that when you run your application server in domain mode, deployments are automatically propagated to all servers to which the deployment applies; thus distribution of the driver JAR is one less thing for administrators to worry about.
Note on MySQL driver and JDBC Type 4 compliance: while the MySQL driver (at least up to 5.1.18) is designed to be a Type 4 driver, its jdbcCompliant() method always return false. The reason is that the driver does not pass SQL 92 full compliance tests, says MySQL. Thus, you will need to install the MySQL JDBC driver as a module (see below).
define your module with a module.xml file, and the actual jar file that contains your database driver
content of the module.xml file
Under the root directory of the application server, is a directory called modules
module name, which in this example is com.mysql
where the implementation is, which is the resource-root tag with the path element
define any dependencies you might have. In this case, as the case with all JDBC data sources, we would be dependent on the Java JDBC API's, which in this case in defined in another module called javax.api, which you can find under modules/javax/api/main as you would expect.
MDG Technologies allow users to extend Enterprise Architect's modeling capabilities to specific domains and notations. MDG Technologies seamlessly plug into Enterprise Architect to provide additional toolboxes, UML profiles, patterns, templates and other modeling resources.
Free MDG Technology downloads for Enterprise Architect:
EJB
MDG Technology for Enterprise Java Beans allows the user to model EJB entities and EJB sessions, complete with UML profiles for modeling EJB, EJB patterns and Code Management.
(requires Enterprise Architect 4.1 or later)
ICONIX AGILE DDT
ICONIX Agile Developer - Design-Driven Testing (DDT) streamlines the ICONIX modeling process, providing:
Convenient modeling of robustness diagrams
Automatic generation of sequence diagram structures from robustness diagrams
Transformation of robustness control elements to test diagrams
Transformation of sequence diagram elements to test diagrams
Transformation of requirement diagrams to test diagrams
Transformation between test cases and test classes. (JUnit & NUnit)
Built-in model validation rules for ICONIX robustness diagrams
(requires Enterprise Architect 7.5 or later)
Testing
MDG Technology for Testing helps users to rapidly model a wide range of testing procedures including component testing, SUT, Test Cases and more.
(requires Enterprise Architect 4.1 or later)
Instructions for loading an MDG Technology
EXE file:
Download and run the .exe file to install the MDG technology.
Open Enterprise Architect.
Select from the Main Menu Add-Ins | XYZ Technology | Load.
Built-in MDG Technologies:
Most of the MDG Technologies provided by Sparx Systems are built into Enterprise Architect directly. Depending on your edition of Enterprise Architect, some or all of the following MDG Technologies will be available:
In any access control model, the entities that can perform actions in the system are called subjects, and the entities representing resources to which access may need to be controlled are called objects
object-capability model, any software entity can potentially act as both a subject and object
Access control models used by current systems tend to fall into one of two classes:
those based on capabilities
those based on access control lists (ACLs)
Both capability-based and ACL-based models have mechanisms to allow access rights to be granted to all members of a group of subjects (often the group is itself modeled as a subject)
identification and authentication determine who can log on to a system, and the association of users with the software subjects that they are able to control as a result of logging in;
authorization determines what a subject can do;
accountability identifies what a subject (or all subjects associated with a user) did.
Authorization determines what a subject can do on the system
Authorization
Access control models
categorized as either discretionary or non-discretionary
three most widely recognized models are
Discretionary Access Control (DAC)
Mandatory Access Control (MAC)
Role Based Access Control (RBAC)
Attribute-based access control
Discretionary access control
Discretionary access control (DAC) is a policy determined by the owner of an object. The owner decides who is allowed to access the object and what privileges they have.
Every object in the system has an owner
access policy for an object is determined by its owner
DAC systems, each object's initial owner is the subject that caused it to be created
Mandatory access control
Mandatory access control refers to allowing access to a resource
if and only if rules exist
that allow a given user to access the resource
Management is often simplified (over what can be required) if the information can be protected using
hierarchical access control
or by implementing sensitivity labels.
Sensitivity labels
A subject's sensitivity label specifies its
level of trust
level of trust required for access
subject must have a sensitivity level equal to or higher than the requested object
generally speaking, there can be a few independent but overlapping mechanism that will control who is allowed to do what with content:
1. any subject's access to the content itself can be controlled via authorization rules (ie. required vs granted permissions) enforced via system-wide resource-based access control
2. content licensors (~content owners) can restrict the usage of their content by:
* whom - ie. content licensee (legally/commercially represented by an organization)
* how - eg. reuse as unmodified, create derivatives, composite, redistribute, etc
* where - ie. distribution channels their content can be used (eg. only on hotel's vbrochure site, but not in any ids/gds channels)
* when - temporal restrictions may limit scope of content license grant by: start, end, duration, season, etc
3. content licensees can further filter or funnel content available to them (resulting from a combination of license granted to them and access control) based on their own criteria (eg. generate a templated hotel presentation only if: at least 1 textual description, 5 photos and 1 video for a hotel is available with a license to combine them (composite content)
if ecm/vfml is to manage content licensing as a third party between organizations (content licensors & licensees) shouldn't ecm *know* if the user('s organization) has rights to use the content in question?
is this question posed to the user (with required explicit acknowledgement) purely to absolve vfml from liability issues that may result from licensing disagreements?
this being the user's (organization's) 'version'or 'view'of the hotel, since this user normally wouldn't/shouldn't be granted permissions to replace content for a hotel on a different organization's 'view'or 'version' of the same hotel
this implies that *at least* one version of such (temporarily) replaceable content needs to be managed/maintaned to allow reverting
what if, deliberately, ignorantly or maliciously, a user replaces the same piece of--textual or any type, really--content for this hotel n times? will all n versions be required to be managed as an undo history?
the user's ''original content'' might have been version 1, but equally might have been 1 mean:
- previous version of the content, regardless of which user
- initial version of that content attached to the hotel regardless of which user created/updated it and ignoring which organization owns it?, or,
-
requires that in a particular abstraction layer of a computing environment, every module (such as a process, a user or a program depending on the subject) must be able to
access only the information and resources that are necessary for its legitimate purpose