UML&OCL Modeling Languages
Summary
UML & OCL are standards to specify the various aspects of sofware systems (each ones being called a "diagram") :
- Use Case to describe the functionalities (: what is it for ?)
- Sequence or object s' communication to represent a particular interaction (: e.g. how to obtain a result ?)
- Statechart to specify the general behavior of a entity 's type.
- Classes and packages to define the general software architecture
- Deployment to define the material one.
- There are other diagrams that are mostly a composition of the previous one (e.g. classes' diagram inside a class, block part in a sequence diagram linked to a state, conceptual states in activity diagram, etc.).
The language has :
- A syntax to be known (and to be understood by the others) and
- A semantic - "objects exchanging messages" as a paradigm to model software.
1 - 10
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL
thiry laurent ensisa uha alsace mulhouse france unified modeling modelisation language constraint object objet UML OCL