Abstract
Maar al te vaak, veiligheid wordt geacht te laat in de ontwikkeling cyclus. Het gevolg is dat vele implementaties zekerheid over de volgende problemen:
* Applicatie-ontwikkelaars zijn sterk betrokken bij de veiligheid. Maar in werkelijkheid, veiligheid is een gespecialiseerd gebied, en de beste beheerd door de beheerders van de veiligheid.
[…]

classes are at the heart of any object-oriented system; therefore, that the most popular UML diagram is the class diagram. A system’s structure is made up of a collection of pieces often referred to as objects. Classes describe the different types of objects that your system can have, and class diagrams these classes […]

http://www.eclipse.org/modeling/mdt/?project=uml2
The Model Development Tools (MDT) project focuses on big “M” modeling within the Modeling project. Its purpose is twofold:
1. To provide an implementation of industry standard metamodels.
2. To provide exemplary tools for developing models based on those metamodels.
http://www.vogella.de/articles/UML/article.html Tutorial
http://www.eclipse.org/modeling/mdt/uml2/docs/articles/Getting_Started_with_UML2/article.html Getting Started tutorial
http://wiki.eclipse.org/MDT-UML2 Wiki for more information

A use case is a case (or situation) where your system is used to fulfill one or more of your user’s requirements. Use cases are at the heart of your model. How can you begin to design a system if you don’t know what it will be required to do?
Use cases specify only what your […]

http://www.omg.org UML is a concise language but a big subject. As well as learning about UML, it’s worth reading through the tutorials and documentation available at the Object Management Group’s web site.

Stereotypes signify a special use or intent and can be applied to almost any element of UML notation. Stereotypes modify th meaning of an element an describe the element’s role within your model.

<< actor, person >>Administrator
Stereotype applied to classe
utility
Represents a class that provides utility services through static method, just as Java math class.
Stereotypes applied to […]

Notes can be placed on a diagram in isolation or attached to a specific part of the diagram as shown.

The 4+1 view model breaks down a model into a set of views, each capturing a specific of your system:

Logical view
Describes the abstract descriptions of a system’s parts. Used to model what a system is made up of and how the parts interact with each other. The types of UML diagrams that typically make […]

UML modeling is not just about diagrams; it’s about capturing your system as a model-the diagrams are actually just windows into that model. A particular diagram will show you some part of your model but not necessarily everything.
Use Case
Interactions between your system and users or other external systems. Also helpful in mapping […]

So, why does any of this matter if your team has a home-grown modeling technique it’s been using for years and you all understand what each other means? If you ever have to show your design to external stakeholders, they might become frustrated trying to understand your home-grown symbols, when you cold have used a […]

It’s a formal language
Each element of the language has a strongly defined meaning , so youcan be confident that when you model a particular facet of your system it will not be misunderstood.
It’s concise
The entire language is made up of simple and straightforward notation.
It’s comprehensive
It describes all important aspect of a system.
It’s scaleable
Where needed, […]