Indira Gandhi National Open University Project Mini  Report Sample On MCA  At










NAME: …………….

ENROLMENT NO:  ………………………


Submitted in partial fulfillment for the award of the Degree of

Master of Computer Applications (MCA)

Indira Gandhi National Open University

Maidan Garhi

New Delhi – 110068.



Name                                                          :        ……………………

Enrollment  No.                               :        …………………….




I hereby declare that this project work titled “ONLINE APPOINTMENT MANAGEMENT SYSTEM ” is my original work and no part or it has been submitted for may other degree purpose or published in any other from till date.








  1.1. Background                                                                                                             6
  1.2. Objectives                                                                                                               6
  1.3Purpose, Scope, and Applicability                                                                            8
     1.3.1 Purpose                                                                                                              8
     1.3.2 Scope                                                                                                                9
     1.3.3 Applicability                                                                                                    10
CHAPTER 2. SURVEY OF TECHNOLOGIES                                    11
CHAPTER 3. REQUIREMENTS AND ANALYSIS                                         
3.1. Problem Definition                                                                                                   13
3.2. Requirements Specification                                              14
3.3. Planning and Scheduling                                                                                         23
3.4  Software and Hardware Requirements                                                                     26
3.5  Conceptual Models                                                                                                 39
CHAPTER 4.  SYSTEM DESIGN                                            
4.1. Data Design                                                                                                            41
4.2   Physical Design                                                                                                      42
4.2.1   Design Methodology                                                                           42
4.2.2.  Design Overview                                                                                 42
4.2.3.  Process Modeling                                                                                43
4.3  Data Flow Diagram                                                                                                44
4.4  Data Modeling                                                                                                         53
4.5  ER Diagram                                                                                                             59
4.6  Modules of the Project                                                                                            60
4.7  Process Logic                                                                                                            62
4.8  User Interface Design                                                                                             63
4.9 Security Issues                                                                                                         67
5.1 Implementation Approaches                                                                                  68
5.2 Coding Details and Code Efficiency                                                                      69
5.1.2 Code efficiency                                                                                                   71
6.1 Test Reports                                                                                                           108
6.2 User Documentation                                                                                              115
7.1  Conclusion                                                                                                            116
7.2. Limitations of the System                                                                                     117
7.3. Future Scope of the Project                                                                          118
BIBLIOGRAPHY                                                                                                      119










1.3.1  PURPOSE

  1. The current manual system has a lot of paper work and it does not deal with new purchase and sale.
  1. To maintain the records of sale and service manually, is a Time-consuming job.
  1. With the increase in database, it will become a massive job to maintain the database.
  1. Requires large quantities of file cabinets, which are huge and require quite a bit of space in the office, which can be used for storing records of previously sale tyre.
  1. The retrieval of records of previously sold tyre will be a tedious job.
  1. Lack of security for the records, anyone disarrange the records of your system.
  1. If someone want to check the details of the available product for his satisfaction (like the details of the owner of the tyre) the previous system does not provide any necessary detail of this type.

1.3.2 Scope

  1. Problem of Reliability: Current system is not reliable. It seems to vary in from one month to the, next. Some times it gives quality good output, but some times the output is worst.
  2. Problem of Accuracy: There are too many mistakes in reports.
  3. Problem of timeliness: In the current system the reports and output produced is mostly late and in most of the cases it is useless because it is not on time.
  4. Problem of Validity: The output and reports mostly contains misleading information. The customer’s information is sometimes not valid.
  5. Problem of Economy: The current system is very costly. We have  to spend lots of money to keep the system up and going, but still not get the desired results.
  6. Problem of Capacity: The current system is suffering from problem of capacity also. The staff for organization is very less and the workload is too much. Few peoples cannot handle all the work

1.3.3 Applicability

  1. Details: The new proposed system stores and maintains all the details of the products,seekers,doctors etc..
  1. Registers: There is no need of keeping and maintaining database manually. It remembers each and every record and we can get any report related to products and customer at any time.
  1. Speed: The new proposed system is very fast with 100% accuracy and saves time.
  1. Manpower: The new proposed system needs less manpower. Less people can do the large work.
  1. Efficiency: The new proposed systems complete the work of many persons in less time.
  1. Past details: the new proposed system contains the details of every past user for future assistance.
  1. Reduces redundancy: The most important benefit of this system is that it reduces the redundancy of data within the data.
  1. Work load: Reduces the work load of the data store by helping in easy updates of the records and providing them with the necessary details together with database management system.



