Scribd
Upload
34 views

CMS Report

Uploaded by

2O556 Ritika Sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
34 views

CMS Report

Uploaded by

2O556 Ritika Sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 66

1.

INTRODUCTION

1
1) PROJECT OVERVIEW:-

A college management system is a comprehensive software solution designed to streamline


and automate various administrative and academic processes within an educational
institution. It plays a crucial role in enhancing efficiency, reducing manual workloads, and
improving overall organizational effectiveness. Here's a detailed report on the key
components, benefits, a features of a college management system.

College Management Systems Plays an essential role in the current educational system.
College authorities all over the world are engaged in a lot of day-to-day administrative and
academic activities to manage and provide a better academic experience to students
effectively. However, maintaining and keeping track of college administrative activities is not
an easy process in the fast-growing world. It requires hard work and often it is time-
consuming. To better perform the college administrative activities of educational institute and
to assure parents the real-time progress and security of their children, educational institutes
utilizes College Management software nowadays. Such applications often offer many
features that help to enhance the performance of college with minimum efforts. College
Management software does it by avoiding the manual paper works and automation of many
academic and administrative activities.

College management solutions are web and mobile-based applications with centralized data
storage structures that make it easier for administrators, students, teachers, and parents to
access data from iPhone and Android devices.

2
2.
OBJECTIVE

3
Objective:

The objective of a College Management System (CMS) project is to streamline and automate
various administrative and academic processes within an educational institution. The primary
goal is to enhance efficiency, transparency, and effectiveness in managing the day-to-day
operations of a school. Here are some key objectives of a College Management System
project.

1. Automation of Administrative Tasks: Implementing automation for tasks such as


student admissions, attendance tracking, timetable scheduling, and examination
management helps

2. Reduce manual effort and minimizes the chances of errors.

3. Student Information Management: Create a centralized database for student


information, including personal details, academic records, attendance, and disciplinary
history. This ensures easy access to accurate and up-to-date information.

4. Staff Management: Manage information related to teaching and non-teaching staff,


including their personal details, qualifications, and attendance. This facilitates efficient
staff allocation and payroll processing.

5. Grading and Examination Management: Streamline the process of conducting


examinations, grading, and result management. This includes generating report cards
and transcripts automatically based on the recorded grades.

6. Communication and Collaboration: Facilitate communication between teachers,


students, and parents. This can include features such as messaging, notifications, and
access to academic progress reports

7. Timetable Management: Generate class timetables efficiently, taking into


consideration teacher availability, classroom availability, and other scheduling
constraints.

8. User-Friendly Interface: Develop a user-friendly interface that is easy to navigate for


administrators, teachers, students, and parents. This contributes to widespread adoption
and effective use of the system.

4
2.1) TECHNOLOGIES USED IN PROJECT

What is HTML?

 HTML stands for Hyper Text Markup Language


 HTML is the standard markup language for creating Web pages
 HTML describes the structure of a Web page
 HTML consists of a series of elements
 HTML elements tell the browser how to display the content
 HTML elements label pieces of content such as “this is a heading”, “this is a
paragraph”, “this is a link”, etc.

Example Explained

 The <!DOCTYPE html> declaration defines that this document is an HTML5


document.
 The <html> element is the root element of an HTML page.
 The <head> element contains meta information about the HTML page.
 The <title> element specifies a title for the HTML page (which is shown in the
browser’s title bar or in the page’s tab).
 The <body> element defines the document’s body, and is a container for all the
visible contents, such as headings, paragraphs, images, hyperlinks, tables, lists, etc.
 The <h1> element defines a large heading.
 The <p> element defines a paragraph.

What is CSS?

 CSS stands for Cascading Style Sheets.


 CSS describes how HTML elements are to be displayed on screen, paper, or in other
media.

 CSS saves a lot of work. It can control the layout of multiple web pages all at once.
 External style sheets are stored in CSS files.

5
Why CSS?

CSS saves time: You can write CSS once and reuse the same sheet in multiple HTML pages.

Easy Maintenance: To make a global change simply change the style, and all elements in all
the Web pages will be updated automatically.

Search Engines: CSS is considered a clean coding technique, which means search engines
won’t have to struggle to “read” its content.

Superior styles to HTML: CSS have a much wider array of attributes than HTML, so you
can give a far better look to your HTML page in comparison to HTML attributes.

Offline Browsing: CSS can store web applications locally with the help of an offline cache.

Using this we can view offline websites.

What is PHP?

PHP is an acronym for "PHP: Hypertext Preprocessor"

PHP is a widely-used, open source scripting language

PHP scripts are executed on the server

PHP is free to download and use

PHP files can contain text, HTML, CSS, JavaScript, and PHP code

PHP code is executed on the server, and the result is returned to the browser as plain HTML

PHP files have extension ".php".

6
Why PHP?

PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)

PHP is compatible with almost all servers used today (Apache, IIS, etc.)

PHP supports a wide range of databases

PHP is free. Download it from the official PHP resource: www.php.net

PHP is easy to learn and runs efficiently on the server side

7
3.

SYSTEM ANALYSIS &


SYSTEM DESIGN

8
3) SYSTEM ANALYSIS

System analysis is a process of gathering and interpreting fact, diagnosing problem and the
information about the Dental Clinic management system to recommend improvement on the
system. It is a problem solving activity that requires intensive communication between the
system user and system developers. System analysis or study is an important phase of any
system development process. The system is studied to the minutest detail and analyzed. The
system analyst plays the role of the interrogator and dwells deep into the working of the
present system. The system is viewed as a whole and the input to the system are identified.
The output from the organization are traced to the various processes

System analysis phase is divided into many sub-phases to make analysis is work easy. This
phase is not easy phase, but very cumbersome and complex. This phase of SDLC is tricky
and time consuming also

