MIS501 Assessment: Analysis of Enrolment and Timetable UML Diagrams

This report evaluates a hand-drawn Use Case diagram designed for an enrolment and timetable system at Torrens University Australia. The analysis focuses on the diagram's suitability for effective communication, highlighting the absence of a programmer as a customer, which impacts high-level communication. The report provides constructive criticism, pointing out the untidy visuals and the need for clearer customer roles, specifically the inclusion of programmers and the diversification of student groups. Recommendations include a thorough review of the case study requirements, improvements in diagram clarity, and the establishment of a stronger relationship between the program director and the timetable manager. The report also suggests including key customers like existing students and programmers. The conclusion emphasizes the diagram's descriptiveness, while also pointing out flaws, such as the inclusion of unnecessary customers and the omission of important activities. The report concludes that if these issues were addressed, the diagram would be significantly improved.

Running Head: ENROLMENT AND TIME TABLE SCHEDULER
ENROLMENT AND TIME TABLE SCHEDULER
Name of the Student
Name of the University
Author note

1
ENROLMENT AND TIME TABLE SCHEDULER
Table of Contents
Introduction......................................................................................................................................2
Suitability of the diagram for proper communication.....................................................................2
Constructive criticism for the other’s diagram................................................................................2
Recommendation.............................................................................................................................4
Recommended readings...................................................................................................................4
Conclusion.......................................................................................................................................4
Bibliography....................................................................................................................................6

2
ENROLMENT AND TIME TABLE SCHEDULER
Introduction
This report is based on developing Use case diagrams for implementation of enrolment
and timetable system in Torrens University Australia. This report is discussing about the
sustainability of the diagram that is hand drawn. This report is also providing the constructive
critique to the hand drawn diagram that is allocated by facilitator and hence wise recommend
readings that might be beneficial.
Suitability of the diagram for proper communication
The major missing of the diagram is that there is no programmer as a customer in the use
case. This is the main reason that the suitability of the project as per the performing high level
communication with the programmer reduces. Despite the fact that the programmer as a
customer’s absence has been degrading the quality of the diagram, it is to be stated that the
diagram has established a proper relation in between the higher hierarchy of customers and lower
hierarchy of customers. This is the major reason that this diagram can be considered as logically
correct. Only if the customer program was present the entire diagram would have been highly
suitable for performing high level communication. Even presence of other staffs in the diagram
is made which would have enhanced the communication process if the programmers would have
been present.
Constructive criticism for the other’s diagram
The diagram that is provided has been very untidy in the first place. The visuals are also
unclear.

3
ENROLMENT AND TIME TABLE SCHEDULER
To start of the diagram it is seen that there are 5 customers, the customers are namely
Program director, Time Table manager, Teacher, Student and other staffs. These are the
customers that were provided in the case study. According to me, these customers were just
examples of customers that are to be used in the project. Despite the fact that it is obvious that
these customers are to be included in the diagram, there are few other customers that are to be
implemented with holding these customers. As per my knowledge, inclusion of programmer as a
customer and diversification of the student group into 2 sections .i.e. Existing students and New
Students will be useful in this case. To start off with the use cases there are total 7 direct use
cases and 5 other extended uses cases from the initial section. The first use case that is
considered is the Log In use case. In this use case all the customers’ needs to log in the system as
per the stated diagram. Which is obvious as that is the sole way out for the starting the entire
process. However that have been an issue in the log in use case as there are 5 extended uses cases
attached to the same. As the project that is considered in this case is not regarding the logging
process so this exaggerated detailing is not needed however the detailing that is provided depicts
proper knowledge and depth of the student in this field. So the extended use cases from Log in
use case are Program director Log in, Time table manger log in, teaching staff log in, student log
in and other staff log in. The main aspect that is missing is that there is no diversification of the
existing students and the new students. As per the case study the existing students will be
providing insights during developing the project. This part of the project is completely missing
and hence wise a complete activity is missed in the diagram. Again it is to be stated that that in
the diagram the other staffs that are present are not having any task to complete, yet they are
present in the diagram. It is seen that they have just logged in and no other task is done by them
henceforth there is no need of including them in the diagram and similarly in the database of the