PHP: PHP is a dynamic and interactive server-side, object-oriented, open source scripting language. PHP is a language used to develop interactive and dynamic content on the web and it is often used together with the Apache web server. While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext Preprocessor. PHP code is interpreted by a web server with a PHP processor module which generates the resulting web page: PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. It has also evolved to include a command-line interface capability and can be used in standalone graphical applications. PHP is free software released under the PHP License, which is incompatible with the GNU General Public License (GPL) due to restrictions on the usage of the term PHP. PHP can be deployed on most web servers and also as a standalone shell on almost every operating system and platform, free of Varcharge.

HTML: Hyper Text Markup Language and Extensible markup Language are the predominant markup languages for web pages.It provides a means to describe the structure of text-based information in a document and to supplement that text with interactive forms, embedded images, and other objects.

MySQL: MySQL is the world’s most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It is named after co-founder Michael Widenius’ daughter, My. The SQL phrase stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation. MySQL is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other ‘AMP’ stacks). LAMP is an acronym for “Linux, Apache, MySQL, Perl/PHP/Python.” Free-software-open source projects that require a full-featured database management system often use MySQL.





  1. Problem of Reliability:
  1. Problem of Accuracy:
  1. Problem of timeliness:
  1. Problem of Validity:
  1. Problem of Economy:
  1. Problem of Capacity:


This Project is coupled with material on how to use the various tool, sub sets  available PHP and My Sql.

The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.


Requirement Specification

The main part of problem is to obtain a clear understanding of the needs of user and

what exactly are desired from the software. It is used for specifying the


Fact finding tools:

After obtaining the background knowledge, I began to collect data on the existing

system’s output, input, and costs. The tools used in data collection / information

gathering are:

Review of the written Documents

On-site  Observation




Review of the written documents:

In this phase we analyzed all the documents like the day books, supply report, order

generating  forms, supply forms, account etc. All these things describe the format

and functions of the current system included in most manuals are system

requirement that help  determine how III various objectives are met.

The form is one of the most important source through which ! draw some

conclusion like:

  1. Who use the form(s)? How important are they to the user?
  2.  Do the forms include all the necessary information? What item should be added or deleted?
  1. How readable and easy to follow is the form?
  2. How does the information in the form help other user make better decision?
  3. What other uses does the form offer the user area?

By analyzing all the details we draw a conclusion that what are the merit and De-

merit of the current phase. Will the company contain all the back up of all the

important document of not sales person contains all the information about the

available vehicles or not. But above all there are some problems with the on site

observations that one analyst must face during analysis like:

  1. Take long time and get inefficient result
  2. Attitude and motivation of subject cannot be readily observed
  3. Observation are subject to error
  4. In a complex situation it can be very time­ consuming

So for this we switched towards the other fact finding tools like interviews and



 Interviews and Questionnaires:

The interviews is a face to face interpersonal role situation in which a person called

The interview asks a person being interview questions designed to gather

information about a problem area. The interview is the oldest and most often used

device for gathering information in systems work. It has qualities that behavioral

and on-site observation do not possess .it can be used for two main purposes:

(a)      as an exploratory device to identify relations or verify Information

(b)      to capture information as it exists


  1. On site observation:

It is not the easy task to do. In the on site observation the main objective is to get close as possible to the real system that are being studied. There are some questions hat can serve as a guide for the on site observations:

  1. What kind of the system is it? What does it do?
  2. Who runs the system? Who are the important people in it?
  3. What is the history of the system? How it get to its present stage of the Development first in this phase we more likely listened than talk and to and to listen with a sympathetic and genuine interest when information is conveyed. We

have not to give any advice or passing moral judgment on what is observed. Not to

argue with anyone or not to show any hostility towards one person and undue friendliness towards another.

So in the on site observation we first visited to the entire organization watched all the transactions, watched the way of taking orders by the sales executive. What types of forms are used in the entire place? Are all forms are written, printed or not.

