Cricket Training Management System UML Diagram

Posted By freeproject on March 18, 2018

Cricket Training Management System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Cricket Training Management System which shows the flows between the activity of Trainer, Schedules, Attendance, Equipments, Fees. The main activity involved in this UML Activity Diagram of Cricket Training Management System are as follows:

  • Trainer Activity
  • Schedules Activity
  • Attendance Activity
  • Equipments Activity
  • Fees Activity

Features of the Activity UML diagram of Cricket Training Management System

  • Admin User can search Trainer, view description of a selected Trainer, add Trainer, update Trainer and delete Trainer.
  • Its shows the activity flow of editing, adding and updating of Schedules
  • User will be able to search and generate report of Attendance, Equipments, Fees
  • All objects such as ( Trainer, Schedules, Fees) are interlinked
  • Its shows the full description and flow of Trainer, Equipments, Fees, Attendance, Schedules
Cricket Training Management System Activity Diagram

Cricket Training Management Class Diagram

Posted By freeproject on August 2, 2017

Cricket Training Management Class Diagram describes the structure of a Cricket Training Management classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Cricket Training Management are Cricket, Trainer, Players, Fees, Schedules, Equipments.

Classes of Cricket Training Management Class Diagram:

  • Cricket Class : Manage all the operations of Cricket
  • Trainer Class : Manage all the operations of Trainer
  • Players Class : Manage all the operations of Players
  • Fees Class : Manage all the operations of Fees
  • Schedules Class : Manage all the operations of Schedules
  • Equipments Class : Manage all the operations of Equipments

Classes and their attributes of Cricket Training Management Class Diagram:

  • Cricket Attributes : cricket_id, cricket_player_id, cricket_trainer_id, cricket_registration, cricket_type, cricket_description
  • Trainer Attributes : trainer_id, trainer_cricket_id, trainer_name, trainer_mobile, trainer_email, trainer_username, trainer_password, trainer_address
  • Players Attributes : player_id, player_college_id, player_name, player_mobile, player_email, player_username, player_password, player_address
  • Fees Attributes : fees_id, fees_amount, fees_type, fees_description
  • Schedules Attributes : schedule_id, schedule_name, schedule_type, schedule_description
  • Equipments Attributes : equipment_id, equipment_name, equipment_type, equipment_description

Classes and their methods of Cricket Training Management Class Diagram:

  • Cricket Methods : addCricket(), editCricket(), deleteCricket(), updateCricket(), saveCricket(), searchCricket()
  • Trainer Methods : addTrainer(), editTrainer(), deleteTrainer(), updateTrainer(), saveTrainer(), searchTrainer()
  • Players Methods : addPlayers(), editPlayers(), deletePlayers(), updatePlayers(), savePlayers(), searchPlayers()
  • Fees Methods : addFees(), editFees(), deleteFees(), updateFees(), saveFees(), searchFees()
  • Schedules Methods : addSchedules(), editSchedules(), deleteSchedules(), updateSchedules(), saveSchedules(), searchSchedules()
  • Equipments Methods : addEquipments(), editEquipments(), deleteEquipments(), updateEquipments(), saveEquipments(), searchEquipments()

Class Diagram of Cricket Training Management :

Class Diagram Image: 
Cricket Training Management Class Diagram

Cricket Training Management System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Cricket Training Management System which shows components, provided and required interfaces, ports, and relationships between the Attendance, Trainer, Schedules, Cricket and Fees. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Cricket Training Management System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Cricket Training Management System:

  • Attendance Component
  • Trainer Component
  • Schedules Component
  • Cricket Component
  • Fees Component

Featues of Cricket Training Management System Component Diagram:

  • You can show the models the components of Cricket Training Management System.
  • Model the database schema of Cricket Training Management System
  • Model the executables of an application of Cricket Training Management System
  • Model the system's source code of Cricket Training Management System
Component Diagram: 

Cricket Training Management Dataflow Diagram

Posted By namita on June 30, 2017

Cricket Training Management Data flow diagram is often used as a preliminary step to create an overview of the Cricket without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Cricket process. It contains all of the userflow and their entities such all the flow of Cricket Trainer, Players, Fees, Schedules, Equipments, Attendance, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the Cricket process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Cricket Training Management :

This is the Zero Level DFD of Cricket Training Management, where we have eloborated the high level process of Cricket. It’s a basic overview of the whole Cricket Training Management or process being analyzed or modeled. It’s designed to be an at-a-glance view of Equipments,Attendance and Login showing the system as a single high-level process, with its relationship to external entities of Cricket Trainer,Players and Fees. It should be easily understood by a wide audience, including Cricket Trainer,Fees and Equipments In zero leve DFD of Cricket Training Management, we have described the high level flow of the Cricket system.

High Level Entities and proccess flow of Cricket Training Management:

  • Managing all the Cricket Trainer
  • Managing all the Players
  • Managing all the Fees
  • Managing all the Schedules
  • Managing all the Equipments
  • Managing all the Attendance
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of Cricket Training Management

First Level Data flow Diagram(1st Level DFD) of Cricket Training Management :

First Level DFD (1st Level) of Cricket Training Management 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 Cricket Training Management system as a whole. It also identifies internal data stores of Login, Attendance, Equipments, Schedules, Fees that must be present in order for the Cricket system to do its job, and shows the flow of data between the various parts of Cricket Trainer, Fees, Attendance, Login, Equipments 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 Cricket.

