Scribd Logo
Upload

Welcome to Scribd!

    • 3K views

    Hard Copy of Faculty Feedback System

    Uploaded by

    Saurav Datta
    Faculty Feed Back System

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Hard Copy of Faculty Feedback System

    Uploaded by

    Saurav Datta
    3K views16 pages
    Faculty Feed Back System

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Faculty Feed Back System

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    3K views16 pages

    Hard Copy of Faculty Feedback System

    Uploaded by

    Saurav Datta
    Faculty Feed Back System

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 16
    At a glance
    Powered by AI
    The document discusses the design and development of a Faculty Feedback System using different diagrams and methodologies. It covers chapters on introduction, problem solving methodology, design solution, testing, future scope and conclusion.

    The different chapters covered are introduction, problem solving methodology, design solution and software architecture, result and observation, testing methodology, future scope and conclusion.

    The different types of diagrams used are Data Flow Diagram (DFD), Entity Relationship Diagram (ERD). DFD shows the logical flow of the system and ERD represents the logical structure of the database.

    Chapter 1 1) Introduction 1.1) 1.2) 1.3) 1.4) 1.5) Chapter 2 2) Problem Solving Methodology (Requirement Analysis) 2.1) 2.

    .2) 2.3) Chapter 3 3) Design Solution & Software Architecture............ 3.1) Software Design..........17 3.2) Use Case Diagram..........19 3.3) Use Case Specification20 3.4) Entity Identification28 3.5) Entity Relationship Diagram......34 3.6) Abbreviation & Symbols Used in the ERD34 3.7) ER - Diagram.30 3.8) Detail Table Structure31 Chapter 4 4) Result & Observation 4.1) Control Flow of the Project...35 4.2) Sample Screens Snapshot.39 4.3) Time Analysis51 4.4) Gantt chart51 Data Flow Diagram....13 CAD.....14 Level 1 DFD15 Theoretical Concept .4 Problem Statement ...5 Objective ..7 Scope of the Project .7 Assumption of the Project Configuration.9

    4.5) PERT Chart52 4.6) Cost & Benefit Analysis.53 Chapter 5 5) Testing Methodology. 5.1) Software Testing55 5.2) Sample Test Case........58

    Chapter 6 6) Future Scope .61

    Chapter 7 7) Conclusion 63

    Appendix Sample Source Code.64 Reference & Bibliography ...70

    Chapter - 1
    Introduction
    THE FACULTY FEEDBACK SYSTEM mainly encompasses on the feedbacks given by the students of any department of a college/institution on their respective faculties. The system is built with the key idea of making it as much as interactive and simple which can be readily used as a native user. Generally FACULTY FEEDBACK SYSTEM focuses on the records of keeping the feedback taken from the students and hence
    maintaining such records on paper is rather a laborious and hectic method. Our project is aimed to curve out the way from the hectic paper work of physically maintaining log records and provide an alternative and efficient way to do the same work with much higher precision and in half of time. It is designed and developed by keeping in mind that it can be very easily retrieved and updated and also with the idea that it can be very user friendly so that it becomes a complete success among every departments of a college. The system draws its strength from its simplicity, inter activeness and user friendliness by enabling the native users to use it without the overhead of inbuilt complexities.

    Faculty Feedback System is the process of taking feedback of each and every student of any department on their respective faculty. This process if done manually requires lot of paperwork which is very complex. So to reduce the workload and paperwork faculty feedback system has been developed.

    Hardware Requirement

    Hard Drive Capacity CD/DVD Drive RAM CPU Monitor Mouse Keyboard

    : 40GB : As required : 1GB recommended : Pentium (4), 1.50 GHz : Color (14 inch or more) : Optical mouse : M/M Keyboard

    Software Requirement
    Operating System Data Base Server : Windows XP Professional SP 2/Windows -7

    : MySQL : Apache Foundation

    Software Used For Development


    Operating System Data Base Server Front End Business Logic : Windows XP Professional SP 2/Windows -7

    :MySQL : Apache Foundation

    : Html, JavaScript, Cascading Style Sheet : PHP

    The project is hinged on three-tier architecture They are: Client end, which consists of forms, designed using Html, Java Script, Css Business Logic at Server End designed php Back end, which consist of MySQL

    PHP stands for Hypertext Processor, developed in 1994 by Rasmus Lerdorf while finding a way to control and customize his personal homepage in a better way. According to the sources, it all began with building some CGI binaries but then he got interest and started working with many applications in PHP. At that time it was not so interesting but as time changed, it became popular with its PHP forms and then it became a great web development language. PHP is a server side scripting.

    PHP has been used in developing this project because of its following features

    PHP runs on different platforms (Windows, Linux, Unix, etc.) PHP is compatible with almost all servers used today (Apache, IIS, etc.) PHP is FREE to download from the official PHP resource.

    PHP frameworks provide a low barrier of entry for web developers as it is easy to learn and runs efficiently on the server side

    PHP is a light programming code

    MySQL is a relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It is named after developer Michael Widenius' daughter, My. The SQL phrase stands for Structured Query Language.

    Reason behind choosing MySQL for database are as follows:


    MySQL is an extensible, open source database engine MySQL is very secure to use MySQL is platform independent

    Chapter - 2
    Problem Solving Methodology (REQUIREMENT ANALYSIS)

    Data Flow Diagram (DFD) was popularized by D. E. Macro in 1978 and Gane & Sarson in1979 through their structured system analysis methodologies. According to their vision data flow diagram should be the first tool used for the purpose of preparing a model system. A DFD also known as Bubble Chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So, it is the starting point of the design phase that functionally decomposes the requirement specifications down to the lowest level.

    Data Flow Diagrams (DFD) shows the logical flow of a system and defines the boundaries of the system. For a candidate system, it describes the inputs (source), outputs (destination), databases (data stores), and procedures (data flows). 2.1.2 Abbreviations & Symbols Used In The DFDs With Their Meanings Are As Follows

    1.

    DFD

    : Data Flow Diagram

    2.

    : Process

    3.

    : Data Flow

    4.

    : Data Store

    5.

    :External Entity

    Request for Edit Profile

    Profile
    Managemen t Sending Profile info

    Registered User
    Request for Login Sending Login info

    User Profile Details

    Log In
    Request for Login User Reg Details Sending Login info customer_profil e

    Admin

    customer_reg General User

    Registered User

    Requesting Thread Posting

    Sending Registration info

    Request for Registration

    Sending Thread info

    Thread/ Question Post

    Registratio n

    customer_reg

    Requesting Ans Posting

    User Details

    Answer Post

    Thread Details

    Admin

    Chapter - 3
    Design Solution and Software Architecture

    3.5 Entity Relation Diagram


    Entity Relationship Diagram constitutes a technique for representing the logical structure of a database in a pictorial manner. They provide a simple and readily understood means of communicating the salient features of the design of any given database. It was introduced by Chen in 1976. It uses three features to describe data: i) Entities, which specify distinct real world items in an application. ii) Relationships which connect entities and represent meaningful dependencies between them. iii) Attributes, which specify properties of entities and relationships. 3.6 Follows Abbreviations & Symbols Used In the ERDs With Their Meanings Are as

    : Attribute

    : Data Flow

    : Decision Box

    : Entity

    You might also like