a) System study: The system study is information-oriented stage in which user; middle level
and higher-level management have to face interviews.

b) Requirement analysis: The user expectation whit new or candidate system is called user
requirement. The requirement can be qualitative and quantitative

c) Documentation : The report of system study and requirement analysis is studied and
documented. Designer team for system designing user this document. If document dose not
contain appropriate information , design cannot be successful

9
3.1) IDENTIFICATION OF NEED

The old manual system was suffering from a series of drawbacks. Since whole of the
system was to be maintained with hands the process of keeping, maintaining and retrieving
the information was very tedious and lengthy. The records were never used to be in a
systematic order. there used to be lots of difficulties in associating any particular transaction
with a particular context. If any information was to be found it was required to go through the
different registers, documents there would never exist anything like report generation. There
would always be unnecessary consumption of time while entering records and retrieving
records. One more problem was that it was very difficult to find errors while entering the
records. Once the records were entered it was very difficult to update these records. The
reason behind it is that there is lot of information to be maintained and have to be kept in
mind while running the business .For this reason we have provided features Present system is
partially automated (computerized), actually existing system is quite laborious as one has to
enter same information at three different places.

10
3.2) Preliminary Investigation

Preliminary Investigation basically refers to the collection of information that guides the
management of an organization to evaluate the merits and demerits of the project request and
make an informed judgment about the feasibility of the proposed system. This sort of
investigation provides us with a through picture of the kind of software and hardware
requirements which are most feasible for the system, plus the environment in which the entire
project has to be installed and made operational.

1) Reviewing the documents provided by the organization

They were quite effective in guiding us towards visualizing the features that were needed to
be put together in the system and the required output which had to be generated once the
system became functional.

These specifications provided to us by the organization showed how the new system should
look like; it helped us in understanding the basic structure of the application which we were
supposed to develop.

2) On site observation

Another technique utilized by us to gain information about the project was to visit the client
site where the system had to be installed. Here a detailed system study was carried out,
checking the existing system to replicate it with our system. We also observed the activities
of the system directly. During the on-site observation, we saw the office environment, work
load of the system and users, method of work, and the facilities provided by the organization.
This information helped us to understand how the system should operate. But after
interviewing the persons, who is affected by the system, we got more details that further
explain the project and shown whether assistance is merited economically, operationally and
technically.

3) Conducting interviews

This method of investigation conducted by us involved questioning the concerned personnel


to get the user’s (client) view about the system and the features they desired it to have. Some
of the Questions put forward by our team were:

a) The amount of data needed to be stored. b) The number of customers using the system.

c) number of which the application needed to be installed.

11
3.3) FEASIBILITY STUDY

After doing the project School Management System, study and analyzing all the existing or
required functionalities of the system, the next task is to do the feasibility study for the
project. All projects are feasible - given unlimited resources and infinite time. Feasibility
study includes consideration of all the possible ways to provide a solution to the given
problem. The proposed solution should satisfy all the user requirements and should be
flexible enough so that future changes can be easily done based on the future upcoming
requirements.

. A) Economical Feasibility:- This is a very important aspect to be considered while


developing a project. We decided the technology based on minimum possible cost factor.

 All hardware and software cost has to be borne by the organization.


 Overall we have estimated that the benefits the organization is going to receive from
the proposed system will surely overcome the initial costs and the later on running
costforsystem

B) Technical Feasibility:- This included the study of function, performance and


constraints that may affect the ability to achieve an acceptable system. For this feasibility
study, we studied complete functionality to be provided in the system, as described in the
System Requirement Specification (SRS).

C) Operational Feasibility:- No doubt the proposed system is fully GUI based that is
very user friendly and all inputs to be taken all self-explanatory even to a layman.
Besides, a proper training has been conducted to let know the essence of the system to the
users so that they feel comfortable with new system. As far our study is concerned the
clients are comfortable and happy as the system has cut down their loads and doing.

12
3.4) PROJECT PLANNING

Software project plan can be viewed as the following:

1) Within the organization: How the project is to be implemented? What are various
constraints (time, cost, staff )? What is market strategy?

2) With respect to the customer: Weekly or timely meetings with the customer with
presentation on status reports. Customers feedback is also taken and further modification and
developments are done. Project milestones and deliverables are also presented to the
customer.

For a successful software project, the following steps can be followed:

 Select a project
 Identifying project’s aims and objectives
 Understanding requirements and specification
 Methods of analysis, design and implementation
 Testing techniques
 Documentation

 Project Estimates
 Cost
 Time
 Size of code
 Duration
 Resource Allocation
 Hardware
 Software
 Previous relevant project information
 Digital Library
 Risk Management
 Risk avoidance
 Risk detection

13
3.5) Project Scheduling (Gantt/Pert chart)

Everyone knows what a schedule is, at least anyone who has had to get anything done on
time. But when it comes to creating a project schedule, well, that’s something few have deep
experience with.

What and who is being scheduled, and for what purposes, and where is this scheduling taking
place, anyway?

A project is made up of many tasks, and each task is given a start and end (or due date), so it
can be completed on time. Likewise, people have different schedules, and their availability
and vacation or leave dates need to be documented in order to successfully plan those tasks.

Whereas people in the past might have printed calendars on a shared wall in the water-cooler
room, or shared spreadsheets via email, today most teams use online project scheduling tools.
Typically, project scheduling is just one feature within a larger project management software
solution, and there are many different places in the software where scheduling takes place.

For example, most tools have task lists, which enable the manager to schedule multiple tasks,
their due dates, sometimes the planned effort against that task, and then assign that task to a
person. The software might also have resource scheduling, basically the ability to schedule
the team’s availability, but also the availability of non-human resources like machines or
buildings or meeting rooms.

