TOOL: Mapping between Enterprise Architect 12.1 menus and Enterprise Architect 13 ribbons

EA 12 to EA 13 changed locations of actions (menu)... To help you through the upgrade there is this very good resource:
Mapping between Enterprise Architect 12.1 menus and Enterprise Architect 13 ribbons

TOOL: EA Image Library (Enterprise Architect, UML tool)

The Short Story

Useful at all times, this free image library will speed up the production of professional diagrams (that can be incorporated into presentations and/or technical documents), in the case you are using Sparx Systems Enterprise Architect (EA) to model your
information system:

Step 1: Download the free image libray

• Download Image Library | Enterprise Architect

Step 2: Install the image library in EA
http://www.sparxsystems.com/enterprise_architect_user_guide/12.0/modeling_basics/importimagelibary.html

Step 3: use the images

To use the images (e.g. change an UML node to a server image):

· Press Ctrl+Shift+W, or
· Right-click the selected element and select Appearance | Select Alternate Image

The Long Story

Why use this with EA? Example: A UML Deployment Diagram can be changed to use the images in the library, instead of the standard UML images (Nodes, Artifacts). This will benefit validation with the customer, hence, it will benefit you, as a business analyst (right?).

Managing the library:
http://www.sparxsystems.com/enterprise_architect_user_guide/12.0/modeling_basics/bitmapimagesindiagrams.html

Inception/Business Modeling/Requirements Engineering: i star framework?

A framework that could be especially suited for an inception phase of a system is i star:
https://en.m.wikipedia.org/wiki/I*

Quoting:
"i* (pronounced "i star") or i* framework is a modeling language suitable for an early phase of system modeling in order to understand the problem domain.

i* modeling language allows to model both as-is and to-be situations.

The name i* refers to the notion of distributed intentionality which underlines the framework. It is an approach originally developed for modelling and reasoning about organizational environments and their information systems composed of heterogeneous actors with different, often competing, goals that depend on each other to undertake their tasks and achieve these goals.

It covers both actor-oriented and Goal modeling.

i* models answer the question WHO and WHY, not what.

In contrast, the UML Use case approach covers only functional goals, with actors directly involved in operations (typically with software) [the what part, including functional requirements].

The KAOS approach covers goals of all types but is less concerned with the intentionality of actors.'"

Crow's foot notation (as in Entity–relationship model)?

About Crow's foot notation (FFR):

https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model#Crow.27s_foot_notation

Entity–relationship model - Wikipedia

PS. UML now has equivalent diagrams, used for conceptual modelling (look for UML Domain Models, that show [domain] entities as classes with just a name).

DIGEST: Modelling Tools tasks and Sparx Systems EA Documentation (UML Modelling Tool)

And the proper freshly linked links are indeed these ones:

• Modelling tasks (what do I need to be able to do to be a modeller?): http://silvaonsoftware.blogspot.pt/2016/07/tools-modelling-tools-hot-topics.html

• Initial EA tasks: http://silvaonsoftware.blogspot.pt/2016/11/modelling-ea-initial-management-tasks.html
• Using EA for analysis and modelling (PDF): http://silvaonsoftware.blogspot.pt/2017/01/tools-modeling-with-sparx-systems-ea.html
• Using EA for Data Modelling (building the physical data model for a RDBMS): http://www.sparxsystems.com.au/downloads/whitepapers/Database_Modeling_In_UML.pdf
• User Manuals, Getting Started and similar PDFs: http://silvaonsoftware.blogspot.pt/2016/07/resource-ea-additional-documentation.html

Is this enough?

Modelling: EA initial management tasks

Some common management tasks for EA (to be performed by the EA UML repository manager, which could be the Technical Manager of your project) include:

Activate Security - Turn on the option that allows you to define who alters what part of the model and who does not (lock, unlock):
http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/usersecurity.html

Managing Users - Create profiles, users belonging to profiles and defining permissions for those:
http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/managingusers.html

Import Users from Active Directory - Integrating existing (e.g. domain) users into EA 
http://www.sparxsystems.com/enterprise_architect_user_guide/8.0/projects_and_teams/import_user_ids_from_active_di.html

Initial EA Scripts - The DB schema that has to be loaded into the SQL DB initially: 
http://silvaonsoftware.blogspot.pt/2016/10/ea-initial-scripts.html


(@2017-06-23: Minor rephrases)

EA initial SQL scripts

