Course Enquiry System UML Diagram

Posted By freeproject on March 18, 2018

Course Enquiry System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of Course Enquiry System which shows the flows between the activity of Enquiry, Registrations, Syllabus, Students, Fees. The main activity involved in this UML Activity Diagram of Course Enquiry System are as follows:

  • Enquiry Activity
  • Registrations Activity
  • Syllabus Activity
  • Students Activity
  • Fees Activity

Features of the Activity UML diagram of Course Enquiry System

  • Admin User can search Enquiry, view description of a selected Enquiry, add Enquiry, update Enquiry and delete Enquiry.
  • Its shows the activity flow of editing, adding and updating of Registrations
  • User will be able to search and generate report of Syllabus, Students, Fees
  • All objects such as ( Enquiry, Registrations, Fees) are interlinked
  • Its shows the full description and flow of Enquiry, Students, Fees, Syllabus, Registrations
Course Enquiry System Activity Diagram

Course Enquiry System Class Diagram

Posted By freeproject on August 2, 2017

Course Enquiry System Class Diagram describes the structure of a Course Enquiry System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Course Enquiry System are Course, Fees, Syllabus, Students, Registrations, Trainers.

Classes of Course Enquiry System Class Diagram:

  • Course Class : Manage all the operations of Course
  • Fees Class : Manage all the operations of Fees
  • Syllabus Class : Manage all the operations of Syllabus
  • Students Class : Manage all the operations of Students
  • Registrations Class : Manage all the operations of Registrations
  • Trainers Class : Manage all the operations of Trainers

Classes and their attributes of Course Enquiry System Class Diagram:

  • Course Attributes : course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
  • Fees Attributes : fees_id, fees_amount, fees_type, fees_description
  • Syllabus Attributes : syllabus_id, syllabus_course_id, syllabus_name, syllabus_type, syllabus_description
  • Students Attributes : student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
  • Registrations Attributes : registration_id, registration_student_id, registration_course_id, registration_name, registration_type, registration_number, registration_date, registration_description
  • Trainers Attributes : trainer_id, trainer_course_id, trainer_name, trainer_mobile, trainer_email, trainer_username, trainer_password, trainer_address

Classes and their methods of Course Enquiry System Class Diagram:

  • Course Methods : addCourse(), editCourse(), deleteCourse(), updateCourse(), saveCourse(), searchCourse()
  • Fees Methods : addFees(), editFees(), deleteFees(), updateFees(), saveFees(), searchFees()
  • Syllabus Methods : addSyllabus(), editSyllabus(), deleteSyllabus(), updateSyllabus(), saveSyllabus(), searchSyllabus()
  • Students Methods : addStudents(), editStudents(), deleteStudents(), updateStudents(), saveStudents(), searchStudents()
  • Registrations Methods : addRegistrations(), editRegistrations(), deleteRegistrations(), updateRegistrations(), saveRegistrations(), searchRegistrations()
  • Trainers Methods : addTrainers(), editTrainers(), deleteTrainers(), updateTrainers(), saveTrainers(), searchTrainers()

Class Diagram of Course Enquiry System :

Class Diagram Image: 
Course Enquiry System Class Diagram

Course Enquiry System Component Diagram

Posted By freeproject on February 8, 2018

This is a Component diagram of Course Enquiry System which shows components, provided and required interfaces, ports, and relationships between the Syllabus, Enquiry, Course, Registrations and Trainers. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Course Enquiry System UML component diagram, describes the organization and wiring of the physical components in a system.

Components of UML Component Diagram of Course Enquiry System:

  • Syllabus Component
  • Enquiry Component
  • Course Component
  • Registrations Component
  • Trainers Component

Featues of Course Enquiry System Component Diagram:

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

Course Enquiry System Dataflow Diagram

Posted By freeproject on April 18, 2017

Course Enquiry System Data flow diagram is often used as a preliminary step to create an overview of the Course Enquiry without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Course Enquiry process. It contains all of the userflow and their entities such all the flow of Course, Enquiry, Subject, Student, Semester, Fees, Teacher. All of the below diagrams has been used for the visualization of data processing and structured design of the Course Enquiry process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of Course Enquiry System :

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

High Level Entities and proccess flow of Course Enquiry System:

  • Managing all the Course
  • Managing all the Enquiry
  • Managing all the Subject
  • Managing all the Student
  • Managing all the Semester
  • Managing all the Fees
  • Managing all the Teacher
Zero Level DFD Course Enquiry System

First Level Data flow Diagram(1st Level DFD) of Course Enquiry System :

First Level DFD (1st Level) of Course Enquiry System 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 Course Enquiry System system as a whole. It also identifies internal data stores of Teacher, Fees, Semester, Student, Subject that must be present in order for the Course Enquiry system to do its job, and shows the flow of data between the various parts of Course, Subject, Fees, Teacher, Semester 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 Course Enquiry.

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

  • Processing Course records and generate report of all Course
  • Processing Enquiry records and generate report of all Enquiry
  • Processing Subject records and generate report of all Subject
  • Processing Student records and generate report of all Student
  • Processing Semester records and generate report of all Semester
  • Processing Fees records and generate report of all Fees
  • Processing Teacher records and generate report of all Teacher
