Principles of Programming

This document discusses the sustainability of use-case diagram and the application and evaluation of UML in Principles of Programming. It includes a table of contents, use case diagram, and bibliography.

Running head: PRINCIPLES OF PROGRAMMING
Principles of Programming
Name of the Student
Name of the University
Author’s Note

1
PRINCIPLES OF PROGRAMMING
Table of Contents
Use Case Diagram......................................................................................................................2
Sustainability of use-case diagram.............................................................................................2
Application and Evaluation of UML..........................................................................................4
Bibliography...............................................................................................................................6

2
PRINCIPLES OF PROGRAMMING
Use Case Diagram
Sustainability of use-case diagram
The use case diagram is created prior to the development of new enrolment and
timetabling system for capturing the requirement of the system. The development of use case
helps in identification of the user needs and aligning the system with the development of the
information system (Yoshikawa & Nakagawa, 2016). The requirement of the system is
captured in a readable and understandable form for the end user and provides a narrative

3
PRINCIPLES OF PROGRAMMING
description for user goal oriented interaction. It acts as a dialogue script between the two
actors that helps in capturing dialog between system and user for getting response from the
system. The interaction between the end user helps in identify the requirement that are
needed to be followed and finding out the missing details that are obvious for providing
proper functionality for the information system (Jolak, Vesin & Chaudron, 2017). A
conceptual test cases are needed to be followed and the use case also represents the model for
presenting the abstract view. The use case modelling have a system value and it provides a
systematic, intuitive and readable and understandable for the end user and important for the
developer for the development process. The scope and feature of the information system can
be identified for giving different idea and size of the enrolment and timetabling management
system (Chaudron, 2017). The goal oriented interaction is needed to be used between the
under developed system and external agents. UML notation is used for defining the use case
diagram and supports writing expanded use cases for requirement gathering. Here the actor
represents the external entity which is responsible for getting different values from the
information system. The actors are generally peoples but they may also be external software
system that can be integrated with the information system for increasing the efficiency of the
information system (Thi & Helfert, 2017). The actor can also represent a group of user or
secondary actors associated with the enrolment and time table management system.
The primary and secondary actors are needed to be differentiated for increasing the
usability of the system because each of the actors may have different requirement. Here the
primary actors are the administrator and the secondary actors are the student. While taking
decision including support for trade offs main priority is needed to be given to the primary
actors and support is needed to be provided to the secondary actors. Messages are used for
interacting with the actors and it is needed to be initiated by the use cases or the actors
(Pourali & Atlee, 2018). The use cases and the actors combine to form the use case model.

4
PRINCIPLES OF PROGRAMMING
The use case diagram also represents the relationship between the use cases and the
relationship may be of three types such as include, generalization and extends. Apart from
capturing the requirement for the development of new enrolment and time table management
system it also helps in defining the iterations. The use cases that are need to be implemented
for defining the iterations and it acts as a good source for the development of the class
diagram (Maylawati, Ramdhani & Amin, 2018). The architecture of the system can also be
identified with the development of use case model. It also helps in creating test cases for the
testing phase of software development and eliminate the errors such that the final project is
efficient and work according to the desired outputs. Thus the use case can help in
communicating high level communication for the programmer and add for details in the
software development process.
Application and Evaluation of UML
For the improvement of use case diagram in future the actors and the use case for the
information system is needed to be identified. The flow of information between the different
modules of the information system should also be identified such that the relationship
between actors and the use case can help them to prepare the class diagram and identify the
flow of information between the module. The roles and responsibility of the actor should also
be identified and they are need to categorized according to it. After the development of the
use case it is needed to be tested for performing all the functionality that is required for the
development of new enrolment and time table management system (Addazi et al., 2017). For
the development of the use case interviews is needed to be arranged with the stakeholders and
the requirement of the software information system is needed to be identified. It helps in
identifying the ways the actors would be involved in the system for the management of the
cases. The cases is needed to ne discussed in details for identifying scope of each of the use
cases and deciding the activity that should be involved for integration of the other use cases.

5
PRINCIPLES OF PROGRAMMING
The name of the use case should have a noun and verb such that it can simply define the
cases and the name should also suggest the functionality of the use case (Bhutto et al., 2018).
The use cases are also needed to be prioritized for determining the order of implementation of
use case and following the priority for the deployment of use case helps in risk reduction. The
software developers use the use cases for the implementation of the software system and thus
it is essential for including all the interaction between the system and actors. The interaction
is needed to be organized with a common flow such that the alternative paths for reaching the
goals can be identified (Pourali & Atlee, 2018). The path used for reaching the goal is known
as scenario and the list of the alternative paths are known as inline and the steps should
indicate the order and help in facilitating the reference portion of use case. A structured use
case model is needed to be created such that enough details are added to the model. Writing
of the use case is the best method for requirement analysis of the system and it allows the
development team to gather the requirement in a orderly and through manner as it is gathered
from the external view point and verified with the users.

6
PRINCIPLES OF PROGRAMMING
Bibliography
Addazi, L., Ciccozzi, F., Langer, P., & Posse, E. (2017, July). Towards Seamless Hybrid
Graphical–Textual Modelling for UML and Profiles. In European Conference on
Modelling Foundations and Applications (pp. 20-33). Springer, Cham.
Bhutto, A., Hussain, D. A., Ujjan, I. A., & Syed, M. (2018). Formal Approach for UML
Components Based Development Profile. University of Sindh Journal of Information
and Communication Technology, 2(2), 125-129.
Chaudron, M. R. (2017, May). Empirical studies into UML in practice: pitfalls and prospects.
In 2017 IEEE/ACM 9th International Workshop on Modelling in Software
Engineering (MiSE) (pp. 3-4). IEEE.
Jolak, R., Vesin, B., & Chaudron, M. R. (2017). Using Voice Commands for UML Modelling
Support on Interactive Whiteboards: Insights and Experiences. In CIbSE (pp. 85-98).
Maylawati, D. S. A., Ramdhani, M. A., & Amin, A. S. (2018). Tracing the Linkage of
Several Unified Modelling Language Diagrams in Software Modelling Based on Best
Practices. International Journal of Engineering & Technology (UEA), 7(2.19), 776-
780.
Pourali, P., & Atlee, J. M. (2018). An Experimental Investigation on Understanding the
Difficulties and Challenges of Software Modellers When Using Modelling Tools.
Technical Report CS-2018--03. David R. Cheriton School of Computer Science,
University of Waterloo. 44 pages. https://uwaterloo. ca/computer-science/sites/ca.
computer-science/files/uploads/files/cs-2018--03. pdf.
Thi, T. T. P., & Helfert, M. (2017). Modelling information manufacturing systems. arXiv
preprint arXiv:1704.06226.

7
PRINCIPLES OF PROGRAMMING
Yoshikawa, H., & Nakagawa, T. (2016). Development of plant DiD Risk Monitor system for
NPPs by utilizing UML modelling technology. IFAC-PapersOnLine, 49(19), 397-
402.