There are four primary advantages of the interviews:

  1. its flexibility
  2. easy to validate the information gathered
  3. effective technique for elicit information about complex subject
  4. instance, goals must be based on what competitors do.



It is usually associated with the self-administrated tools with items of the closed or fixed alternative type. By this nature a questionnaires offer the following advantages:

(a) It is economical and requires less skill to administer than the interview

(b) Unlike the interview which generally questions one subject at time questionnaire can be administrated to large number of individuals simultaneously.

(c) The questionnaires place less pressure on the subjects for immediate responses. Respondents have to think the question over and do calculations to provide more accurate data.


Mainly interviews and questionnaires are divided into two categories.

  1. The unstructured alternative
  2. The structured alternative

The unstructured interview is a relatively nondirective information technique. The role of the analyst as an interviewer is to encourage the respondent to talk freely and serve as a catalyst to the expression of feeling and opinions.

Following are the sample questions which we asked in the form of questionnaires and interviews:­


Samples Questions asked to Computer Operators


Samples Questions asked to Administrators



Sample Questions asked to consumers (Center’s customers)





Gantt Chart

Gantt charts mainly used to allocate resources to activities. The resources allocated to activities include staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful for resource planning. A Gantt chart is special type of bar chart where each bar represents an activity. The bars are drawn along a timeline. The length of each bar is proportional to the duration of the time planned for the corresponding activity.

Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by coloring each milestone when completed. The project will start in the month of August and end after 4 months at the end of November.       

PERT (Project Evaluation and Review Technique) charts consist of a network of boxes and arrows. The boxes represent activities and the arrows represent task dependencies.

PERT chart represents the statistical variations in the project estimates assuming a normal distribution. Thus in a PERT chart instead of making a single estimate for each task, pessimistic, likely, and optimistic estimates are also made. The boxes of PERT charts are usually annotated with the pessimistic, likely, and optimistic estimates for every task. Since all possible completion times between the minimum and maximum durations for every task have to be considered, there are many critical paths, depending on the permutations of the estimates for each task. This makes critical path analysis in PERT charts very complex. A critical path in a PERT chart is shown by using thicker arrows. The PERT chart representation of the ONLINE STUDY CENTER MANAGEMENT SYSTEM problem of Figure A. is shown in Figure B.


Specification Part 0 15 0 15 0
Design Database Part 15 60 15 60 0
Design GUI Part 15 45 90 120 75
Code Database Part 60 165 60 165 0
Code GUI Part 45 90 120 165 75
Integrate and Test 165 285 165 285 0
Write User Manual 15 75 225 285 210


PERT charts are a more sophisticated form of activity chart. In activity diagrams only the estimated task durations are represented. Since the actual durations might vary from the estimated durations, the utility of the activity diagrams is limited.





Processor                     :           Inter core 2 Duo or above

Memory                       :           2 GB RAM or above

Cache Memory            :           128 KB or above

Hard Disk                   :           30 GB or above [at least 3 MB free space required]

Printer                         :           Dot Matrix / DeskJet connected to LPT port



Operating System       :           Windows 7

Font-End Tool                        :           HTML, PHP

Back-End                    :           My Sql

Server                          :         Wamp Server


PHP, MY SQL programming tools are complete programming environments. It allows programmers to build a GUI program using the various on-screen controls such as buttons, text, menus, boxes etc. These controls are placed on a form and then the processing details related with each control are filled in.

In the business world, competitive strategies have become the order of the day to improve quality, cut costs and provide a high response customer service base. Most organizations today need to be market driven and do a lot of value addition to their products and services. This naturally calls for rational decision making, which requires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client/Server is the technology that empowers the desktop, thus setting a trend for the way successful organizations will use technology in the next decade.



PHP, MY SQL programming tools are complete programming environments. It allows programmers to build a GUI program using the various on-screen controls such as buttons, text, menus, boxes etc. These controls are placed on a form and then the processing details related with each control are filled in.

In the business world, competitive strategies have become the order of the day to improve quality, cut costs and provide a high response customer service base. Most organizations today need to be market driven and do a lot of value addition to their products and services. This naturally calls for rational decision making, which requires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client/Server is the technology that empowers the desktop, thus setting a trend for the way successful organizations will use technology in the next decade.