First Level DFD Course Enquiry System

Second Level Data flow Diagram(2nd Level DFD) of Course Enquiry System :

DFD Level 2 then goes one step deeper into parts of Level 1 of Course Enquiry. It may require more functionalities of Course Enquiry to reach the necessary level of detail about the Course Enquiry functioning. First Level DFD (1st Level) of Course Enquiry System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Teacher, Fees, Semester, Student, Subject, Enquiry, Course.

Low level functionalities of Course Enquiry System

  • Admin logins to the system and manage all the functionalities of Course Enquiry System
  • Admin can add, edit, delete and view the records of Course, Subject, Semester, Teacher
  • Admin can manage all the details of Enquiry, Student, Fees
  • Admin can also generate reports of Course, Enquiry, Subject, Student, Semester, Fees
  • Admin can search the details of Enquiry, Semester, Fees
  • Admin can apply different level of filters on report of Course, Student, Semester
  • Admin can tracks the detailed information of Enquiry, Subject, Student, , Semester
Second Level DFD Course Enquiry System

Course Enquiry System ER Diagram

Posted By freeproject on July 17, 2017

This ER (Entity Relationship) Diagram represents the model of Course Enquiry System Entity. The entity-relationship diagram of Course Enquiry System shows all the visual instrument of database tables and the relations between Fees, Students, Course, Trainers etc. It used structure data and to define the relationships between structured data groups of Course Enquiry System functionalities. The main entities of the Course Enquiry System are Course, Fees, Syllabus, Students, Registrations and Trainers.

Course Enquiry System entities and their attributes :

  • Course Entity : Attributes of Course are course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
  • Fees Entity : Attributes of Fees are fees_id, fees_amount, fees_type, fees_description
  • Syllabus Entity : Attributes of Syllabus are syllabus_id, syllabus_course_id, syllabus_name, syllabus_type, syllabus_description
  • Students Entity : Attributes of Students are student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
  • Registrations Entity : Attributes of Registrations are registration_id, registration_student_id, registration_course_id, registration_name, registration_type, registration_number, registration_date, registration_description
  • Trainers Entity : Attributes of Trainers are trainer_id, trainer_course_id, trainer_name, trainer_mobile, trainer_email, trainer_username, trainer_password, trainer_address

Description of Course Enquiry System Database :

  • The details of Course is store into the Course tables respective with all tables
  • Each entity (Trainers, Syllabus, Registrations, Fees, Course) contains primary key and unique keys.
  • The entity Syllabus, Registrations has binded with Course, Fees entities with foreign key
  • There is one-to-one and one-to-many relationships available between Registrations, Students, Trainers, Course
  • All the entities Course, Registrations, Syllabus, Trainers are normalized and reduce duplicacy of records
  • We have implemented indexing on each tables of Course Enquiry System tables for fast query execution.
Course Enquiry System ER Diagram

Course Enquiry System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of Course Enquiry System which shows the interaction between the objects of Course, Students, Syllabus, Registrations, Enquiry. The instance of class objects involved in this UML Sequence Diagram of Course Enquiry System are as follows:

  • Course Object
  • Students Object
  • Syllabus Object
  • Registrations Object
  • Enquiry Object

This is the UML sequence diagram of Course Enquiry System which shows the interaction between the objects of Course, Students, Syllabus, Registrations, Enquiry. The instance of class objects involved in this UML Sequence Diagram of Course Enquiry System are as follows:

  • Course Object
  • Students Object
  • Syllabus Object
  • Registrations Object
  • Enquiry Object

Course Enquiry System 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 Course Enquiry System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Course Enquiry System. The main actors of Course Enquiry System in this Use Case Diagram are: Super Admin, System User, College, Student, who perform the different type of use cases such as Manage Course, Manage Fees, Manage Syllabus, Manage Students, Manage Registrations, Manage Trainers, Manage Enquiry, Manage Users and Full Course Enquiry System Operations. Major elements of the UML use case diagram of Course Enquiry System are shown on the picture below.

The relationships between and among the actors and the use cases of Course Enquiry System:

  • Super Admin Entity : Use cases of Super Admin are Manage Course, Manage Fees, Manage Syllabus, Manage Students, Manage Registrations, Manage Trainers, Manage Enquiry, Manage Users and Full Course Enquiry System Operations
  • System User Entity : Use cases of System User are Manage Course, Manage Fees, Manage Syllabus, Manage Students, Manage Registrations, Manage Trainers, Manage Enquiry
  • College Entity : Use cases of College are Create Courses, Create Syllabus, Add Content, Check Applications, Approve Applications
  • Student Entity : Use cases of Student are Search Courses, Apply of Course, Check Application Status

Use Case Diagram of Course Enquiry System :

Course Enquiry System Use Case Diagram