Because projects have so many moving parts, and are frequently changing, project
scheduling software automatically updates tasks that are dependent on one another, when one
scheduled task is not completed on time. It also generates automated email alerts, so team
members know when their scheduled tasks are due or overdue, and to let the manager know
when someone’s availability has changed.

Project scheduling is simple when managed online, thankfully, especially since the software
does all the hard part for you!

14
3.5.1 How to schedule a project

Project scheduling occurs during the planning phase of the project. You have to ask yourself
three questions to start:
1. What needs to be done?
2. When will it be done?
3. Who will do it?
Once you’ve got answers to these questions, then you can begin to plan dates, link activities,
set the duration, milestones and resources. The following are the steps needed to schedule a
project:

1. Define activities

What are the activities that you have to do in the project? By using a Work Breakdown
Structure (WBS) and a deliverables diagram, you can begin to take these activities and
organize them by mapping out the tasks necessary to complete them in an order than makes
sense.

2. Do estimates

Now that you have the activities defined and broken down into tasks, you next have to
determine the time and effort it will take to complete them. This is an essential piece of the
equation in order to calculate the correct schedule.
3. Determine dependencies

Tasks are not an island, and often one cannot be started until the other is completed. That’s
called a task dependency, and your schedule is going to have to reflect these linked tasks.
One way to do this is by putting a bit of slack in your schedule to accommodate these related
tasks.

4. Assign resources

The last step to finalizing your planned schedule is to decide on what resources you are going
to need to get those tasks done on time. You’re going to have to assemble a team, and their
time will need to be scheduled just like the tasks.

15
3.5.2. PERT chart

A PERT chart is a project management tool that provides a graphical representation of a


project's timeline. PERT, or Program Evaluation Review Technique, allows the tasks in a
particular project to be analyzed.

16
3.5.3. Gantt chart

A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. On the left of the chart is
a list of the activities and along the top is a suitable time scale. Each activity is represented by
a bar; the position and length of the bar reflects the start date, duration and end date of the
activity.

Task Name Start Date End Date Duration

Planning 27 July 28July 2days

Analysis 29 July 31 July 3days

Design 1 August 3August 3days

Coding 4August 22August 20days

Unit testing 23August 2September 10days

Integration Testing 3September 9September 7days

17
3.6) Software Requirement Analysis

This project is a web application that is developed in PHP having MySqli as back end.

 Database design:- MySqli


 Website design:- CSS
 Server:-XAMPP
 Coding(logic):- PHP and HTML
 Platform:- Windows
 Application:-VS CODE

3.6.1. Software Requirement on Server side

a. MySQL

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include
dBase, paradox, IMS, SQL Server and MySQL Server. These systems allow users to
create, update and extract information from their database. A database is a structured
collection of data. Data refers to the characteristics of people, things and events.
MySQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single
complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record
can have the same field name.

During an MySQL Server Database design project, the analysis of your business
needs identifies all the fields or attributes of interest. If your business needs change
over time, you define any additional fields or change the definition of existing fi elds.

b. Apache Server

Often referred to as simply Apache, a public-domain open source web server


developed by aloosely-knit group of programmers. The first version of Apache, based
on the NCSA httpd web server, was developed in 1995.Core development of the
Apache web server is performed by a group of about 20 volunteer programmers,

18
called the Apache group. However, because the source code is freely available,
anyone can adapt the server for specific needs, and there is a large public library of
Apache Add-ons. In many respects, development of Apache is similar to
development of the Linux Operating System.

3.6.2 Software requirement for development

a) XAMPP:-

XAMPP is a free and open source cross-platform web server developed by Apache
Friends. XAMPP stands for Cross-Platform (X), Apache (A), MariaDB (M), PHP (P) and
Perl (P). It is a simple, lightweight Apache distribution that makes it extremely easy for
developers to create a local web server for testing purposes. Everything needed to set up a
web server – server application (Apache), database (MariaDB), and scripting language
(PHP) – is included in an extractable file. XAMPP is also cross-platform, which means it
works equally well on Linux, Mac and Windows.

b) CSS:-

CSS stands for Cascading Style Sheets. CSS describes how HTML elements are to be
displayed on screen, paper, or in other media.CSS saves a lot of work. It can control the
layout of multiple web pages all at once. External style sheets are stored in CSS files.

C) HTML:-

HTML stands for Hyper Text Markup Language.HTML is the standard markup language for
creating Web pages.HTML describes the structure of a Web page.HTML consists of a series
of elements.HTML elements tell the browser how to display the content

d) PHP:-

PHP is an acronym for "PHP: Hypertext Preprocessor.PHP is a widely-used, open source


scripting language.PHP scripts are executed on the server.PHP is free to download and use

19
3.6.3. Hardware and software recruitment
 SOFTWARE REQUIREMENTS:-
 HTML V5.0
 CSS V3.0
 php
 WINDOW 10
 Visual Studio Code
 Xampp server

 HARDWARE REQUIREMENT:-
 i3,AMD Ryzen 3 or above
 4GB RAM or above
 20GB Hard Disk or above
 Other hardware
 Keyboard
 CD-ROM
 Android mobile phone
 Data cable

20
3.7) DATA FLOW DIAGRAM

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
Information System. A data flow diagram can also be used for the visualization of Data
Processing. It is common practice for a designer to draw a context-level DFD first which
shows the interaction between the system and outside entities. This context-level DFD is then
"exploded" to show more detail of the system being modeled

A DFD represents flow of data through a system. Data flow diagrams are commonly used
during problem analysis. It views a system as a function that transforms the input into desired
output. A DFD shows movement of data through the different transformations or processes in
the system.