Introduction to Php, My Sql


MySQL™ and PHP are two of the most popular open source technologies to emerge during the past decade. PHP is a powerful language for writing server-side Web applications. MySQL is the world’s most popular open source database. Together, these two technologies provide you with a powerful platform for building database-driven Web applications.

This hands-on MySQL and PHP training course teaches attendees everything they need to successfully build data-driven Web sites using MySQL and PHP.



It’s very likely that the first task the administrator will want to undertake is proper configuration of MySQL’s configuration file. This file, entitled my.cnf, stores default startup options for both the server and for clients. Correct configuration of this file can go a long way towards optimizing MySQL, as various memory buffer settings and other valuable options can be set here.

Interestingly, the scope of this file can be set according to its location. The settings will be considered global to all MySQL servers if stored in /etc/my.cnf. It will be global to a specific server if located in the directory where the MySQL databases are stored (/usr/local/mysql/data for a binary installation, or /usr/local/var for a source installation). Finally, its scope could be limited to a specific user if located in the home directory of the MySQL user (~/.my.cnf). Keep in mind that even if MySQL does locate a my.cnf file in /etc/my.cnf (global to all MySQL servers on that machine), it will continue its search for a server-specific file, and then a user-specific file. You can think of the final configuration settings as being the result of the /etc/my.cnf, mysql-data-dir/my.cnf, and ~/.my.cnf files.

In order to aid administrator’s in the proper configuration of this file, the MySQL developers have included four sample my.cnf files within the distribution. Their names are my-huge.cnf.sh, my-large.cnf.sh, my-medium.cnf.sh, and my-small.cnf.sh, and each denotes recommended configuration settings in accordance with system resource availability.


Data Type


CHAR( ) A fixed section from 0 to 255 characters long.
VARCHAR( ) A variable section from 0 to 255 characters long.
TINYTEXT A string with a maximum length of 255 characters.
TEXT A string with a maximum length of 65535 characters.
BLOB A string with a maximum length of 65535 characters.
MEDIUMTEXT A string with a maximum length of 16777215 characters.
MEDIUMBLOB A string with a maximum length of 16777215 characters.
LONGTEXT A string with a maximum length of 4294967295 characters.
LONGBLOB A string with a maximum length of 4294967295 characters.

The ( ) brackets allow you to enter a maximum number of characters will be used in the column.


BLOB stands for Binary Large OBject. Both TEXT and BLOB are variable length types that store large amounts of data. They are similar to a larger version of VARCHAR. These types can store a large piece of data information, but they are also processed much slower.


TINYINT( ) -128 to 127 normal
0 to 255 UNSIGNED.
SMALLINT( ) -32768 to 32767 normal
0 to 65535 UNSIGNED.
MEDIUMINT( ) -8388608 to 8388607 normal
0 to 16777215 UNSIGNED.
INT( ) -2147483648 to 2147483647 normal
0 to 4294967295 UNSIGNED.
BIGINT( ) -9223372036854775808 to 9223372036854775807 normal
0 to 18446744073709551615 UNSIGNED.
FLOAT A small number with a floating decimal point.
DOUBLE( , ) A large number with a floating decimal point.
DECIMAL( , ) A DOUBLE stored as a string , allowing for a fixed decimal point.

The integer types have an extra option called UNSIGNED. Normally, the integer goes from an negative to positive value. Using an UNSIGNED command will move that range up so it starts at zero instead of a negative number.



ENUM ( ) Short for ENUMERATION which means that each column may have one of a specified possible values.
SET Similar to ENUM except each column may have more than one of the specified possible values.




The PHP IDE Project is a proposed open-source project under the Eclipse Tools Project. This document describes the content and the scope of the proposed project.

This proposal is in the Project Proposal Phase and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the


PHP started as an open source project about 10 years ago. During the last 10 years, PHP has gained significant momentum with now more than 23 million Web domains running PHP. PHP’s simplicity and low cost of ownership have all contributed to the fast and wide adoption of the language. PHP has now reached the point of maturity where organizations are seeking standard tools and solutions that will further facilitate application development with PHP.

