University Project: IST 311 - Sequence Diagram for Music Practice App

This assignment presents a sequence diagram for a music practice application, designed to help students utilize their practice time effectively. The diagram illustrates the interactions between various objects, including the user, controller, and model, within a Model-View-Controller (MVC) architecture. The application allows students to practice note pitches, durations, and both, as well as view high scores and progress. The use of a sequence diagram helps visualize the flow of actions, such as user login and registration, accessing music through the index method, and fetching data from the database using the music model. The assignment emphasizes the importance of the controller in handling requests and the model in acting as a gateway to the database. The ProgressUpdate functionality is also discussed, highlighting the use of client-side scripting to track progress and send data to the backend. The document includes a class diagram, sequence diagram, and bibliography.

Running head: OBJECT-ORIENTED DESIGN
Object-Oriented Design
Name of the Student
Name of the University
Author’s note:

1OBJECT-ORIENTED DESIGN
Class Diagram:
Figure 1: Class Diagram of Music Practice App
(Source: Created by Author)

2OBJECT-ORIENTED DESIGN
Sequence Diagram:
Figure 2: Sequence Diagram
(Source: Created by Author)
This sequence diagram has one actor and five other objects. The use controller is used to
login and register user. Logged in user can see all available music through index method in
MusicController. Model View Controller approach is special because user does not access
requested page directly. Rather user sends a request to controller through URL and controller
decides what to do. The User will call index method and controller will fetch all details from
database using music model. Models in MVC approach has a great significance. Models does not
represent the database but is the gateway to the database. So each time controller needs to fetch
data from database, the website will call models to do that. ProgressUpdate does not lead to any
other view. This is used by combination of server and front end side scripting. Client side

3OBJECT-ORIENTED DESIGN
scripting keep track of progress and when user wants to store data, the client side script sends
XMLHTTP request to backend with progress and auto generated score data.

4OBJECT-ORIENTED DESIGN
Bibliography:
Almadi, S.H., Ali, N.M. and Admodisastro, N., 2018. ID NO. UPM 019 TOPIC: Class Diagram
Recommender System (CDRS): An Educational Tool for UML Class Diagram. UNIVERSITY
CARNIVAL on e-LEARNING (IUCEL) 2018, p.434.
Muñoz, P., Burgueño, L., Vallecillo-Moreno, A.J. and Gogolla, M., 2019. Automatic Generation
of Valid Behavioral Scripts from UML Sequence Diagrams.