The short story

The Enterprise Architect (EA) initial (SQL) scripts can be found here:
http://www.sparxsystems.com.au/resources/corporate/index.html#sql_scripts

And here are the instructions to apply it:
http://www.sparxsystems.com.au/enterprise_architect_user_guide/13.0/model_repository/upsizingtosqlserver.html

The long story

What are these good for? If you want to run EA with a centralized model (stored on a RDBMS like Oracle, MS SQL Server, MySQL and so on) you should start by install that DB and create an empty database there (CREATE DATABASE DDL).

You will be able to open an empty model from the EA tool (remote model) only after manually running this scripts on the SQL database (using the Administration tools of the DMBS or a general-purpose SQL tool like Aqua Data Studio, Squirrel SQL Client - open source, java-based, etc.).

After these initial steps you can have the full team working on the same (remote) model.
Remember: If you need permissions per package in the model you'll have to activate security.

(@2016-11-14: Added instructions link)

TOOLS: UML tools list

One extensive list of UML tools can be found here:

• https://en.wikipedia.org/wiki/List_of_Unified_Modeling_Language_tools

To check:

• ArgoUML
• UMLet

Other already referred here around include:

• Enterprise Architect - Sparx Systems
• MagicDraw

RESOURCE: EA additional documentation

Sparx's Enterprise Architect (EA) UML Modelling Tool has loads of documentation in the WWW (aside from the local online help documentation that typically is very self-contained and informative). Several task-oriented docs exist and are made available via the WWW web site. Some interesting examples are presented here (direct links for download):

Reference Booklets (PDF List):

• http://www.sparxsystems.com.au/resources/booklets/

Getting Started:

• http://www.sparxsystems.com.au/downloads/resources/booklets/getting_started_with_enterprise_architect.pdf (Getting Started)
• http://www.sparxsystems.com.au/downloads/resources/booklets/using_enterprise_architect.pdf  (Using EA)
• http://www.sparxsystems.com.au/bin/EAUserGuide.pdf (User Guide)
• https://www.sparxsystems.com.au/resources/user-guides/basics/tutorial.pdf (Tutorial)

Requirements management with EA:

• https://sparxsystems.com.au/downloads/whitepapers/Requirements_Management_in_Enterprise_Architect.pdf

Data Modelling:

• http://www.sparxsystems.com.au/resources/uml_datamodel.html
• http://www.sparxsystems.com.au/downloads/whitepapers/Database_Modeling_In_UML.pdf
• https://community.sparxsystems.com/white-papers/669-data-modeling-from-conceptual-model-to-dbms (from Conceptual to Physical)

When and how to use Version Control with EA:

• http://www.sparxsystems.com.au/WhitePapers/Version_Control.pdf

UML additional resources: 

• http://www.sparxsystems.com.au/resources/links.html

(Updated: @2016-10-10: Added version control PDF; 2018-03: updated broken links)

TOOLS: Modelling Tools Hot Topics

The main (hot) topics for any modelling tool include:

- How to organize hierarchically information (eventually, segregate model info by SW life cycle phase plus, RFP, Proposal packages)
- UML Support: New packages, new subpackages; new [UML] diagrams; new [UML] elements; establish relationships between them (UML relationships, several types: agreggation, composition, generalization, simple trace, ...);
- How to store requirements information: features (requested, proposed), requirements (several types); features and requirements are not part of the initial UML spec so the tools will support them differently (with some kind of stereotyped UML element most probably); if applicable: How to store testing information (the spec as well as test results including evidences and created issues) - typically for this, test management tools will be used.

- How to create traceability matrices. How to export them (to Word, CSV / Excel, ...)

- How to perform traceability analysis (what relates to what; where is it stored in the model, ...), including gap analysis
- How to draw basic UML diagrams: Some are simpler than other: class, sequence, object, package, deployment, use case, state machine, activity, communication, composite structure, component, interaction overview, and timing diagrams (Tip: See "UML Distilled")
- How to capture sequence diagrams from executable code
- Team conventions for the model: package names, UML Element identifiers (requirements, UML components), ...

If you know how to do this in your UML Modelling tool then you're ready to start modelling.

Advanced tasks for team leaders might also include:
- How to generate documentation from the model (HTML, doc, xls, PDF, more)
- How to reverse engineer: Code, physical database models, Web Services, XML...
- How to forward engineer (classes to code skeletons; tables to DDL SQL, ...)