Project Goal

The PHP IDE project will deliver a PHP Integrated Development Environment framework for the Eclipse platform. This project will encompass the development components necessary to develop PHP-based Web Applications and will facilitate extensibility. It will leverage the existing Web Tools Project in providing developers with PHP capabilities.

Project Scope

The project will contribute an initial set of Eclipse plug-ins that will add PHP IDE capabilities to Eclipse, and will provide APIs to further extend the functionality of the project. The project will be composed of a set of extensible features covering the development life cycle of PHP including functionality that deals with developing, deploying, documenting, debugging and testing PHP-based applications.

The next section describes in detail the design, features and extension points needed in order to provide a comprehensive IDE.

Project Description

Functional Requirements

The PHP IDE Project will include the following components:


The PHP IDE Core provides the infrastructure for the PHP IDE and includes:

  • PHP Language Model – provides infrastructure for the PHP language and the most popular extensions. This Core component is the basis of all PHP language classes, functions and constants and it will support both PHP 4 and PHP 5. The two PHP major versions support will affect the code assist, syntax coloring and PHP Functions view.
  • PHP Inspector / Code Builder – analyzes PHP language elements such as: classes, functions, constants, variables, include statements, PHPDoc blocks and errors. The PHP Inspector component is based on the PHP language Lexer and Parser and provides analysis for all PHP source code in either PHP 4 or PHP 5.
  • PHPDoc Support – provides infrastructure that helps overcome some of the PHP language complexities. It adds capabilities to the PHP Language model and the PHP Inspector.
  • PHP User Model – provides an API for navigating through PHP inspected data (PHP classes, functions, constants, variables and include statements). Used by the search engine, Code Assist and PHP Explorer View.
  • PHP Source Code Formatter – Format PHP code according to personal preferences. The tool works in tandem with the Web Tools Project formatter.


The PHP IDE UI provides the user interface for the PHP IDE. It includes several contributions to the Eclipse workbench:

  • PHP Editor –
  • PHP Outline View –
  • PHP specific –
  • Generic web view –
  • Project Outline View –
  • PHP Explorer View –
  • PHP Language View –
  • PHP Manual View –
  • The UI will also provide the following functionalities:
  • PHP Searching –
  • Open PHP Type Dialog –


Debug Perspective

Debug Preview


Extension Points

The following list is work in progress and will most likely expand as requirements are identified. The PHP IDE project will provide extension points to facilitate the extensibility of the project. The extensions points will provide the ability to

  • Extend the debug communication protocol, between the PHP IDE and the Web Server, with new messages. This will enable to increase the debugging capabilities with new features and functions.
  • Integrate additional PHP builders.
  • Extend the PHP data models by providing new data model that will reflect code assist and outline view.
  • Launch of a PHP project on any Web server.

In addition, the PHP IDE project will define several extension points to enhance the PHP Editor. The extensions points will provide the ability to

  • Add new folding structured (regions) for the PHP Editor (similar to org.eclipse.jdt.ui.foldingStructureProviders)
  • Enhance the PHP IDE with new text hover to the PHP Editor

The PHP IDE project will be built using several Eclipse Web Tools Platform (WTP) project components. The WTP provide generic, extensible and standards-based tools for Web-centric application development. It provides editors for various Web centric languages such as: HTML, CSS, JavaScript, WSDL, etc. In addition, WTP provides facilities for configuring and connecting to Web Servers. The PHP IDE will use the WTP Server facilities to manage and configure Web Servers. PHP IDE project will benefit from the client web development support, already available in the WTP (HTML, CSS, etc) and will add the server side web development support (PHP). The integration between the PHP IDE and WTP will provide the PHP IDE’s users with a comprehensive solution for WEB development.

