Skip to content

Commit 813b2af

Browse files
committed
Link examples in README.md
1 parent 6784539 commit 813b2af

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,10 @@ Use stylings by including the theme file at the top of your code.
3737
```
3838

3939
## Support for the following diagrams
40-
1. Use Cases (see examples/usecase.puml): diagram to support documentation of PEOPLE and PROCESS.
41-
2. Activity (see examples/activity_model.puml): diagram to illustrate activities in a PROCESS. It can be used as an alternative to BPMN diagrams.
42-
3. System model (see examples/systemmodel.puml): diagram for a functional SYSTEM view. Represents the first two layers of a C4 model (System context and Containers)
43-
4. Data model (see examples/datamodel.puml): illustrates a DATA model with or without system specific data types. Main purpose of this model is to have a ubiquitous language for software product deveopment to avoid misunderstandings between users and developers.
44-
5. Class model (see examples/class_model.puml): The class model forms the core of the module design. The classes can be used to represent both level 3 and level 4 in the C4 model. The methods of the classes are the basis of the messages in the sequence model.
45-
6. Sequence model (see examples/systemmodel.puml): The seqence model shows the interactions of the modules from the class model.
46-
7. Mind maps (see examples/mindmap.puml): The mind map visualizes ideas and concepts in a tree-like structure.
40+
1. Use Cases (see [examples/usecase.puml](examples/usecase.puml)): diagram to support documentation of PEOPLE and PROCESS.
41+
2. Activity (see [examples/activity_model.puml](examples/activity_model.puml)): diagram to illustrate activities in a PROCESS. It can be used as an alternative to BPMN diagrams.
42+
3. System model (see [examples/systemmodel.puml](examples/systemmodel.puml)): diagram for a functional SYSTEM view. Represents the first two layers of a C4 model (System context and Containers)
43+
4. Data model (see [examples/datamodel.puml](examples/datamodel.puml)): illustrates a DATA model with or without system specific data types. Main purpose of this model is to have a ubiquitous language for software product deveopment to avoid misunderstandings between users and developers.
44+
5. Class model (see [examples/class_model.puml](/examples/class_model.puml)): The class model forms the core of the module design. The classes can be used to represent both level 3 and level 4 in the C4 model. The methods of the classes are the basis of the messages in the sequence model.
45+
6. Sequence model (see [examples/systemmodel.puml](examples/systemmodel.puml) ): The seqence model shows the interactions of the modules from the class model.
46+
7. Mind maps (see [examples/mindmap.puml](examples/mindmap.puml)): The mind map visualizes ideas and concepts in a tree-like structure.

0 commit comments

Comments
 (0)