Analysis Report

Project Theme : Supplementary Hours

June 8, 2024
Table of Contents

1. Introduction 1

2. The Methods of Modeling 2

2.1. The Modeling Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. the modeling tool used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

3. Structural Diagrams 3
3.1. Class Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. State-Transition Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

4. Interaction Diagrams 4
4.1. Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Activity Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.3. Use Case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

5. First Increment: University Structure 5

5.1. Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. Admin Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3. Activity diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.3.1. Admin Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.3.2. Update Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3.3. Reset Passworrd . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3.4. Create Department . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3.5. update department . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3.6. delete department . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3.7. Create Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3.8. update group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3.9. delete group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3.10. Create Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3.11. update level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.12. delete level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.13. Create Subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.14. update Subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
 5.3.15. delete Subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.16. Create Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3.17. update room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.18. delete room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3.19. Create Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3.20. update section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3.21. delete section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.22. Create Semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.3.23. update semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.3.24. delete semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3.25. Create Specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3.26. update specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3.27. delete Specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4. Sequence diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4.1. Admin Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4.2. update department . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4.3. Reset Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.4. Create Department . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4.5. update department . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4.6. delete department . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.7. Create Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4.8. update group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.4.9. delete group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.4.10. Create Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.4.11. update level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.4.12. delete level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.4.13. Create Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4.14. update Subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.4.15. delete Subject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.4.16. Create Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.4.17. update room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.4.18. delete room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.4.19. Create Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.4.20. update section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3
 5.4.21. delete section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.4.22. Create Semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.4.23. update semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.4.24. delete semester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.4.25. Create Specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.4.26. update specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.4.27. delete Specialty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

6. Second Increment: Teacher 61

6.1. Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.2. Admin Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.3. Teacher Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.3.1. Create Teacher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3.2. Update Teacher . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.3.3. delete Teacher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.3.4. Create non Personel Offdays . . . . . . . . . . . . . . . . . . . . . . 67
6.3.5. Create Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.3.6. Update Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.3.7. delete Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.3.8. Create Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.3.9. Update Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . 72
6.3.10. delete Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.3.11. Create Personel Offdays . . . . . . . . . . . . . . . . . . . . . . . . 74
6.3.12. Create Offdays Type . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.3.13. Update Offdays Type . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.3.14. delete non Personel Offdays . . . . . . . . . . . . . . . . . . . . . . 77
6.3.15. Create Seance Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.3.16. delete Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.3.17. Create Seance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.3.18. Update Seance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.3.19. delete Seance Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.3.20. Create Teacher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.3.21. Update Teacher . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.3.22. delete Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . . 85

4
 6.3.23. Create Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.24. Update Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.3.25. delete Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3.26. Create Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3.27. Update Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . 90
6.3.28. delete Teacher Session . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.3.29. Create Offdays Type . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.3.30. Update Offdays Type . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.3.31. delete Offdays type . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.3.32. Create Seance Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.3.33. Update Seance Type . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.3.34. delete seance type . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.3.35. Update Seance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.3.36. delete Seance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7. deployment Diagram 100

8. Conclusion 101

5
1. Introduction
To ensure the development process precisely addresses client needs, it’s important to formal-
ize informal requirement statements. This formalization helps eliminate misunderstandings
and ambiguities. The process involves analyzing requirements to generate clear and pre-
cise flows that define expected results in terms of functionality, performance, robustness,
and maintenance. These flows are illustrated through different types of diagrams, such as
structural, interaction, and behavioral diagrams. This document will discuss some of these
diagrams and outline the techniques used to create them.

1
2. The Methods of Modeling
2.1. The Modeling Language
Unified Modeling Language (UML) UML (Uni-
fied Modeling Language) is a standardized visual mod-
eling language used in software engineering to express
software design and system architecture. It is designed
for:

• Visualizing system architecture and design.

• Communicating system design to stakeholders.

• Documenting software systems.

• Supporting software development processes.

2.2. the modeling tool used

Astah is a software development tool suite that provides comprehensive support
for software design, modelling, and develop-ment. It is based on the Unified
Modeling Language (UML) and supports a wide range of software development
processes and methodologies, including Agile, Waterfall, and DevOps. It includes
a variety of modelling and diagramming tools and offers integration with popular
development tools.
. . .
.

2
3. Structural Diagrams
Structural diagrams are a type of diagram used in software engineering and systems analysis
to illustrate the structure of a system or software application. They are typically used to
model the components, classes, objects, and relationships between them in a software
system.

3.1. Class Diagrams

A class diagram is a type of UML diagram that represents the classes, interfaces, and their
relationships in a software system. It provides a high-level view of the system’s structure.

3.2. State-Transition Diagrams

A state-transition diagram is a UML diagram that shows the possible states of an object
and the events that cause a transition from one state to another.