Dataflow diagrams can be used to provide the end user with a physical idea of where the data
they input ultimately has an effect upon the structure of the whole system from order to
dispatch to restock how any system is developed can be determined through a dataflow
diagram. The appropriate register saved in database and maintained by appropriate authorities

Data Flow Diagram Notation

Function/Process

File/Database

Input/output

Flow

21
There are seven rules for construct a data flow diagram.

i. Arrows should not cross each other.


ii. Squares, circles and files must wears names.
iii. Decomposed data flows must be balanced.
iv. No two data flows, squares or circles can be the same names.
v. Draw all data flows around the outside of the diagram.
vi. Choose meaningful names for data flows, processes & data stores.
vii. Control information such as record units, password and validation requirements are
not penitent to a data flow diagram.

Fig.1 Data flow diagram of college management system

22
3.8 ER-Diagram

An entity-relationship diagram (ERD) is a data modeling technique that creates a graphical


representation of the entities, and the relationships between entities, within an information
system.

The three main components of an ERD are:

1. The entity is a person, object, place or event for which data is collected. The entity is
represented by a rectangle and labelled with a singular noun.
2. The relationship is the interaction between the entities. A relationship may be
represented by a diamond shape, or more simply, by the line connecting the entities.
3. The cardinality defines the relationship between the entities in terms of numbers. The
three main cardinal relationships are: one-to-one, expressed as 1:1; one-to-many,
expressed as 1: M; and many-to-many, expressed as M: N

3.8.1. Symbols Used In ER Diagram

Following are the various symbols used in the Entity Relationship Diagram:-

Description Represents Symbols Representation

Rectangle Entity Set

Ellipse Attributes

Diamond Relationship Set

23
Arrows Link Attributes To
Entity Set

ba
bsc
ec
bcom

Fig.2 ER-Diagram of college management system

24
3.9 Control Flow diagram

A Process flow diagram depicts components and their relationships of any system.
Commonly used as a step-by-step guide, which makes flowchart look like a chain.

Fig.3 Control flow diagram of college management system

25
4.
System Design

26
4. System Design

System design, or "modularity in design", is a design approach that subdivides a system into
smaller parts called modules or skids, that can be independently created and then used in
different systems. A modular system can be characterized by functional partitioning into
discrete scalable, reusable modules; rigorous use of well-defined modular interfaces; and
making use of industry standards for interfaces.

Besides reduction in cost (due to less customization, and shorter learning time), and
flexibility in design, modularity offers other benefits such as augmentation (adding new
solution by merely plugging in a new module), and exclusion. Examples of modular systems
are cars , computers , process systems etc.

Back End Modules: - Admin Module

Front End Modules: - User Module

27
Admin Module:

Admin of website can login and help the Users. It can manage site content. Admin can edit,
delete Pages and Comments. It also manages users of website. Admin can approve or un -
approve the

User Module:

User can login on this Easy to communicate between developers who are working on
applications. User can share information between a group and solve issues. Updates of
completed and pending tasks can be analyzed. A user can also give feedback.

28
4.2 Database Design

Database: In below diagram show the list of all tables that are use in college management
system project.

 Information BA

 Information BCOM

29
 Information BSC

 Login table

30
 Marks BA

 Marks BCOM

 Marks BSC

31
 TEMP

4.3 User Interface Design

Home page:

this is first page of our website. It is contain home page, about us ,admin login, student login,
gallery and contact us.

32
About us:-

Gallery:-

33
Contact us

LOGIN:-(Admin login)

34
When admin click insert then goes to this page(registration page).

35
When admin click marks then goes to this page(marks page).

Login(student login):-

36
37
4.4 Test Cases

A test case is a set of conditions or variables under which a tester will determine whether a
system under test satisfies requirements or works correctly. The process of developing test
cases can also help find problems in the requirements or design of an application.

A test case is a document, which has a set of test data, preconditions, expected results and
post conditions, developed for a particular test scenario in order to verify compliance against
a specific requirement.

Test Case acts as the starting point for the test execution, and after applying a set of input
values; the application has a definitive outcome and leaves the system at some end point or
also known as execution post condition.

A Test Case is a set of actions executed to verify a particular feature or functionality of your
software application.

Now, consider the Test Scenario Check Login Functionality there many possible cases like

Test Case 1: Check results on entering valid User Id & Password

Test Case 2: Check results on entering Invalid User ID & Password

Test Case 3: Check response when User ID is Empty & Login Button is pressed, and many
more

38
4.4.1. Unit testing

Soon after the program is corrected for syntax errors, the program has to be checked for
logical errors, at the unit level. Programs may have simple user inputs or outputs thru screens
or reports. The inputs must be validated for their format, data type, boundary conditions etc.
Also, the elementary functionality of the program must be verified. In most of the cases, the
programmers themselves will do this unit test.

4.4.2. System testing

After all the interfaces are tested between multiple modules, the whole set of software is
tested to establish that all modules work together correctly as an application or system or
package. This is again performed by independent testes. The testers will have to do the
system testing as though they are the end users of the application. Systems Testing includes
special testing methods like.

39
5.
CODING

40
CODING (INDEX PAGE)

<html>

<head>
<title> college management system</title>
<link rel="stylesheet" href="style.css">
<link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-
awesome/6.4.2/css/fontawesome.min.css"
integrity="sha512-
siarrzI1u3pCqFG2LEzi87McrBmq6Tp7juVsdmGY1Dr8Saw+ZBAzDzrGwX3vgxX1Nkio
YNCFOVC0GpDPss10zQ=="
crossorigin="anonymous" referrerpolicy="no-referrer" />
<link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-
awesome/5.14.0/css/all.css">
</head>

<body>

