Solutions Produits
Modeling: UML, BPMN, EA
Comprehensive System Modeling
Methodological Support
SOA SolutionA
SOA Architecture
Entreprise Architecture (EA)
Business Process Modeling
Goals, Dictionnary, Business Rules
Requirements
UML Analysis and Design
Document Generation
MDA - Model Driven Architecture
Code Generation: Java, C#, C++
Teamwork
Packaging
UML Modeler
Scope Manager
SOA Solution (EA, BPMN, SOA)
SysML
Document Publisher
TeamWork
MDA Modeler
Java Developer
C# Developer
C++ Developer
SQL Designer
Fortran Developer
Free Add Ons
Modelio Modeler
Services and Assistance
Consulting and Training
Diagrams supported
Products brochures
White papers
Objecteering tutorials
Modelling Practical Guides
Objecteering 6 Enterprise Edition
Objecteering UML Free Edition
Objecteering SOA Free Edition
Patches & Service Packs
Free Add-ons
Objecteering Software
Contact-us
References
Customers
Partners
Events
Accueil
Home Solutions Products Services & Support Ressources Downloads About us Home
Objecteering empowers UML2 – Examples
Présentation
Diagramme de classe
Diagramme de Use Case
Diagramme de d'objets
Diagramme de communication
Diagramme de déploiement
Diagramme de d'activité
Diagramme de séquence
Diagramme
Diagramme d'état
Diagramme de BPMN
Diagramme de profils
Diagramme d'objectifs
Diagramme d'exigences
Diagramme de dictionnaire
Requirement diagrams
A requirement specifies a capability or condition that must be satisfied. A requirement can define a function that a system must perform or a performance condition a system must achieve. A requirement can appear in other diagrams to show its relationships to other model elements. Requirements have properties and links to other elements (requirements or model elements).
In the example, requirements are connected to model elements in order to express model elements that refine, satisfy or verify them.
Requirement diagrams are based on the OMG’s SysML (System Modeling Language) standard.
précedente
suivante
Copyright © 2009 Objecteering Software : Modeling