School Automation System UML Diagram

Posted By freeproject on March 23, 2018

School Automation System Activity Diagram

Posted By freeproject on March 13, 2018

This is the Activity UML diagram of School Automation System which shows the flows between the activity of School, Course, Registration, Classes, Teacher. The main activity involved in this UML Activity Diagram of School Automation System are as follows:

  • School Activity
  • Course Activity
  • Registration Activity
  • Classes Activity
  • Teacher Activity

Features of the Activity UML diagram of School Automation System

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

School Automation System Class Diagram

Posted By freeproject on August 2, 2017

School Automation System Class Diagram describes the structure of a School Automation System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the School Automation System are Teachers, Cources, Registrations, Schools, Students, Classes.

Classes of School Automation System Class Diagram:

  • Teachers Class : Manage all the operations of Teachers
  • Cources Class : Manage all the operations of Cources
  • Registrations Class : Manage all the operations of Registrations
  • Schools Class : Manage all the operations of Schools
  • Students Class : Manage all the operations of Students
  • Classes Class : Manage all the operations of Classes

Classes and their attributes of School Automation System Class Diagram:

  • Teachers Attributes : teacher_id, teacher_college_id, teacher_name, teacher_mobile, teacher_email, teacher_username, teacher_password, teacher_address
  • Cources Attributes : course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
  • Registrations Attributes : registration_id, registration_student_id, registration_course_id, registration_name, registration_type, registration_number, registration_date, registration_description
  • Schools Attributes : school_id, school_name, school_type, school_description
  • Students Attributes : student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
  • Classes Attributes : class_id, class_student_id, class_name, class_room, class_type, class_description

Classes and their methods of School Automation System Class Diagram:

  • Teachers Methods : addTeachers(), editTeachers(), deleteTeachers(), updateTeachers(), saveTeachers(), searchTeachers()
  • Cources Methods : addCources(), editCources(), deleteCources(), updateCources(), saveCources(), searchCources()
  • Registrations Methods : addRegistrations(), editRegistrations(), deleteRegistrations(), updateRegistrations(), saveRegistrations(), searchRegistrations()
  • Schools Methods : addSchools(), editSchools(), deleteSchools(), updateSchools(), saveSchools(), searchSchools()
  • Students Methods : addStudents(), editStudents(), deleteStudents(), updateStudents(), saveStudents(), searchStudents()
  • Classes Methods : addClasses(), editClasses(), deleteClasses(), updateClasses(), saveClasses(), searchClasses()

Class Diagram of School Automation System :

Class Diagram Image: 
School Automation System Class Diagram

School Automation System Component Diagram

Posted By freeproject on February 8, 2018

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

Components of UML Component Diagram of School Automation System:

  • Student Component
  • Classes Component
  • Registration Component
  • Course Component
  • School Component

Featues of School Automation System Component Diagram:

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

School Automation System Dataflow Diagram

Posted By namita on July 10, 2017

School Automation System Data flow diagram is often used as a preliminary step to create an overview of the School without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the School process. It contains all of the userflow and their entities such all the flow of Schools, Students, Classes, Teachers, Cources, Registrstion, Login. All of the below diagrams has been used for the visualization of data processing and structured design of the School process and working flow.


Zero Level Data flow Diagram(0 Level DFD) of School Automation System :

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

High Level Entities and proccess flow of School Automation System:

  • Managing all the Schools
  • Managing all the Students
  • Managing all the Classes
  • Managing all the Teachers
  • Managing all the Cources
  • Managing all the Registrstion
  • Managing all the Login
Zero Level Data flow Diagram(0 Level DFD) of School Automation System

First Level Data flow Diagram(1st Level DFD) of School Automation System :

First Level DFD (1st Level) of School Automation 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 School Automation System system as a whole. It also identifies internal data stores of Login, Registrstion, Cources, Teachers, Classes that must be present in order for the School system to do its job, and shows the flow of data between the various parts of Schools, Classes, Registrstion, Login, Cources 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 School.

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

  • Processing Schools records and generate report of all Schools
  • Processing Students records and generate report of all Students
  • Processing Classes records and generate report of all Classes
  • Processing Teachers records and generate report of all Teachers
  • Processing Cources records and generate report of all Cources
  • Processing Registrstion records and generate report of all Registrstion
  • Processing Login records and generate report of all Login
First Level Data flow Diagram(1st Level DFD) of School Automation System

Second Level Data flow Diagram(2nd Level DFD) of School Automation System :

DFD Level 2 then goes one step deeper into parts of Level 1 of School. It may require more functionalities of School to reach the necessary level of detail about the School functioning. First Level DFD (1st Level) of School Automation System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Login, Registrstion, Cources, Teachers, Classes, Students, Schools.

Low level functionalities of School Automation System

  • Admin logins to the system and manage all the functionalities of School Automation System
  • Admin can add, edit, delete and view the records of Schools, Classes, Cources, Login
  • Admin can manage all the details of Students, Teachers, Registrstion
  • Admin can also generate reports of Schools, Students, Classes, Teachers, Cources, Registrstion
  • Admin can search the details of Students, Cources, Registrstion
  • Admin can apply different level of filters on report of Schools, Teachers, Cources
  • Admin can tracks the detailed information of Students, Classes, Teachers, , Cources
Second Level Data flow Diagram(2nd Level DFD) of School Automation System

School Automation System ER Diagram

Posted By freeproject on July 17, 2017

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

School Automation System entities and their attributes :

  • Teachers Entity : Attributes of Teachers are teacher_id, teacher_college_id, teacher_name, teacher_mobile, teacher_email, teacher_username, teacher_password, teacher_address
  • Cources Entity : Attributes of Cources are course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
  • Registrations Entity : Attributes of Registrations are registration_id, registration_student_id, registration_course_id, registration_name, registration_type, registration_number, registration_date, registration_description
  • Schools Entity : Attributes of Schools are school_id, school_name, school_type, school_description
  • Students Entity : Attributes of Students are student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
  • Classes Entity : Attributes of Classes are class_id, class_student_id, class_name, class_room, class_type, class_description

Description of School Automation System Database :

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

School Automation System Sequence Diagram

Posted By freeproject on January 31, 2018

This is the UML sequence diagram of School Automation System which shows the interaction between the objects of Teacher, Registration, School, Student, Classes. The instance of class objects involved in this UML Sequence Diagram of School Automation System are as follows:

  • Teacher Object
  • Registration Object
  • School Object
  • Student Object
  • Classes Object

This is the UML sequence diagram of School Automation System which shows the interaction between the objects of Teacher, Registration, School, Student, Classes. The instance of class objects involved in this UML Sequence Diagram of School Automation System are as follows:

  • Teacher Object
  • Registration Object
  • School Object
  • Student Object
  • Classes Object

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

The relationships between and among the actors and the use cases of School Automation System:

  • Super Admin Entity : Use cases of Super Admin are Manage Teachers, Manage Cources, Manage Registrations, Manage Schools, Manage Students, Manage Classes, Manage Users and Full School Automation System Operations
  • System User Entity : Use cases of System User are Manage Teachers, Manage Cources, Manage Registrations, Manage Schools, Manage Students, Manage Classes
  • Admission Department Entity : Use cases of Admission Department are Create Registration, Add Students, View Applications, Download Reports
  • Student Entity : Use cases of Student are Add Admission Forms, View Details, Apply for Admission

Use Case Diagram of School Automation System :

School Automation System Use Case Diagram

Project Category