<header>
<nav>
<div class="logo">
<p>college</p>
</div>
<ul>
<li><a href="home.html">home</a></li>
<li><a href="about.html">about us</a></li>
<li><a href="#">login</a>
<ul>
<li><a href="../college/admin/login1.html">
admin login</a></li>
<li><a href="../college/student/login.html">
student login</a></li>
</ul>
</li>
<li><a href="#">gallary</a>
<ul>
<li><a href="image.html">photos</a></li>
<li><a href="video.html">videos</a></li>
</ul>

41
</li>
<li><a href="contactus.html">contact us</a></li>
</ul>
</nav>
</header>
<div class="content-item">
<img src="image/classroom.jpg">

<div class="content">
<h1>college <span>management</span></h1><br>
<a href="student/login.php">login</a>

</div>

</div>
<hr size="8" color="orange"><br>

<center>
<div class="banner">

<div class="container">

<h2>ABOUT US </h2>

</div>

</div>
</center>
<hr size="8" color="orange"><br>

<div class="about">
<div class="container2">
<div class="text" style="max-width: 100%;">

<h1> welcome to college</h1>


<center>
<hr size="8" color="orange" width="30%"><br><br>
</center>
<div class="col-md-5 pic">
<center>
<a href="image/g4.jpg"> <img
src="image/g4.jpg" height="30px" width="40%"></a>
42
<img src="image/g3.jpg" width="40%"
height="30px">
</center>
</div>
<div class="abt-info-pic">
<center>
<h4 class="mb-4"><b>Tempor libero doloremque
nam sunt neque ipsum accusamus magnablanditiis similique
tempore</b></h4> <p>Lorem ipsum dolor, sit amet consectetur
adipisicing elit. Velit modi nesciunt illum libero doloremque
<br>nam sunt neque ipsum accusamus magnam blanditiis similique
tempore, minima dolorem veniam, <br>laboriosam praesentium eius
incidunt! Lorem ipsum dolor sit, amet consectetur adipisicing elit.
</p>
</center>
<br>
<p></p>
</div>
</div>
</div>
</div>
</div>
<center>
<div class="banner">

<div class="container">

<h2>CONTACT US</h2>

</div>

</div>
</center>
<center>
<div class="cont">
<div class="row1">
<div class="col">
<div class="inner">
<i class="fa fa-map-marker"></i>
<h3 class="text1">OUR college</h3>
<span>street 123,himachal
pardesh,INDIA</span>

43
</div>
</div>
<div class="col">
<div class="inner">
<i class="fa fa-envelope"></i>
<h3 class="text1">EMAIL</h3>
<span>[email protected]</span>
</div>
</div>
<div class="col">
<div class="inner">
<i class="fa fa-phone"></i>
<h3 class="text1"> MOBILE NO.</h3>
<span>+91 7804536720</span>
</div>
</div>
</div>
</div>

</center>

<footer class="footer">
<div class="container1">
<div class="row">
<div class="footer-col">
<h4>school</h4>
<ul>
<li><a href="#">home</a></li>
<li><a href="#">about us</a></li>
<li><a href="#">admin</a></li>
<li><a href="#">student</a></li>
<li><a href="#">gallary</a></li>
<li><a href="#">contact us</a></li>
</ul>
</div>
<div class="footer-col">
<h4>get help</h4>
<ul>
<li><a href="#">FAQ</a></li>
<li><a href="#">searching</a></li>
<li><a href="#"> returns</a></li>
<li><a href="#">register stauts</a></li>

44
<li><a href="#">college search</a></li>
<li><a href="#">contact us</a></li>
</ul>
</div>
<div class="footer-col">
<h4>online register</h4>
<ul>
<li><a href="#">online register</a></li>
<li><a href="#">online login</a></li>
<li><a href="#">online checking</a></li>

</ul>
</div>
<div class="footer-col">
<h4>follow us</h4>
<div class="social-links">
<a href="#"><i class="fab fa-
facebook"></i></a>
<a href="#"><i class="fab fa-
instagram"></i></a>
<a href="#"><i class="fab fa-
linkedin"></i></a>
<a href="#"><i class="fab fa-
twitter"></i></a>
<a href="#"><i class="fab fa-
youtube"></i></a>

</div>
</div>

</div>
</div>
</footer>
</body>
</html>

45
CODEING (DATABASE CONNECTIVITY)

<?php

$servername = "localhost";
$username = "root";
$password = "";
#create connection
$conn = new mysqli($servername, $username, $password, "college");
if ($conn->connect_error) {
echo " error in database connectivity";
}
echo "connected successfully";
?>

CODEING( STUDENT LOGIN)

<html>

<head>
<title>student login</title>
<link rel="stylesheet" href="../admin/style2.css">
</head>

<body>
<form name="myform" method="POST" action="log.php">
<header>
<nav>
<div class="logo">
<p>college</p>
</div>
<ul>
<li><a href="../home.html">home</a></li>
<li><a href="../about.html">about us</a></li>
<li><a href="#">login</a>
<ul>
<li><a href="../admin/login1.html"> admin login</a></li>
<li><a href="login.html"> student login</a></li>
</ul>
</li>

46
<li><a href="#">gallary</a>
<ul>
<li><a href="../image.html">photos</a></li>
<li><a href="../video.html">videos</a></li>
</ul>
</li>
<li><a href="../contactus.html">contact us</a></li>
</ul>
</nav>
</header>
<div class="login-wrapper">
<center>
<div class="login">
<div class="lo">
<h2>student login</h2>
<h4> sign in to continue</h4>

<input type="text" placeholder="enter your student id or username" name="std"


size="25" id="txt"><br><br>
<input type="password" placeholder="enter your login password" name="pass"
size="25" id="txt"><br><br>
<input type="submit" value="Login" id="txt1">
</div>
</div>