Additional tasks to be performed:
- How to create a collaborative (centralized) model from scratch
- How to baseline the model (per milestone) and perform backups
- How to activate and configure security (roles, users, authorization)
- How to activate and read audit logs (activity logs, per user)
- How to import and export from the model to other UML tools (XMI support) - either the full model or parts of it

If you know how to do these latter tasks, you're ready to help / manage teams doing modelling.

Modelling tools include Sparx Systems Enterprise Architect (EA), MagicDraw, ...
(Click here for EA additional documentation).

(@2016-07-26: Updated task grouping; minor rephrases/typos; 2016-11-17: EA add. doc. link)

INSTALL: Sparx EA

To install and configure EA to use the floating license, starting from https://delivery.critical.pt/TechAreas/net/SitePages/ToolsPage.aspx select Enterprise Architect (https://delivery.critical.pt/TechAreas/net/SitePages/ToolEnterpriseArchitect.aspx). Look at the PDF with the installation instructions (INTERNAL).

You can also download a free trial from the Sparx Systems WWW site.

BOOK: The Unified Modeling Language Reference (Booch, Jacobson, Runbaugh)

This is the total opposite of the UML Distilled book, mainly because it has ~700 pages.
It is still a very good book by Grady Booch, James Runbaugh and Ivar Jacobson.

http://www.amazon.com/Unified-Modeling-Language-Reference-paperback/dp/032171895X

Book additional details:
ISBN-13: 978-0321718952
ISBN-10: 032171895X

Systems Modeling: About SysML

About SysML, a Systems Engineering Modeling Language, based on UML and using the UML Profile mechanism (that allows it to be extended):

• http://www.omgsysml.org/INCOSE-OMGSysML-Tutorial-Final-090901.pdf
• https://en.wikipedia.org/wiki/Systems_Modeling_Language#List_of_SysML_Tools
• http://www.jot.fm/issues/issue_2007_07/article5.pdf - 155 pages overview
• http://www.informit.com/store/sysml-distilled-a-brief-guide-to-the-systems-modeling-9780321927866 - SysML Distilled BOOK in a format similar to the UML Distilled book. 

PS. Sparx EA tool does support SysML. 

BOOK: UML Distilled (Martin Fowler)

This is my top recommendation for having on the desk, instead of the real UML standards (thousands of pages). If you're using UML to convey some design (or software construction) information, this book on its third edition provides you simple chapters with only a few pages per UML diagram type, speeding you up in understanding (and allowing you to create new) UML Diagrams. 

Our (old) copy of the book

This and the cheat sheet (in the cover pages) makes this book a must have.
You can read more about it here:

• http://www.amazon.com/UML-Distilled-Standard-Modeling-Language-ebook/dp/B000OZ0N8A/ref=sr_1_1?s=digital-text&ie=UTF8&qid=1462357802&sr=1-1&keywords=uml+distilled

From the Back Cover:

Would you like to understand the most important elements of Class diagrams? (See page 35.)
Do you want to see the new UML 2.0 interaction frame notation for adding control flow to sequence diagrams (see page 58) and the unofficial notation that many prefer? (See page 60.)
Do you want to know what changes have been made to all versions of the UML? (See page 151.)
Do you want a quick reference to the most useful parts of the UML notation? (See the inside covers.)
Do you want to find out what diagram types were added to the UML 2.0 without wading through the spec? (See page 11.)
More than 300,000 developers have benefited from past editions of UML Distilled . This third edition is the best resource for quick, no-nonsense insights into understanding and using UML 2.0 and prior versions of the UML.
Some readers will want to quickly get up to speed with the UML 2.0 and learn the essentials of the UML. Others will use this book as a handy, quick reference to the most common parts of the UML. The author delivers on both of these promises in a short, concise, and focused presentation.
This book describes all the major UML diagram types, what they're used for, and the basic notation involved in creating and deciphering them. These diagrams include class, sequence, object, package, deployment, use case, state machine, activity, communication, composite structure, component, interaction overview, and timing diagrams. The examples are clear and the explanations cut to the fundamental design logic.
If you are like most developers, you don't have time to keep up with all the new innovations in software engineering. This new edition of Fowler's classic work gets you acquainted with some of the best thinking about efficient object-oriented software design using the UML--in a convenient format that will be essential to anyone who designs software professionally.
About the Author
Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns. 

(@2016-07-20: Cover photo and co-author)