4
ENROLMENT AND TIME TABLE SCHEDULER
system. Another major mistake that can be considered is that the program director is less
involved in the project. In this diagram the job role of the program director is to perform opening
of classes and allocating the classes to teacher. He must also have the acknowledgement in the
time setting process after the student and the time table manager gets in a deal. Job role of the
teacher is also not stated in a proper manner.
Recommendation
The recommendations that are to be stated are as follows: -
 The case study must be read properly as few of the requirements of the project are
overlooked while preparing the diagram.
 The diagram needs to be more clear and tidy
 Proper relation in between the program director and the time table manager is to
be established. This will ensure that proper communication process can be established.
 Few important customers like the existing student and the programmers are
needed to be included in the diagram.
It can be stated that if these measures are followed in a proper manner then the project
will be a successful one.
Recommended readings
As per the diagram that is provided it can be stated that the student already has an
extensive knowledge regarding developing use case diagram. Hence for bettering the knowledge
of he can further read the books that are stated in the bibliography section.

5
ENROLMENT AND TIME TABLE SCHEDULER
Conclusion
From the above conclusion it can be stated that the diagram is highly descriptive. The
descriptiveness of the picture can be well stated through the log in section of the diagram.
However there are several issues that are present in the diagram. Usage of excess customers that
are of no use are present in the diagram like the other staffs. They are not having any task in the
entire project yet they are present in the diagram. However absence of important customers are
also noted in this customers. Few customers are missed like the existing students which had led
to missing of an entire activity. In case all these issues were mitigated this diagram would have
been a proper diagram and not much flaws would have been detected in it.

6
ENROLMENT AND TIME TABLE SCHEDULER
Bibliography
Singh, A., & Sharma, E. S. (2015). Functional Test Cases Generation Based on Automated
Generated Use Case Diagram. Chandigarh University, International Journal of
Innovative Research in Advanced Engineering (IJIRAE), 2(8).
Singh, M., Sharma, A. K., & Saxena, R. (2016). Formal Transformation of UML Diagram: Use
Case, Class, Sequence Diagram with Z Notation for Representing the Static and Dynamic
Perspectives of System. In Proceedings of International Conference on ICT for
Sustainable Development(pp. 25-38). Springer, Singapore.
Sabharwal, S., Kaur, P. and Sibal, R., 2017. Empirical and Theoretical Validation of a Use Case
Diagram Complexity Metric. Int. Assoc. of, pp.35-47.
Vachharajani, V., Vasant, S., & Pareek, J. (2016). Feasibility Study of Proposed Architecture for
Automatic Assessment of Use-Case Diagram. In Proceedings of International
Conference on ICT for Sustainable Development (pp. 97-104). Springer, Singapore.
Faitelson, D., & Tyszberowicz, S. (2017, May). UML diagram refinement (focusing on class-and
use case diagrams). In Proceedings of the 39th International Conference on Software
Engineering (pp. 735-745). IEEE Press.
Seidl, M., Scholz, M., Huemer, C., & Kappel, G. (2015). The Use Case Diagram. In UML@
Classroom (pp. 23-47). Springer, Cham.
Krainer, D., Ströckl, D. E., & Oberzaucher, J. (2017, June). Use Case Focused User-Interaction
Diagram: A Communication Tool within AAL Projects. In Proceedings of the 10th

7
ENROLMENT AND TIME TABLE SCHEDULER
International Conference on PErvasive Technologies Related to Assistive
Environments (pp. 193-196). ACM.
Minhas, N. M., Masood, S., Petersen, K., & Nadeem, A. (2018). A Systematic Mapping of Test
Case Generation Techniques Using UML Interaction Diagram. Journal of Software:
Evolution and Process.
Vachharajani, V., & Pareek, J. (2019). Framework To Approximate Label Matching For
Automatic Assessment Of Use-Case Diagram. International Journal of Distance
Education Technologies (IJDET), 17(3), 75-95.

8
ENROLMENT AND TIME TABLE SCHEDULER

9
ENROLMENT AND TIME TABLE SCHEDULER