... | ... | @@ -15,9 +15,9 @@ Consider a class as a blueprint for creating an object during runtime of an appl |
|
|
Assume that your customer wants you to develop a web application called "StudentData" which is similar to the StudiDB. This application must be accessible by students, lecturers, and administrators. All of these users must be able to register and to login. For this purpose, an external authentication service is used. Students can join lectures and view their exams taken so far. Lecturers can assign grades to students and print reports with statistics about their lectures. Administrators can add users and lectures.
|
|
|
|
|
|
## An Example Class Diagram for the given Scenario
|
|
|
The following figure shows an example UML component diagram which reflects the requirements mentioned in [Example Scenario](#example-scenario):
|
|
|
The following figure shows an example UML class diagram, which reflects the requirements mentioned in [Example Scenario](#example-scenario):
|
|
|
|
|
|

|
|
|

|
|
|
|
|
|
### Explanation
|
|
|
We model several classes in order to represent the central objects within our web application *StudentData*. |