</center>
</div>

</form>

</body>

<?php
$servername = "localhost";
$username = "root";
$password = "";
#create connection
$conn = new mysqli($servername, $username, $password, "record");
if ($conn->connect_error) {
echo " error in database connectivity";
}
#echo "connected successfully";

$name = $_POST['std'];
$pass = $_POST['pass'];

$sql = "select username,password,registrationno from login";

47
$result = $conn->query($sql);
if ($result->num_rows > 0) {
while ($row = $result->fetch_assoc()) {
if ($row["username"] == $name and $row["password"] == $pass) {

$var = $row['registrationno'];

echo "<h3>hi $name Your registration num is $var</h3>";


include("show.html");

$sql1 = "insert into temp(registrationno) values($var)";

if ($conn->query($sql1) === TRUE) {


echo "LOGIN table updated successfully";
}
}}}
$conn->close();
?>

</html>

CODEING(STUDENT/MARKS.PHP)

<html>

<head>
<title>search form </title>
<link rel="stylesheet" href="../admin/style2.css">

</head>

<body>

<header>
<nav>
<div class="logo">
<p>college</p>
</div>
<ul>
<li><a href="home.html">home</a></li>
<li><a href="about.html">about us</a></li>

48
<li><a href="#">login</a>
<ul>
<li><a href="../admin/login1.html"> admin login</a></li>
<li><a href="student/login.html"> student login</a></li>
</ul>
</li>
<li><a href="#">gallary</a>
<ul>
<li><a href="image.html">photos</a></li>
<li><a href="video.html">videos</a></li>
</ul>

</li>
<li><a href="contactus.html">contact us</a></li>
</ul>
</nav>
</header>
<div class="login-wrapper">
<center>
<div class="login">
<div class="lo">
<br><h1>SEARCH FORM</h1>
<BR><BR><BR>
<?php
$servername = "localhost";
$username = "root";
$password = "";
#create connection
$conn = new mysqli($servername, $username, $password, "college");
if ($conn->connect_error) {
echo " error in database connectivity";
}
#echo "connected successfully";

$q="select registrationno from temp";


$r=$conn->query($q);

