- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Student Feedback System Activity Diagram
This is the Activity UML diagram of Student Feeback System which shows the flows between the activity of Subject, Feedback, Class, Teacher, Student. The main activity involved in this UML Activity Diagram of Student Feeback System are as follows:
- Subject Activity
- Feedback Activity
- Class Activity
- Teacher Activity
- Student Activity
Features of the Activity UML diagram of Student Feeback System
- Admin User can search Subject, view description of a selected Subject, add Subject, update Subject and delete Subject.
- Its shows the activity flow of editing, adding and updating of Feedback
- User will be able to search and generate report of Class, Teacher, Student
- All objects such as ( Subject, Feedback, Student) are interlinked
- Its shows the full description and flow of Subject, Teacher, Student, Class, Feedback
Login Activity Diagram of Student Feeback System:
This is the Login Activity Diagram of Student Feeback 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 Class, Subject, Feedback, Student, Teacher. All the pages such as Feedback, Student, Teacher are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Student Feeback System. The various objects in the Student, Class, Subject, Feedback, and Teacher 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
Student Feeback System Class Diagram
Student Feeback System Class Diagram describes the structure of a Student Feeback System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Student Feeback System are Student, Feedback, Class, Faculty, Teacher, Subject.
Classes of Student Feeback System Class Diagram:
- Student Class : Manage all the operations of Student
- Feedback Class : Manage all the operations of Feedback
- Class Class : Manage all the operations of Class
- Faculty Class : Manage all the operations of Faculty
- Teacher Class : Manage all the operations of Teacher
- Subject Class : Manage all the operations of Subject
Classes and their attributes of Student Feeback System Class Diagram:
- Student Attributes : student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
- Feedback Attributes : feedback_id, feedback_title, feedback_type, feedback_comment, feedback_description
- Class Attributes : class_id, class_student_id, class_name, class_room, class_type, class_description
- Faculty Attributes : faculty_id, faculty_teacher_id, faculty_name, faculty_room, faculty_type, faculty_description
- Teacher Attributes : teacher_id, teacher_college_id, teacher_name, teacher_mobile, teacher_email, teacher_username, teacher_password, teacher_address
- Subject Attributes : subject_id, subject_course_id, subject_student_id, subject_name, subject_type, subject_description
Classes and their methods of Student Feeback System Class Diagram:
- Student Methods : addStudent(), editStudent(), deleteStudent(), updateStudent(), saveStudent(), searchStudent()
- Feedback Methods : addFeedback(), editFeedback(), deleteFeedback(), updateFeedback(), saveFeedback(), searchFeedback()
- Class Methods : addClass(), editClass(), deleteClass(), updateClass(), saveClass(), searchClass()
- Faculty Methods : addFaculty(), editFaculty(), deleteFaculty(), updateFaculty(), saveFaculty(), searchFaculty()
- Teacher Methods : addTeacher(), editTeacher(), deleteTeacher(), updateTeacher(), saveTeacher(), searchTeacher()
- Subject Methods : addSubject(), editSubject(), deleteSubject(), updateSubject(), saveSubject(), searchSubject()
Class Diagram of Student Feeback System :
- Posted By: freeproject
- Comments: 0
Student Feeback System Component Diagram
This is a Component diagram of Student Feeback System which shows components, provided and required interfaces, ports, and relationships between the Feedback, Teacher, Feedback Type, Subject and Class. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Student Feeback System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Student Feeback System:
- Feedback Component
- Teacher Component
- Feedback Type Component
- Subject Component
- Class Component
Featues of Student Feeback System Component Diagram:
- You can show the models the components of Student Feeback System.
- Model the database schema of Student Feeback System
- Model the executables of an application of Student Feeback System
- Model the system's source code of Student Feeback System
- Posted By: freeproject
- Comments: 0
Student Feedback System Dataflow Diagram
Student Feedback System Data flow diagram is often used as a preliminary step to create an overview of the Student Feedback without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Student Feedback process. It contains all of the userflow and their entities such all the flow of Student, Feedback, Class, Feedback Type, Faculty, Subject, Teacher. All of the below diagrams has been used for the visualization of data processing and structured design of the Student Feedback process and working flow.
Zero Level Data flow Diagram(0 Level DFD) of Student Feedback System :
This is the Zero Level DFD of Student Feedback System, where we have eloborated the high level process of Student Feedback. It’s a basic overview of the whole Student Feedback System or process being analyzed or modeled. It’s designed to be an at-a-glance view of Faculty,Subject and Teacher showing the system as a single high-level process, with its relationship to external entities of Student,Feedback and Class. It should be easily understood by a wide audience, including Student,Class and Faculty In zero leve DFD of Student Feedback System, we have described the high level flow of the Student Feedback system.High Level Entities and proccess flow of Student Feedback System:
- Managing all the Student
- Managing all the Feedback
- Managing all the Class
- Managing all the Feedback Type
- Managing all the Faculty
- Managing all the Subject
- Managing all the Teacher
First Level Data flow Diagram(1st Level DFD) of Student Feedback System :
First Level DFD (1st Level) of Student Feedback 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 Student Feedback System system as a whole. It also identifies internal data stores of Teacher, Subject, Faculty, Feedback Type, Class that must be present in order for the Student Feedback system to do its job, and shows the flow of data between the various parts of Student, Class, Subject, Teacher, Faculty 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 Student Feedback.Main entities and output of First Level DFD (1st Level DFD):
- Processing Student records and generate report of all Student
- Processing Feedback records and generate report of all Feedback
- Processing Class records and generate report of all Class
- Processing Feedback Type records and generate report of all Feedback Type
- Processing Faculty records and generate report of all Faculty
- Processing Subject records and generate report of all Subject
- Processing Teacher records and generate report of all Teacher
Second Level Data flow Diagram(2nd Level DFD) of Student Feedback System :
DFD Level 2 then goes one step deeper into parts of Level 1 of Student Feedback. It may require more functionalities of Student Feedback to reach the necessary level of detail about the Student Feedback functioning. First Level DFD (1st Level) of Student Feedback System shows how the system is divided into sub-systems (processes). The 2nd Level DFD contains more details of Teacher, Subject, Faculty, Feedback Type, Class, Feedback, Student.Low level functionalities of Student Feedback System
- Admin logins to the system and manage all the functionalities of Student Feedback System
- Admin can add, edit, delete and view the records of Student, Class, Faculty, Teacher
- Admin can manage all the details of Feedback, Feedback Type, Subject
- Admin can also generate reports of Student, Feedback, Class, Feedback Type, Faculty, Subject
- Admin can search the details of Feedback, Faculty, Subject
- Admin can apply different level of filters on report of Student, Feedback Type, Faculty
- Admin can tracks the detailed information of Feedback, Class, Feedback Type, , Faculty
- Posted By: freeproject
- Comments: 0
Student Feeback System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Student Feeback System Entity. The entity-relationship diagram of Student Feeback System shows all the visual instrument of database tables and the relations between Feedback, Faculty, Student, Subject etc. It used structure data and to define the relationships between structured data groups of Student Feeback System functionalities. The main entities of the Student Feeback System are Student, Feedback, Class, Faculty, Teacher and Subject.
Student Feeback System entities and their attributes :
- Student Entity : Attributes of Student are student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
- Feedback Entity : Attributes of Feedback are feedback_id, feedback_title, feedback_type, feedback_comment, feedback_description
- Class Entity : Attributes of Class are class_id, class_student_id, class_name, class_room, class_type, class_description
- Faculty Entity : Attributes of Faculty are faculty_id, faculty_teacher_id, faculty_name, faculty_room, faculty_type, faculty_description
- Teacher Entity : Attributes of Teacher are teacher_id, teacher_college_id, teacher_name, teacher_mobile, teacher_email, teacher_username, teacher_password, teacher_address
- Subject Entity : Attributes of Subject are subject_id, subject_course_id, subject_student_id, subject_name, subject_type, subject_description
Description of Student Feeback System Database :
- The details of Student is store into the Student tables respective with all tables
- Each entity ( Subject, Class, Teacher, Feedback, Student) contains primary key and unique keys.
- The entity Class, Teacher has binded with Student, Feedback entities with foreign key
- There is one-to-one and one-to-many relationships available between Teacher, Faculty, Subject, Student
- All the entities Student, Teacher, Class, Subject are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Student Feeback System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Student Feeback System Sequence Diagram
This is the UML sequence diagram of Student Feeback System which shows the interaction between the objects of Feedback Type, Subject, Faculty, Student, Teacher. The instance of class objects involved in this UML Sequence Diagram of Student Feeback System are as follows:
- Feedback Type Object
- Subject Object
- Faculty Object
- Student Object
- Teacher Object
Login Sequence Diagram of Student Feeback System:
This is the Login Sequence Diagram of Student Feeback System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Faculty, Feedback Type, Subject, Teacher, Student. All the pages such as Subject, Teacher, Student are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Student Feeback System. The various objects in the Teacher, Faculty, Feedback Type, Subject, and Student 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 Student Feeback System which shows the interaction between the objects of Feedback Type, Subject, Faculty, Student, Teacher. The instance of class objects involved in this UML Sequence Diagram of Student Feeback System are as follows:
- Feedback Type Object
- Subject Object
- Faculty Object
- Student Object
- Teacher Object
- Posted By: freeproject
- Comments: 0
Student Feedback System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Student Feeback System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Student Feeback System. The main actors of Student Feeback System in this Use Case Diagram are: Super Admin, System User, Teacher, Student, who perform the different type of use cases such as Manage Student, Manage Feedback, Manage Class, Manage Feedback Type, Manage Faculty, Manage Teacher, Manage Subject, Manage Users and Full Student Feeback System Operations. Major elements of the UML use case diagram of Student Feeback System are shown on the picture below.
The relationships between and among the actors and the use cases of Student Feeback System:
- Super Admin Entity : Use cases of Super Admin are Manage Student, Manage Feedback, Manage Class, Manage Feedback Type, Manage Faculty, Manage Teacher, Manage Subject, Manage Users and Full Student Feeback System Operations
- System User Entity : Use cases of System User are Manage Student, Manage Feedback, Manage Class, Manage Feedback Type, Manage Faculty, Manage Teacher, Manage Subject
- Teacher Entity : Use cases of Teacher are View Feedback, Search Feedback, View Rankings
- Student Entity : Use cases of Student are Submit Feedback, Search Teacherrs, Filters Feedback
Use Case Diagram of Student Feeback System :
