- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Online Music Portal System Activity Diagram
This is the Activity UML diagram of Online Music Portal System which shows the flows between the activity of Album, Music, Track, Music Library, Performaer. The main activity involved in this UML Activity Diagram of Online Music Portal System are as follows:
- Album Activity
- Music Activity
- Track Activity
- Music Library Activity
- Performaer Activity
Features of the Activity UML diagram of Online Music Portal System
- Admin User can search Album, view description of a selected Album, add Album, update Album and delete Album.
- Its shows the activity flow of editing, adding and updating of Music
- User will be able to search and generate report of Track, Music Library, Performaer
- All objects such as ( Album, Music, Performaer) are interlinked
- Its shows the full description and flow of Album, Music Library, Performaer, Track, Music
Login Activity Diagram of Online Music Portal System:
This is the Login Activity Diagram of Online Music Portal System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Track, Album, Music, Performaer, Music Library. All the pages such as Music, Performaer, Music Library are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Online Music Portal System. The various objects in the Performaer, Track, Album, Music, and Music Library page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Online Music Portal System Class Diagram
Online Music Portal System Class Diagram describes the structure of a Online Music Portal System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Online Music Portal System are Performaer, Track, Music Library, Singer, Music, Album.
Classes of Online Music Portal System Class Diagram:
- Performaer Class : Manage all the operations of Performaer
- Track Class : Manage all the operations of Track
- Music Library Class : Manage all the operations of Music Library
- Singer Class : Manage all the operations of Singer
- Music Class : Manage all the operations of Music
- Album Class : Manage all the operations of Album
Classes and their attributes of Online Music Portal System Class Diagram:
- Performaer Attributes : performer_id, performer_music_id, performer_name, performer_mobile, performer_email, performer_username, performer_password, performer_address
- Track Attributes : track_id, track_music_id, track_name, track_type, track_description
- Music Library Attributes : music_library_id, music_library_name, music_library_type, music_library_description
- Singer Attributes : singer_id, singer_music_id, singer_name, singer_mobile, singer_email, singer_username, singer_password, singer_address
- Music Attributes : music_id, music_album_id, music_type, music_description
- Album Attributes : album_id, album_name, album_type, album_description
Classes and their methods of Online Music Portal System Class Diagram:
- Performaer Methods : addPerformaer(), editPerformaer(), deletePerformaer(), updatePerformaer(), savePerformaer(), searchPerformaer()
- Track Methods : addTrack(), editTrack(), deleteTrack(), updateTrack(), saveTrack(), searchTrack()
- Music Library Methods : addMusic Library(), editMusic Library(), deleteMusic Library(), updateMusic Library(), saveMusic Library(), searchMusic Library()
- Singer Methods : addSinger(), editSinger(), deleteSinger(), updateSinger(), saveSinger(), searchSinger()
- Music Methods : addMusic(), editMusic(), deleteMusic(), updateMusic(), saveMusic(), searchMusic()
- Album Methods : addAlbum(), editAlbum(), deleteAlbum(), updateAlbum(), saveAlbum(), searchAlbum()
Class Diagram of Online Music Portal System :
- Posted By: freeproject
- Comments: 0
Online Music Portal System Component Diagram
This is a Component diagram of Online Music Portal System which shows components, provided and required interfaces, ports, and relationships between the Album, Track, Singer, Music and Music Library. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Online Music Portal System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Online Music Portal System:
- Album Component
- Track Component
- Singer Component
- Music Component
- Music Library Component
Featues of Online Music Portal System Component Diagram:
- You can show the models the components of Online Music Portal System.
- Model the database schema of Online Music Portal System
- Model the executables of an application of Online Music Portal System
- Model the system's source code of Online Music Portal System
- Posted By: freeproject
- Comments: 0
Online Music Portal Dataflow Diagram
Online Music Portal Data flow diagram is often used as a preliminary step to create an overview of the Music Portal without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Music Portal process. It contains all of the userflow and their entities such all the flow of Music, Album, Album Type, Performer, Track, Music Library, Singer. All of the below diagrams has been used for the visualization of data processing and structured design of the Music Portal process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Online Music Portal :
This is the Zero Level DFD of Online Music Portal, where we have eloborated the high level process of Music Portal. It’s a basic overview of the whole Online Music Portal or process being analyzed or modeled. It’s designed to be an at-a-glance view of Track,Music Library and Singer showing the system as a single high-level process, with its relationship to external entities of Music,Album and Album Type. It should be easily understood by a wide audience, including Music,Album Type and Track In zero leve DFD of Online Music Portal, we have described the high level flow of the Music Portal system.High Level Entities and proccess flow of Online Music Portal:
- Managing all the Music
- Managing all the Album
- Managing all the Album Type
- Managing all the Performer
- Managing all the Track
- Managing all the Music Library
- Managing all the Singer
First Level Data flow Diagram(1st Level DFD) of Online Music Portal :
First Level DFD (1st Level) of Online Music Portal shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the Online Music Portal system as a whole. It also identifies internal data stores of Singer, Music Library, Track, Performer, Album Type that must be present in order for the Music Portal system to do its job, and shows the flow of data between the various parts of Music, Album Type, Music Library, Singer, Track of the system. DFD Level 1 provides a more detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of Music Portal.Main entities and output of First Level DFD (1st Level DFD):
- Processing Music records and generate report of all Music
- Processing Album records and generate report of all Album
- Processing Album Type records and generate report of all Album Type
- Processing Performer records and generate report of all Performer
- Processing Track records and generate report of all Track
- Processing Music Library records and generate report of all Music Library
- Processing Singer records and generate report of all Singer
Second Level Data flow Diagram(2nd Level DFD) of Online Music Portal :
DFD Level 2 then goes one step deeper into parts of Level 1 of Music Portal. It may require more functionalities of Music Portal to reach the necessary level of detail about the Music Portal functioning. First Level DFD (1st Level) of Online Music Portal shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Singer, Music Library, Track, Performer, Album Type, Album, Music.Low level functionalities of Online Music Portal
- Admin logins to the system and manage all the functionalities of Online Music Portal
- Admin can add, edit, delete and view the records of Music, Album Type, Track, Singer
- Admin can manage all the details of Album, Performer, Music Library
- Admin can also generate reports of Music, Album, Album Type, Performer, Track, Music Library
- Admin can search the details of Album, Track, Music Library
- Admin can apply different level of filters on report of Music, Performer, Track
- Admin can tracks the detailed information of Album, Album Type, Performer, , Track
- Posted By: freeproject
- Comments: 0
Online Music Portal System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Online Music Portal System Entity. The entity-relationship diagram of Online Music Portal System shows all the visual instrument of database tables and the relations between Track, Singer, Performaer, Album etc. It used structure data and to define the relationships between structured data groups of Online Music Portal System functionalities. The main entities of the Online Music Portal System are Performaer, Track, Music Library, Singer, Music and Album.
Online Music Portal System entities and their attributes :
- Performaer Entity : Attributes of Performaer are performer_id, performer_music_id, performer_name, performer_mobile, performer_email, performer_username, performer_password, performer_address
- Track Entity : Attributes of Track are track_id, track_music_id, track_name, track_type, track_description
- Music Library Entity : Attributes of Music Library are music_library_id, music_library_name, music_library_type, music_library_description
- Singer Entity : Attributes of Singer are singer_id, singer_music_id, singer_name, singer_mobile, singer_email, singer_username, singer_password, singer_address
- Music Entity : Attributes of Music are music_id, music_album_id, music_type, music_description
- Album Entity : Attributes of Album are album_id, album_name, album_type, album_description
Description of Online Music Portal System Database :
- The details of Performaer is store into the Performaer tables respective with all tables
- Each entity ( Album, Music Library, Music, Track, Performaer) contains primary key and unique keys.
- The entity Music Library, Music has binded with Performaer, Track entities with foreign key
- There is one-to-one and one-to-many relationships available between Music, Singer, Album, Performaer
- All the entities Performaer, Music, Music Library, Album are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Online Music Portal System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Online Music Portal System Sequence Diagram
This is the UML sequence diagram of Online Music Portal System which shows the interaction between the objects of Album, Music Library, Album Type, Singer, Performaer. The instance of class objects involved in this UML Sequence Diagram of Online Music Portal System are as follows:
- Album Object
- Music Library Object
- Album Type Object
- Singer Object
- Performaer Object
Login Sequence Diagram of Online Music Portal System:
This is the Login Sequence Diagram of Online Music Portal System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Album Type, Album, Music Library, Performaer, Singer. All the pages such as Music Library, Performaer, Singer are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Online Music Portal System. The various objects in the Performaer, Album Type, Album, Music Library, and Singer page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Online Music Portal System which shows the interaction between the objects of Album, Music Library, Album Type, Singer, Performaer. The instance of class objects involved in this UML Sequence Diagram of Online Music Portal System are as follows:
- Album Object
- Music Library Object
- Album Type Object
- Singer Object
- Performaer Object
- Posted By: freeproject
- Comments: 0
Online Music Portal System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Online Music Portal System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Online Music Portal System. The main actors of Online Music Portal System in this Use Case Diagram are: Super Admin, System User, Anonymous Users, Users, who perform the different type of use cases such as Manage Performaer, Manage Track, Manage Music Library, Manage Singer, Manage Music, Manage Album, Manage Album Type, Manage Users and Full Online Music Portal System Operations. Major elements of the UML use case diagram of Online Music Portal System are shown on the picture below.
The relationships between and among the actors and the use cases of Online Music Portal System:
- Super Admin Entity : Use cases of Super Admin are Manage Performaer, Manage Track, Manage Music Library, Manage Singer, Manage Music, Manage Album, Manage Album Type, Manage Users and Full Online Music Portal System Operations
- System User Entity : Use cases of System User are Manage Performaer, Manage Track, Manage Music Library, Manage Singer, Manage Music, Manage Album, Manage Album Type
- Anonymous Users Entity : Use cases of Anonymous Users are View Information, Fill Contact Us, Search Content
- Users Entity : Use cases of Users are Search Tracks, Create Own Album, Add Tracks to Album, Play Music, Download Music
Use Case Diagram of Online Music Portal System :