Main plug-ins:

  • PHP Editor, will extend the WTP’s Structure Editor. The Editor will add PHP support to the Structured Editor using PHP Lexical Analyzer for the PHP language. The use of the WTP’s Structure Editor as a baseline for the extended functionality will provide the PHP developer with the benefits and capabilities that are already available with the WTP editor.
  • Debugger – The debugger communication protocol between the IDE and the server side in the PHP IDE will be based on Zend’s proven debugging protocol. This protocol defines the agreed-upon format for transmitting data between both the server and the client side in order to facilitate debugging of a PHP application. The debug protocol will support PHP web server debugging and PHP stand-alone application debugging. Debug initiation will be done through an HTTP request made to the debugger server side, then the debugger server will open a communication channel to the PHP IDE to start debugging communication.
  • Inspection – The PHP IDE will make use of an existing Zend inspection model and tool for parsing PHP code. The PHP parser establishes a model constructed by file data for each of the project files. Each file’s data includes: classes, functions, constants, errors and include file data. The model is used for Code Assist, Outline View, Project Outline View and PHP Explorer View. The model is updated while you type in the editor and for every change in the PHP Project’s structure.

Code contributions

Zend and IBM will be making an initial code contribution that will encompass the core functionality for the PHP project including:

  • High-quality and proven PHP model infrastructure incl. editor, syntax highlighting, code completion, and PHP explorer
  • PHP perspectives
  • PHP debugging capabilities

Development Plan

We plan to have an initial prototype version available by the end of Q1/2006. After the availability of the initial version we will work on incorporating changes and feedback as needed and strive to release the first functional version as early as possible.

3.5 Conceptual Models








  • Flexible –
  • Maintainable –
  • Portable
  • Easy to use –
  • Reliable





4.2.1 Design Methodology:



4.2.2. Design Overview:


4.2.3 Process Modeling:



DFDs are built utilizing four noteworthy parts:

  • External elements –
  • Data stores –
  • Processes –

Process names are by and large unambiguous and pass on however much importance as could reasonably be expected without being too long. Case: check data, obtained time plan and so on.


Data flows – speaks to the development of data between different parts.




Data Structure   Requirements according to the modules:

  • Identify The Various Tables Required.
  • Fields for These Tables.
  • The Various Key Fields (for example Primary key and foreign key).
  • Identify The Various Constraints like Not Null, Unique etc.


Describing Data Elements:

Each entry in the data dictionary consists of a set of details describing the data used or produced in the system.  Each item is identified by a data name, description, alias, and length  and  has  specific  values  that  are  permissible  for  it  in  the  system  being studied.


  1. Admin
  2. Student Table
  1. Feedback
  1. Question
  1. Registration
  1. Topic
  1. Tutorial
  1. Answer
  1. Quiz
  1. Results
  1. Notes
  1. Department
  1. Fee
  1. Course table



Admin Table

Primary Key
VarVarchar (50)
Not Null
Not Null
VarVarchar (50)
Not Null
VarVarchar (1)

Student Details Table

Field Name
Data Type Constraint
Enrollment_No. Character(20) Primary Key
Student_Name Character(20) Not Null
Father_Name Character(20) Not Null
Date_of_Birth Date Not Null
Address Character(30) Not Null
Telephone_No. Number Not Null

Attendance Details Table

Field Name
Type Constraint
Student_Roll_No. Character(25) Primary Key
Course_Name Character(25) Not Null
Month Character(20) Not Null
Date_of_Joining Date Not Null
Total_Classes Number Not Null
Class_Attendance Character(25) Not Null

Courses Table

Field Name
Type Constraint
Student_Name Character(30) Primary Key
Student_Roll_No. Number Not Null
Course_Name Character(30) Not Null
Start_Date_of_Course Date Not Null
Time_Slot_Theory Character(25) Not Null
Time_Slot_Lab Character(25) Not Null
Days_of_Theory Character(20) Not Null
Days_of_Lab Character(20) Not Null

 Feedback Table

Field Name
Primary Key
VarVarchar (50)
Not Null
VarVarchar (50)
Not Null
Varchar (450)
Not Null

 Question Table

Field Type Constraint
ID Number(10) Primary Key
Question no Varchar (50) Not Null
Name Varchar (50) Not Null
Email Varchar (50) Not Null
Question Varchar (50) Not Null

 Registration Table

Field Type Constraint
ID Number(10) Primary Key
Email id Varchar (50) Not Null
Password Varchar (50) Not Null
Secret Question Varchar (50) Not Null
Secret Answer Varchar (50) Not Null
First Name Varchar (50) Not Null
Last Name Varchar (50) Not Null