3
4. Interaction Diagrams
Interaction diagrams are a type of UML diagram that focuses on illustrating the dynamic
behavior of a system. These diagrams are commonly known as ”Interactivity diagrams”
and are particularly useful in capturing the spatial organization of the various participants
involved in the system’s interactive behavior.

4.1. Sequence Diagrams

Sequence diagrams have a specific focus on presenting the message flow within a system
by providing context for one or multiple lifelines. These diagrams are also capable of
illustrating ordered sequences and facilitating the visualization of real-time data exchange
between the actor and the system (interface, control, and entities).

4.2. Activity Diagrams

Activity diagrams are used to model the flow of activities or processes within a system or
business process. They show the sequence of activities, the decisions that need to be made,
and the relationships between them.

4.3. Use Case Diagrams

Use case diagrams concentrate on delineating the functional requirements of a system from
an external perspective, emphasizing the interactions between various actors and the sys-
tem itself. These diagrams present a clear and structured way to capture the system’s
intended behavior, identifying who (actors) will interact with the system and what goals
(use cases) they aim to achieve. By defining the boundaries of the system, use case diagrams
help in understanding the system’s scope and the relationship between different use cases
and actors. Additionally, these diagrams are instrumental in identifying and organizing
the functional requirements of the system, facilitating communication among stakeholders
and guiding the development process. Through associations, includes, and extends rela-
tionships, use case diagrams provide a comprehensive view of how actors utilize the system
to accomplish their objectives, ensuring that all necessary functionalities are captured and
validated.

4
5. First Increment: University Structure
5.1. Class Diagram
The next section will present the class diagram of the first increment.

Figure 1: Class Diagram for the first increment

5
5.2. Admin Use Case Diagram
The next section will present the Admin Use case diagram

Figure 2: Admin Use case diagram

6
5.3. Activity diagrams
The next section will present activity diagrams of the first increment.

5.3.1. Admin Authentication

Figure 3: activity diagram for admin auth

7
5.3.2. Update Password

Figure 4: activity diagram for update password

8
5.3.3. Reset Passworrd

Figure 5: act diagram of reset password

9
5.3.4. Create Department

Figure 6: activity diagram for create department

10
5.3.5. update department

Figure 7: activity diagram for update department

11
5.3.6. delete department

Figure 8: activity diagram for delete department

12
5.3.7. Create Group

Figure 9: activity diagram for create group

13
5.3.8. update group

Figure 10: activity diagram for update group

14
5.3.9. delete group

Figure 11: activity diagram for delete group

15
5.3.10. Create Level

Figure 12: activity diagram for create level

16
5.3.11. update level

Figure 13: activity diagram for update level

17
5.3.12. delete level

Figure 14: activity diagram for delete level

18
5.3.13. Create Subject

Figure 15: activity diagram for create subject

19
5.3.14. update Subject

Figure 16: activity diagram for update subject

20
5.3.15. delete Subject

Figure 17: activity diagram for delete subject

21
5.3.16. Create Room

Figure 18: activity diagram for create Room

22
5.3.17. update room

Figure 19: activity diagram for update room

23
5.3.18. delete room

Figure 20: activity diagram for delete room

24
5.3.19. Create Section

Figure 21: activity diagram for create section

25
5.3.20. update section

Figure 22: activity diagram for Update section

26
5.3.21. delete section

Figure 23: activity diagram for delete section

27
5.3.22. Create Semester

Figure 24: activity diagram for create semester

28
5.3.23. update semester

Figure 25: activity diagram for update semester

29
5.3.24. delete semester

Figure 26: activity diagram for delete semester

30
5.3.25. Create Specialty

Figure 27: sequence diagram for create specialty

31
5.3.26. update specialty

Figure 28: activity diagram for update specialty

32
5.3.27. delete Specialty

Figure 29: activity diagram for delete specialty

33
5.4. Sequence diagrams
The next section will present sequence diagrams of the first increment.

5.4.1. Admin Authentication

Figure 30: sequence diagram for admin auth

34
5.4.2. update department

Figure 31: sequence diagram for update department

35
5.4.3. Reset Password

Figure 32: sequence diagram for Reset password

36
5.4.4. Create Department

Figure 33: sequence diagram for create department

37
5.4.5. update department

Figure 34: sequence diagram for update department

38
5.4.6. delete department

Figure 35: sequence diagram for delete department

39
5.4.7. Create Group

Figure 36: sequence diagram for create group

40
5.4.8. update group

Figure 37: sequence diagram for update group

41
5.4.9. delete group

Figure 38: sequence diagram for delete group

42
5.4.10. Create Level

Figure 39: sequence diagram for create level

43
5.4.11. update level

Figure 40: sequence diagram for update level

44
5.4.12. delete level

Figure 41: sequence diagram for delete Level