$row=$r->fetch_assoc();
$reg=$row["registrationno"];
49
echo $reg;
/*$sql = "insert into
marksba(registrationno,hindi,history1,english,history2,political,computer,hindi2,political2)
values($reg,$hindi,$history1,$english,$history2,$political,$computer,$hindi2,$political2)";*/
$sql="select
registrationno,hindi,history1,english,history2,political,computer,hindi2,political2,sum,averag
e from marksba where registrationno=$reg";
$result=$conn->query($sql);
if($result->num_rows>0){
while($row=$result->fetch_assoc()){
echo"-registrationno:".$row["registrationno"]."<br>".
"-hindi:".$row["hindi"]."<br>"."-history1:".$row["history1"]."<br>".
"-english:".$row["english"]."<br>"."-history2:".$row["history2"]."<br>".
"-political:".$row["political"]."<br>"."-computer:".$row["computer"]."<br>"."-
hindi2:".$row["hindi2"]."<br>"."-political2:".$row["political2"]."<br>".
"-sum:".$row["sum"]."<br>"."-average:".$row["average"];

}
$sql="select
registrationno,physics,chemistry,maths1,english,maths2,chemistry1,physics2,evs,computer,su
m,average from marksbsc where registrationno=$reg";
$result=$conn->query($sql);
if($result->num_rows>0){
while($row=$result->fetch_assoc()){
echo"-registrationno:".$row["registrationno"]."<br>".
"-physics:".$row["physics"]."<br>"."-chemistry:".$row["chemistry"]."<br>".
"-maths1:".$row["maths1"]."<br>"."-english:".$row["english"]."<br>".
"-maths2:".$row["maths2"]."<br>"."-chemistry1:".$row["chemistry1"]."<br>"."-
physics2:".$row["physics2"]."<br>"."-evs:".$row["evs"]."-
computer:".$row["computer"]."<br>".
"-sum:".$row["sum"]."<br>"."-average:".$row["average"];

}
50
$sql="select
registrationno,BusinessLaw,Accountancy,Taxation,Economic,Enterpreneurship,Mathematics,
English,Computer,sum,average from marksbcom where registrationno=$reg";
$result=$conn->query($sql);
if($result->num_rows>0){
while($row=$result->fetch_assoc()){
echo"-registrationno:".$row["registrationno"]."<br>".
"-BusinessLaw:".$row["BusinessLaw"]."<br>"."-
Accountancy:".$row["Accountancy"]."<br>".
"-Taxation:".$row["Taxation"]."<br>"."-Economic:".$row["Economic"]."<br>".
"-Enterpreneurship:".$row["Enterpreneurship"]."<br>"."-
Mathematics:".$row["Mathematics"]."<br>"."-English:".$row["English"]."<br>"."-
Computer:".$row["Computer"]."<br>".
"-sum:".$row["sum"]."<br>"."-average:".$row["average"];

$qd="delete from temp where registrationno=$reg";


$r=$conn->query($qd);
}
else{
echo"result 0";
}
$conn->close();

?>

<div class="demo">
<a class="button" href="login.html">
<div class="logout">LOGOUT</div></a></div>
</div>
</div>
</center>
</div>
</body>
</html>

51
5.1 Comments and Description of Coding segments

5.1.1. Single Line Comment

While there is only one type of comment in HTML, PHP has two types. The first type we
will discuss is the single line comment. The single line comment tells the interpreter to
ignore everything that occurs on that line to the right of the comment. To do a single line
comment type "//" or "#" and all text to the right will be ignored by PHP interpreter.

Example: // This will print out Hello World!

5.1.2. Multiple Line Comment

Similiar to the HTML comment, the multi-line PHP comment can be used to comment out
large blocks of code or writing multiple line comments. The multiple line PHP comment
begins with " /* " and ends with " */ ".

Example: /* This Echo statement will print out my message to the


the place in which I reside on. In other words, the World. */

52
5.2 Standardization Of The Coding

Every company follows a different coding standard based on their best practices. Coding
standard is required because there may be many developers working on different modules
so if they will start inventing their own standards then source will become very un-
manageable and it will become difficult to maintain that source code in future.

Here are several reasons why to use coding specifications −

 Your peer programmers have to understand the code you produce. A coding standard
acts as the blueprint for all the team to decipher the code.
 Simplicity and clarity achieved by consistent coding saves you from common
mistakes.
 If you revise your code after some time then it becomes easy to understand that code.
 Its industry standard to follow a particular standard to being more quality in software.

There are few guidelines which can be followed while coding in PHP.

a. Indenting and Line Length − Use an indent of 4 spaces and don't use any
tab because different computers use different setting for tab. It is recommended to
keep lines at approximately 75-85 characters long for better code readability.
b. Control Structures − These include if, for, while, switch, etc. Control
statements should have one space between the control keyword and opening
parenthesis, to distinguish them from function calls. You are strongly encouraged
to always use curly braces even in situations where they are technically optional.
c. Function Calls − Functions should be called with no spaces between the
function name, the opening parenthesis, and the first parameter; spaces between
commas and each parameter, and no space between the last parameter, the closing
parenthesis, and the semicolon.
d. Comments − C style comments (/* */) and standard C++ comments (//) are
both fine. Use of Perl/shell style comments (#) is discouraged.
e. PHP Code Tags − Always use <? php ?> to delimit PHP code, not the <? ?>
shorthand. This is required for PHP compliance and is also the most portable way
to include PHP code on differing operating systems and setups.

53
f. Variable Names −

i. Use all lower case letters


ii. Use '_' as the word separator.
iii. Global variables should be prepended with a 'g'.
iv. Global constants should be all caps with '_' separators.
v. Static variables may be prepended with’s’.

g. Alignment of Declaration Blocks − Block of declarations should be


aligned.
h. One Statement Per Line − There should be only one statement per line
unless the statements are very closely related.

54
5.3 Error Handling

When creating scripts and web applications, error handling is an important part. If your
code lacks error checking code, your program may look very unprofessional and you may
be open to security risks.

We will show different error handling methods:

 Simple "die()" statements

 Custom errors
 error triggers

1. Using the die () function:

The first example shows a simple script that opens a text file:

<?php
$file=fopen("welcome.txt","r");
?>

If the file does not exist you might get an error like this:

Warning: fopen(welcome.txt) [function.fopen]: failed to open stream:


No such file or directory in C:\webfolder\test.php on line 2

To prevent the user from getting an error message like the one above, we test whether the
file exist before we try to access it:

<?php
if(!file_exists("welcome.txt")) {
die("File not found");
} else {
$file=fopen("welcome.txt","r");}
?>

Now if the file does not exist you get an error like this:

55
File not found

2. Creating a Custom Error Handler:

Creating a custom error handler is quite simple. We simply create a special function that
can be called when an error occurs in PHP.

This function must be able to handle a minimum of two parameters (error level and error
message) but can accept up to five parameters (optionally: file, line-number, and the error
context):

Syntax
error_function(error_level,error_message,error_file,error_line,error_context)

3. Trigger an Error:

In a script where users can input data it is useful to trigger errors when an illegal input
occurs. In PHP, this is done by the trigger_error() function.

Example

In this example an error occurs if the "test" variable is bigger than "1":

<?php
$test=2;
if ($test>=1) {
trigger_error("Value must be 1 or below");}
?>

The output of the code above should be something like this:

Notice: Value must be 1 or below


in C:\webfolder\test.php on line 6

An error can be triggered anywhere you wish in a script, and by adding a second
parameter, you can specify what error level is triggered.

56
5.4 Validation Checks

Validation means check the input submitted by the user. There are two types of validation
are available in PHP. They are as follows –

 Client-Side Validation − Validation is performed on the client machine web


browsers.
 Server Side Validation − After submitted by data, The data has sent to a server
and perform validation checks in server machine.

Some of Validation rules for field


Field Validation Rules

Name Should required letters and white-spaces


Email Should required @ and .
Website Should required a valid URL
Radio Must be selectable at least once
Check Box Must be checkable at least once
Drop Down menu Must be selectable at least once

57
6.
TESTING

58
6.1 TESTING PROCESS

INTRODUCTION

Testing is the process of running a system with the intention of finding errors. Testing
enhances the integrity of a system by detecting deviations in design and errors in the
system. Testing aims at detecting error-prone areas. This helps in the prevention of
errors in a system. Testing also adds value to the product by conforming to the user
requirements.

The main purpose of testing is to detect errors and error-prone areas in a system.
Testing must be thorough and well-planned. A partially tested system is as bad as an
untested system. And the price of an untested and under-tested system is high.

The implementation is the final and important phase. It involves user-training, system
testing in order to ensure successful running of the proposed system. The user tests the
system and changes are made according to their needs. The testing involves the testing
of the developed system using various kinds of data. While testing, errors are noted
and correctness is the mode.

OBJECTIVES OF TESTING:

The objectives of testing are:

 Testing is a process of executing a program with the intent of finding errors.


 .A Successful test case is one that uncovers an as- yet-undiscovered error.

System testing is a stage of implementation, which is aimed at ensuring that the


system works accurately and efficiently as per the user need, before the live operation
commences. As stated before, testing is vital to the success of a system. System testing
makes a logical assumption that if all parts of the as system are correct, the goal will
be successfully achieved. A series of tests are performed before the system is ready of
the user acceptance test.

59
6.2 TESTING METHODS:

System testing is the stage of implementation. This is to check whether the system
works accurately and efficiently before live operation commences. Testing is vital to
the success of the system. The candidate system is subject to a variety of tests: on line
response, volume, stress, recovery, security and usability tests. A series of tests are
performed for the proposed system is ready for user acceptance testing.

The Testing Steps are:-

White Box Testing:

In this technique, the close examination of the logical parts through the software are
tested by cases that exercise species sets of conditions or loops. all logical parts of the
software checked once. Errors that can be corrected using this technique are
typographical errors, logical expressions which should be executed once may be
getting executed more than once and error resulting by using wrong controls and
loops. When the box testing tests all the independent part within a module a logical
decisions on their true and the false side are exercised , all loops and bounds within
their operational bounds were exercised and internal data structure to ensure their
validity were exercised once.

Alpha Testing:

Acceptance testing is also sometimes called alpha testing. Be spoke systems are
developed for a single customer. The alpha testing proceeds until the system developer
and the customer agree that the provided system is an acceptable implementation of
the system requirements.

Beta Testing:

On the other hand, when a system isto be marked as a software product, another
process called beta testing is often conducted. During beta testing, a system is
delivered among a number of potential users who agree to use it. The customers then
report problems to the developers. This provides the product for real use and detects
errors which may not have been anticipated by the system developers.

60
Unit Testing:

Each module is considered independently. it focuses on each unit of software as


implemented in the source code. it is white box testing.

Integration Testing:

Integration testing aims at constructing the program structure while at the same
constructing tests to uncover errors associated with interfacing the modules. modules
are integrated by using the top down approach.

System Testing:

It is executing programs to check logical changes made in it with intention of finding


errors. a system is tested for online response, volume of transaction, recovery from
failure etc. System testing is done to ensure that the system satisfies all the user
requirements

6.3 Testing Strategies

A testing strategy is a general approach to the testing process rather than a method of
devising particular system or component tests. Different testing strategies may be adopted
depending on the type of system to be tested and the development process used. There are
two different strategies available:

a. Top-Down Testing
b. Bottom-Up Testing

a) Top-Down Testing

Top-Down Testing high levels of a system are tested before testing the detailed
components. The application is represented as a single abstract component with sub-
components represented by stubs. Stubs have the same interface as the component but

61
very limited functionality. After the top-level component has been tested, its sub-
components are implemented and tested in the same way. This process continues
recursively until the bottom - level components are implemented. The whole system may
then be completely tested. Top-down testing should be used with top-down program
development so that a system component is tested as soon as it is coded. Coding and
testing are a single activity with no separate component or module testing phase.If top-
down testing is used, unnoticed design errors may be detected at an early stage in the
testing process. As these errors are usually structural errors, early detection means that
extensive re-design re-implementation may be avoided. Validation can begin early in the
testing process as a demonstrable system can be made available to the users.

b) Bottom-Up Testing

Bottom-Up Testing is the opposite of Top-Down. It involves testing the modules at the
lower levels in the hierarchy, and then working up the hierarchy of modules until the final
module is tested. This type of testing is appropriate for object-oriented systems in that
individual objects may be tested using their own test drivers.

62
7.

CONCLUSION /

FUTURE SCOPE

63
CONCLUSION OF THE PROJECT

Our project is only a humble venture to satisfy the manager their project work , several user
friendly coding have also adopted. This package shall prove to be a powerful package in
satisfying all the requirement al the school. The objective of software planning is to provide
a frame work that enables the manger to make reasonable estimates made within a limited
time frame at the beginning of the software project and should be updated regularly as the
project progresses.

At the end it is concluded that we have made effort on following points…

 A description of the background and context of the project and its relation to work
already done in the area.
 Made statement of the aims and objectives of the project.
 The description of purpose, scope and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement specifications of the system and the actions that can
be done on these things.
 We understand the problem domain and produce a model of the system, which
describes operation that can be performed on the system.
 We included features and operations in detail , including screen layouts.
 We designed user interface and security issues related to system.
 Finally the system is implemented and tested according to test cases.

64
FUTURE SCOPE OF THE PROJECT

The future scope of the College Management System (CMS) project envisions a dynamic
evolution, embracing technological innovations and educational advancements. As we look
ahead, the integration of cutting-edge technologies such as Artificial Intelligence (AI) and
Machine Learning (ML) stands out as a transformative avenue. These technologies can
empower the system to analyze student performance data, predict learning outcomes, and
offer personalized recommendations for optimized educational journeys. Furthermore, the
implementation of advanced data analytics tools will play a pivotal role in generating
actionable insights, facilitating informed decision-making by administrators, teachers, and
parents. Recognizing the growing significance of mobile platforms, the development of
robust mobile applications is paramount, fostering real-time communication and providing
stakeholders with immediate access to vital information, including grades and attendance.

The communication landscape within the educational community is poised for enhancement
through the integration of emerging channels. Chatbots, social media platforms, and other
interactive tools promise to enrich engagement and foster efficient communication among
parents, teachers, and students. In the realm of security and privacy, the future scope
necessitates continual updates, including the exploration of biometric authentication and the
potential incorporation of blockchain technology to fortify data security. As educational
models shift, the system should demonstrate adaptability, aligning with competency-based
education and microlearning strategies. Workflow automation emerges as a key efficiency
booster, automating routine administrative tasks and amplifying overall system performance.

65
8. BIBLIOGRAPHY

1. Wikipedia.com
2. W3School.com
3. Easynotes.com
4. Phptpoint.com
5. Tutorialspoint.com
6. Webtutorials.com
7. Javatpoint.com

66

You might also like