Main entities and output of First Level DFD (1st Level DFD):

  • Processing Cricket Trainer records and generate report of all Cricket Trainer
  • Processing Players records and generate report of all Players
  • Processing Fees records and generate report of all Fees
  • Processing Schedules records and generate report of all Schedules
  • Processing Equipments records and generate report of all Equipments
  • Processing Attendance records and generate report of all Attendance
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of Cricket Training Management

Second Level Data flow Diagram(2nd Level DFD) of Cricket Training Management :

DFD Level 2 then goes one step deeper into parts of Level 1 of Cricket. It may require more functionalities of Cricket to reach the necessary level of detail about the Cricket functioning. First Level DFD (1st Level) of Cricket Training Management shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Attendance, Equipments, Schedules, Fees, Players, Cricket Trainer.

Low level functionalities of Cricket Training Management

  • Admin logins to the system and manage all the functionalities of Cricket Training Management
  • Admin can add, edit, delete and view the records of Cricket Trainer, Fees, Equipments, Login
  • Admin can manage all the details of Players, Schedules, Attendance
  • Admin can also generate reports of Cricket Trainer, Players, Fees, Schedules, Equipments, Attendance
  • Admin can search the details of Players, Equipments, Attendance
  • Admin can apply different level of filters on report of Cricket Trainer, Schedules, Equipments
  • Admin can tracks the detailed information of Players, Fees, Schedules, , Equipments
Second Level Data flow Diagram(2nd Level DFD) of Cricket Training Management

Cricket Training Management ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Cricket Training Management Entity. The entity-relationship diagram of Cricket Training Management shows all the visual instrument of database tables and the relations between Trainer, Fees, Cricket, Equipments etc. It used structure data and to define the relationships between structured data groups of Cricket Training Management functionalities. The main entities of the Cricket Training Management are Cricket, Trainer, Players, Fees, Schedules and Equipments.

Cricket Training Management entities and their attributes :

  • Cricket Entity : Attributes of Cricket are cricket_id, cricket_player_id, cricket_trainer_id, cricket_registration, cricket_type, cricket_description
  • Trainer Entity : Attributes of Trainer are trainer_id, trainer_cricket_id, trainer_name, trainer_mobile, trainer_email, trainer_username, trainer_password, trainer_address
  • Players Entity : Attributes of Players are player_id, player_college_id, player_name, player_mobile, player_email, player_username, player_password, player_address
  • Fees Entity : Attributes of Fees are fees_id, fees_amount, fees_type, fees_description
  • Schedules Entity : Attributes of Schedules are schedule_id, schedule_name, schedule_type, schedule_description
  • Equipments Entity : Attributes of Equipments are equipment_id, equipment_name, equipment_type, equipment_description

Description of Cricket Training Management Database :

  • The details of Cricket is store into the Cricket tables respective with all tables
  • Each entity (Equipments, Players, Schedules, Trainer, Cricket) contains primary key and unique keys.
  • The entity Players, Schedules has binded with Cricket, Trainer entities with foreign key
  • There is one-to-one and one-to-many relationships available between Schedules, Fees, Equipments, Cricket
  • All the entities Cricket, Schedules, Players, Equipments are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Cricket Training Management tables for fast query execution.
Cricket Training Management ER Diagram

Cricket Training Management System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Cricket Training Management System which shows the interaction between the objects of Players, Attendance, Trainer, Equipments, Schedules. The instance of class objects involved in this UML Sequence Diagram of Cricket Training Management System are as follows:

  • Players Object
  • Attendance Object
  • Trainer Object
  • Equipments Object
  • Schedules Object

This is the UML sequence diagram of Cricket Training Management System which shows the interaction between the objects of Players, Attendance, Trainer, Equipments, Schedules. The instance of class objects involved in this UML Sequence Diagram of Cricket Training Management System are as follows:

  • Players Object
  • Attendance Object
  • Trainer Object
  • Equipments Object
  • Schedules Object

Cricket Training Management Use Case Diagram

Posted By freeproject on July 24, 2017

This Use Case Diagram is a graphic depiction of the interactions among the elements of Cricket Training Management. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Cricket Training Management. The main actors of Cricket Training Management in this Use Case Diagram are: Super Admin, System User, Trainer, Cricketer, who perform the different type of use cases such as Manage Cricket, Manage Trainer, Manage Players, Manage Fees, Manage Schedules, Manage Equipments, Manage Attendance, Manage Users and Full Cricket Training Management Operations. Major elements of the UML use case diagram of Cricket Training Management are shown on the picture below.

The relationships between and among the actors and the use cases of Cricket Training Management:

  • Super Admin Entity : Use cases of Super Admin are Manage Cricket, Manage Trainer, Manage Players, Manage Fees, Manage Schedules, Manage Equipments, Manage Attendance, Manage Users and Full Cricket Training Management Operations
  • System User Entity : Use cases of System User are Manage Cricket, Manage Trainer, Manage Players, Manage Fees, Manage Schedules, Manage Equipments, Manage Attendance
  • Trainer Entity : Use cases of Trainer are Manage Partipants, Manage Timetables, Manage Trainings, Manage Schedules
  • Cricketer Entity : Use cases of Cricketer are Apply for Training, Search Traning, Check Application Status, Make Payment

Use Case Diagram of Cricket Training Management :

 Cricket Training Management Use Case Diagram