45
5.4.13. Create Module

Figure 42: sequence diagram for create Subject

46
5.4.14. update Subject

Figure 43: sequence diagram for update subject

47
5.4.15. delete Subject

Figure 44: sequence diagram for delete subject

48
5.4.16. Create Room

Figure 45: sequence diagram for create Room

49
5.4.17. update room

Figure 46: activity diagram for update room

50
5.4.18. delete room

Figure 47: sequence diagram for delete room

51
5.4.19. Create Section

Figure 48: sequence diagram for create section

52
5.4.20. update section

Figure 49: activity diagram for update section

53
5.4.21. delete section

Figure 50: sequence diagram for delete section

54
5.4.22. Create Semester

Figure 51: sequence diagram for create semester

55
5.4.23. update semester

Figure 52: activity diagram for update semester

56
5.4.24. delete semester

Figure 53: sequence diagram for delete semester

57
5.4.25. Create Specialty

Figure 54: sequence diagram for create specialty

58
5.4.26. update specialty

Figure 55: activity diagram for update specialty

59
5.4.27. delete Specialty

Figure 56: sequence diagram for delete specialty

60
6. Second Increment: Teacher
6.1. Class Diagram
The next section will present the class diagram of the second increment.

Figure 57: Class Diagram for the Second increment

61
6.2. Admin Use Case Diagram
The next section will present the Admin Use case diagram for the Second Increment

Figure 58: Admin Use case diagram

62
6.3. Teacher Use Case Diagram
The next section will present the Teacher Use case diagram for the Second Increment

Figure 59: Teacher Use case diagram

63
6.3.1. Create Teacher

Figure 60: activity diagram create Teacher

64
6.3.2. Update Teacher

Figure 61: Update Teacher act diag

65
6.3.3. delete Teacher

Figure 62: delete teacher act diag

66
6.3.4. Create non Personel Offdays

Figure 63: create non personal offdays act diag

67
6.3.5. Create Position

Figure 64: create Position

68
6.3.6. Update Position

Figure 65: Update Position

69
6.3.7. delete Position

Figure 66: delete Position

70
6.3.8. Create Teacher Session

Figure 67: create Teacher Session act diag

71
6.3.9. Update Teacher Session

Figure 68: Update Teacher Session act diag

72
6.3.10. delete Teacher Session

Figure 69: delete Teacher Session act diag

73
6.3.11. Create Personel Offdays

Figure 70: create personal offdays act diag

74
6.3.12. Create Offdays Type

Figure 71: activity diagram for create offdays Type

75
6.3.13. Update Offdays Type

Figure 72: Update offdays type act diag

76
6.3.14. delete non Personel Offdays

Figure 73: delete non personal offdays act diag

77
6.3.15. Create Seance Type

Figure 74: create Seance Type act diag

78
6.3.16. delete Position

Figure 75: delete Position

79
6.3.17. Create Seance

Figure 76: create Seance act diag

80
6.3.18. Update Seance

Figure 77: Update Seance act diag

81
6.3.19. delete Seance Type

Figure 78: delete Seance Type act diag

82
6.3.20. Create Teacher

Figure 79: activity diagram create Teacher

83
6.3.21. Update Teacher

Figure 80: Update Teacher seq diag

84
6.3.22. delete Teacher Session

Figure 81: Update Teacher Session act diag

85
6.3.23. Create Position

Figure 82: create Position

86
6.3.24. Update Position

Figure 83: Update Position

87
6.3.25. delete Position

Figure 84: delete Position

88
6.3.26. Create Teacher Session

Figure 85: create Teacher Session seq diag

89
6.3.27. Update Teacher Session

Figure 86: Update Teacher Session seq diag

90
6.3.28. delete Teacher Session

Figure 87: delete Teacher Session seq diag

91
6.3.29. Create Offdays Type

Figure 88: sequence diagram for create offdays Type

92
6.3.30. Update Offdays Type

Figure 89: Update offdays type seq diag

93
6.3.31. delete Offdays type

Figure 90: delete offdays type seq diag

94
6.3.32. Create Seance Type

Figure 91: create Seance Type act diag

95
6.3.33. Update Seance Type

Figure 92: Update seance type

96
6.3.34. delete seance type

Figure 93: delete seance type

97
6.3.35. Update Seance

Figure 94: Update Seance seq diag

98
6.3.36. delete Seance

Figure 95: delete Seance seq diag

99
7. deployment Diagram
the next about deployment diagram of this project

Figure 96: deployment diagram

100
8. Conclusion
In conclusion, the use of modelling techniques and tools, such as UML and Astah uml ,
is essential to accurately analyse a software system. Structural and interaction diagrams
enable effective communication and understanding between stakeholders and developers,
leading to the development of high-quality software systems that meet the needs of clients.

101