Topic  Table

Field Type Constraint
ID Number(10) Primary Key
Topic Name Varchar (50) Not Null
Summery Varchar (510) Not Null
Files Varchar (50) Not Null

Tutorial Table

Field Type Constraint
ID Number(10) Primary Key
Topic Name Varchar (50) Not Null
Heading Varchar (50) Not Null
Detail Varchar (30) Not Null
Files Varchar (50) Not Null

 Answer Table

Field Type Constraint
ID Number(10) Primary Key
Ans_no Number (10) Not Null
repname Varchar (50) Not Null
Repemail Varchar (50) Not Null
Answer Varchar (250) Not Null
Q.no Varchar (50) Not Null
Askname Varchar (50) Not Null
Askemail Varchar(50) Not Null
Question Varchar (100) Not Null

Quiz Table

Field Type Constraint
ID Number(10) Primary Key
Date Varchar (50) Not Null
Time Varchar (50) Not Null
Score Varchar (50) Not Null
Topic Varchar (50) Not Null

Result Table

Field Type Constraint
ID Number(10) Primary Key
Student Id Number (10) Not Null
Class Varchar (50) Not Null
Section Varchar (50) Not Null
Marks Varchar (50) Not Null
Max_Marks Varchar (50) Not Null


Field Type Constraint
ID Number(10) Primary Key
Teacher_ID Number(10) Not Null
Title Varchar (50) Not Null
Subject_Name Varchar (50) Not Null
Remarks Varchar (50) Not Null


Field Type Constraint
Department_ID Number(10) Primary Key
Department_Name Varchar (50) Not Null


Field Type Constraint
ID Number(10) Primary Key
Student_ID Number(10) Not Null
Class Varchar (50) Not Null
Date Timestamp Not Null
Amount Currency Not Null
Remarks Varchar (50) Not Null

Course Table

Field Type Constraint
ID Number(10) Primary Key
Course_Name Varchar (10) Not Null
Duration Varchar (50) Not Null
Remarks Varchar (50) Not Null


4.5 ER Diagram



MODULE 1: User Authentication Module

MODULE 2: A New Records Being Entered

MODULE 3: Deleting or Updating the Records

MODULE 4: Tutorials 

MODULE 5: Topics

MODULE 6: Forums

MODULE 7: Searching

MODULE 8: Admin

MODULE 9: Validation of Data Entered by the User & Error Handling

MODULE 10: Feedback





Record Entry

Editing the records:

Deleting the Records:







In this project we have used following validation checks.

  • While entering the data into the form it will check for the nullity of the fields in both of client machine and server.
  • While entering the data the validation will be checking the existing records, if the records found a message will be fired to the end user as “The record already exists”.
  • The students are being granted with access only to the study materials of courses for which student is registered.
  • Passwords are encrypted using PHP before storing the data into the database. And it will be decrypted and authenticated while login into the system.






The different types of testing are as follows


  1. Unit Testing:



  1. Integration Testing:



  1. System Testing:

System testing consists of the following steps:

  1. Program(s) testing.
  2. String testing.
  3. System testing.
  4. System documentation.
  5. User acceptance testing.


  1. Field Testing:


  1. Acceptance Testing:



Reviewing of Code efficiency for a module is carried out after the module is successfully compiled and all the syntax errors eliminated. Code efficiency review is extremely cost-effective strategies for reduction in coding errors in order to produce high quality code. Normally, two types of efficiency are carried out on the code of a module –  code optimization and code inspection. The procedure and final objective of these two efficiency techniques are very different as discussed below.





























The objectives of verification, validity activities are to assess and improve the quality of the work products generated during development and modification of the software. Quality depends upon the various attributes like correctness, completeness, consistency, reliability, usefulness, usability, efficiency and conformance to standards.

The terms verification and validation are used synonymously.  These are defined as under: –

Verification: “Are we building the product right?”

Validation: “Are we building the right product?”











The deliverable product is named as “Online Study Center Management System”.

I have designed the given proposed Website in the PHP to automate the educational department.

The complete set of rules & procedures related to educational administrative department day to day activities and generating report is called Online Study Center Management System”. My project gives a brief idea regarding automated educational department activities.