A

Minor Project Report

On

“WEB SITE DESIGNING IN COLLEGE MANAGMENT”

Submitted to

RAJIV GANDHI TECHNICAL UNIVERSITY

BHOPAL (M.P)

In Partial fulfillment for the award of degree of

MASTER
OF
COMPUTER APPLICATION
By
GOVIND SINGH

Under the Guidance of HOD(MCA Deptt.)

Prof.Sanjay Bohara Prof.Sanjay Bohara

Lecturers (MCA Deptt.)

Principal
Dr. Namrata Jain Gandhi

SHREESAI INSTITUTE OF TECHNOLOGY (SSIT)

NEAR RTO OFFICE, JAORA ROAD
RATLAM-457001 (M.P.)
MAY-2019

1
 A
Minor Project Report
on
“WEB SITE DESIGNING IN COLLEGE MANAGMENT”

Submitted to

SHREE SAI INSTITUTE OF TECHNOLOGY

RATLAM (M.P)

In Partial fulfillment for the award of degree of

MASTER
OF
COMPUTER APPLICATION
By
GOVIND SINGH

Under the Guidance of HOD (MCA Deptt.)

Prof. Sanjay Bohara Prof. Sanjay Bohara

Lecturer (MCA Deptt.)
Principal
Dr. Namrata Gandhi

SHREE SAI INSTITUTE OF TECHNOLOGY (SSIT)

NEAR RTO OFFICE, JAORA ROAD
RATLAM-457001 (M.P.)
MAY-2019

2
 DECLARATION

We hereby declare that the work presented in this project report entitled
“WEB SITE DESIGNING IN COLLEGE MANAGMENT” towards the
partial fulfillment of requirement for the award of degree of Master of Computer
Applications, submitted in the Shree Sai Institute Of Technology , is the authentic
record of my work under the guidance of Prof.Sanjay Bohara, Lecturer (MCA
Deptt.).

NAME OF STUDENT:
GOVIND SINGH

External Examiner Internal Examiner

3
 CERTIFICATE

This is to certify that the project entitled COUNTER “WEB SITE DESIGNING
IN COLLEGE MANAGMENT” has been carried out by GOVIND SINGH
under my guidance in partial fulfillment for the award of MASTER OF
COMPUTER APPLICATION by the Rajiv Gandhi Technical University,
Bhopal (M.P.), during the academic year 2018-19.

Dr. Namrata Gandhi Prof. Sanjay Bohara

Principal (MCA Deptt.) HOD (MCA Deptt.)

Dr. Namrata Gandhi

Principal

SHREE SAI INSTITUTE OF TECHNOLOGY

(Approved by AICTE Delhi, Affiliated to RGTU Bhopal and Govt. of Madhya Pradesh)
NEAR RTO OFFICE, JAORA ROAD, RATLAM-457001

4
 ACKNOWLEDGEMENT

It is our great pleasure to present the project “WEB SITE DESIGNING IN

COLLEGE MANAGMENT” as presenting any project report always gives a
deep knowledge and sense of satisfaction and achievement.
We have no words to express our gratitude towards Prof. Sanjay Bohara (HOD
of MCA Department S.S.I.T, Ratlam.), for giving us the opportunity to do this
project and making all this possible.
We extend our sincere acknowledgment to Prof. Sanjay Bohara (Project
Guide) for providing us such a wonderful project and gave us an opportunity to
complete the main module of the project and for giving his precious time to
complete our project.

Finally I would like to appreciate support of my classmates and friends,

who held my hands during the entire course of project, without their support,
this project would not have attained its completion.

From:
GOVIND SINGH : 0705CA183D07
MCA IVSem

5
 INDEX

1. INTRODUCTION

2. LITERATURE REVIEW

3. METHODOLOGY/EXPERIMENTATION

3.1 ANALYSIS

3.1.1 REQUIREMENT ANALYSIS

3.1.2 OBJECT ORIENTED ANALYSIS
3.1.3USE CASE ANALYSIS

3.2 USE CASE DISCRIPTION

3.3PROJECT PLANNING
3.2.1 REQUIREMENT ANALYSIS
3.3.2 PROJECT PLANING
3.3.3 DESIGNING PHASE
3.3.4 IMPLEMENTATIN PHASE

6
4. TESTING

4.1 TESTING
4.2 TESTING OBJECTIVE
4.3 TEST CASES AND TEST RESULT
1. UNIT TESTING
2. INTEDRATION TESTING
3. VALIDATION TESTING
4. HTML AND CSS VALIDATION PER W3C
5. QUALITY ATTRIBUTE

5. CONCLUSIONS

6. REFERENCES

7
 Chapter – 1
INTRODUCTION

8
1. INTRODUCTION

This application college management system based on Intranet

that aims to all the levels of management providing information
within an organization. This system can be used as an
information management system for the college.

For a given student/staff (Technical / Non-technical) the

Administrator creates login id & password, using these student/
staff (Technical / Non-technical) can access the system to either
upload or download some information from the database.

Not only this added user will also get to know about the events
and extra curriculum activities which will hold into the college
campus.

The main menu will contain six parts which are as follow:

 Home

 About Us

 Event

 Courses

 Gallery

 Contact

9
ABOUT US OF COLLEGE MANAGEMENT SYSTEM
This feature will provide the information about the college and
developers so that if you want to get a new design or any kind of
change and suggestion you can come up to us and make you
contribution in this system of online college management.

CONTACT US OF COLLEGE MANAGEMENT SYSTEM

In this section, we have provided the contact number and proper
address so that students and teachers can reach to us and mentioned
their problems to solve it if there is any technical issue related to their
login and logout.

Students can also contact us if they are curious to know something

about our database and how the system is working, we will provide
them with a brief introduction about the system working and welcome
their ideas if any.

Now, let us discuss the ER-Diagram of the system but before that, we
need to explain why we need ER-diagram why ER-diagram is so useful
while developing and designing the system.

An entity relationship model also called an entity-relationship (ER)

diagram, is a graphical representation of entities and their
relationships to each other, typically used in computing regarding the
organization of data within databases or information systems.
It consists of following fields such as:

An entity which is represented by rectangle it is a real-world object

used to represent the user admin and other real objects.

10
 Chapter – 2

LITERATURE REVIEW

11
2. LITERATURE REVIEW

It is widely accepted that the use of information and communication

technology (ICT) in the organization sector offer great potential for improving the
quality of service provided, the efficiency and effectiveness of personnel and
reduce organizational expenses. Now days the use of information technology (IT)
constitutes an inseparable part of a great deal of our daily activities. Information,
and generally the technology providing it, has become a vital strategic and
economic asset of companies and organizations and, moreover, of their executives.
The rapid development of information technology as regards computing system
and software packages and, simultaneously, the installation of expanded
telecommunication networks, has significantly improved the management of
information improved the management of information, and particularly its
disposition and diffusion consequently, information technology, the science of
gathering, storage, transmission, and processing of information gradually becomes
a science of communication. At the same time, all organization companies are
demand, timesheet management and services of development in a dignified
environment where individually aimed services can be provided to each one of
them, depending or thus needs, companies are changing, not, only in Greece but all
over the world company are becoming more aware of employee working and cost
of respected time. Thus the demand for appropriate information technology in
timesheet management organization is high. That’s why we are committed to
design a project that will provides a information system for all of those user who
need information instantly, user can easy get information about employee,
timesheet and their working hour and can occupy the cost and performance.

12
EXISTING SYSTEM DESCRIPTION OF COLLEGE MANAGEMENT
SYSTEM
In this section, we will discuss the existing system and some of their
drawbacks which force us to plan this whole idea of developing online
college management system.Let us take an example Initially colleges
appoint many employees to maintain the record of the student, teachers,
other staff, employees’salaries and student’s fee.

If any student wants to submit the fee he/she need to go to the fee counter
for paying their fees and wait for one to two days for updating and again
went to the fee office to know the status, and this whole record use to
maintain on card and files so there might be chances of missing.

Suppose if some student comes and ask for the status of his fee after one
month then the worker will open his file and search it manually for the
student’s name which will take time.

Suppose we want to organize an event in college we need to create posters,

banners and make an announcement in classes so that students participate
but if any student got absent on that day then he will remain unnotified.

DRAWBACKS OF THE OF COLLEGE MANAGEMENT SYSTEM

This process is so much time consuming

There is a threat for the record of the student and teachers, in this case,
there might be a chance that person makes entry on someone else record.

There is no proper way of getting to know about the events and extra
curriculum activities happening in colleges.

It might be the case that student tries to bribe the teachers to avoid the long
queue.

So, above this is the whole process of college management system and its
working by our system we can make it a little bit more simple and fast
process of automating it.

We can automate this process by creating the application which will allow
you to use these things in a fully functional way and the application will
include the following entities (an entity is a real-world object).

13
The automated application help in following way:

A student can register himself directly on the college application for any
notification of the event and for depositing fee and students can also post
their queries and check their fee status.

If the students are not aware of policies then admin will make him contact
with this application and help him to complete the whole process.

Admin will maintain the record and atomicity by using the proper table to
save records so that no one can access it and data remain safe.

Students need not bother about his/her fee deposit and without moving
from his place or making so many phone calls he can make the fee payment.

No need of worrying about status you can check that from your place.

Students can check new information and achievements of the college

students through the application which will motivate them and this all
things would be uploaded by the Admin on the application.

The whole process of getting work done will become faster than the
conventional way of getting insurance.

Let us look the different aspects which we have designed to make the
website work properly. Here we are not discussing the admin module
because all others module will cover the admin module part so to remove
the same content from the report we are ignoring the admin part.

14
 Chapter – 3
METHODOLOGY/
EXPERIMENTATION

15
3. METHODOLOGY/ EXPERIMENTATION

3.1. ANALYSIS

Aanalysis can be define as a process of accumulate the requirement of users and

here the developer have to understand what’s the problem users are phasing in
current scenario and after ponder we have to decide how can we solve that
problem, according to web engineering this phase is subdivided in following
phases defined below

3.1.1. Requirement Analysis:

In this phase we have observe a need of people which can solve the problem and the
problem we seems was the problem of contact and the best way we can see in our
daily life is that if any person required to perches an old mobile for that he need
some help about working and functions of the same. His need can b fulfill bye the
person who already use that phone. Searching of this person is very time consuming
and also very time wasting approach, so we ponder on this problem and finally
decide to make a web application named “Sales bizari.com ”. on which every
person can be demand for any help about sales and purchase of any old items. We
have build a online application which will provide a common platform to make a
network between buyer and seller.

16
3.1.2. Object Oriented Analysis:

Analysis is a process defined as “it is a process of accumulation of problems and

requirement rather than solution” and in object oriented analysis we fix some
object and relate them together to make a complete model which can be intended
as solution of particular problem domain. If we talk about our project in our project
in object oriented analysis we realize the problem of ‘contacts’ and object of are
project is nothing but user because the main aim of our project is to make a
network between buyer and seller and we did nothing but made a online
application on which all the buyer and seller can contact with each other this fact
can be understand after examining the diagrams demonstrate below.

3.1.3. Use-case Analysis:

Use case analysis is defined as a process which demonstrates how user will interact
with our application and how the application will solve the problem domain. Use
case analysis of ONLINE SHOP is very simple, any user must have to make a
profile as we can generally in any online application and all the user present on the
site are able to directly contact together for sell or purchase items and also all the
user can upload our item picture and add items in our sell list or bid on item. Any
anther user can also bid on items and admin can also bid on items. Admin can lock
the user and unlock the lock user.

17
2. USER CASE DESCRIPTION:

In above scenario we explained that our site is belongs to C-A or consumer to admin
mode of website development according to which two user can directly communicate
with each other according to our scenario a user can make profile, login or logout in
account, search items, add items, edit item detail, bid on item change bid, remove bid
lock and unlock the user streaming (verifying) items. Search for items by name and
check the item detail. Without login we can also search the item but cannot bid on
items. Without login we can also check the sold items list.

3.2. PROJECT PLANING

If our aim is to build an desktop base application or a standalone program than

it is necessary to always use a linear approach because in some programs we need
to go back for updating purpose and some programs required only one way to go
so it necessary to choose a modal on which we have to work but in case of web
application it is not necessary to choose any linear way to built any project while
we can use a simple approach we can apply on any type of project and reason
behind this is that in any web application we have to jump on any phase and also
there is a large team required for any web application and for each phase there are
some selected member while in standalone program all the team work together on
each phase at a time the phase we use in our project are as follows :

3.2.1 Requirement Analysis: -

18
 Once a customer is started discussing his requirements, the team gets into it,
towards the preliminary requirement analysis. As the web site is going to be a part
of a system, it needs a complete analysis as, how the web site or the web based
application is going to help the present system and how the site is going to help the
business. Moreover the analysis should cover all the aspects especially on how the
web site is going to join the existing system. The first important thing is finding the
targeted audience. Then, all the present hardware, software, people and data should
be considered during the time of analysis. For example, if a company XYZ corp. is
in need of a web site to have its human resource details online, the analysis team
may try to utilize the existing data about the employees from the present database.
The analysis should be done in the way, that it may not be too time consuming or
with very less informative. The team should be able to come up with the complete
cost- benefit analysis and as the plan for the project will be an output of analysis, it
should be realistic. To achieve this analyst should consult the designers, developers
and testers to come up with a realistic plan.

3.2.2 Project Planning: -

Here we have to maintain whole schedule of our project and ensure that the
scope of the project will not grow. Project manager identify the required task for
deciding the schedule and budget of the project. Then he should required
appropriate resource. The project manager generally writes the discovery
document in which milestones must be decided with the deliverables. There should
be some changes controls process to maintain the changes that may sprung up
during designing and implementation phase. The project manager is supposed to
conduct regular meeting with full team of project makers to check the completion

19
of models and compare with schedule. In this phase, you and your team must
determine the "hows" of the application. What scripting language is most
appropriate, which features must be included, and how long will it take? These are
some of the questions that must be answered through this planning phase. The
main tangents at this point are the project plan and functional specification. The
project plan determines a timeframe of events and tasks, while the functional
specification outlines in detail how the application will function and flow.

The Planning Phase is the time when the project team translates the initial
vision/scope from the Envisioning Phase into practical plans on how to achieve it.
The purpose of the Planning Phase is to define the solution in detail along with the
approved project plan and schedule. This work includes creating a functional
specification, developing the solution architecture and design, and preparing cost
estimates. Team members draw upon their expertise to create detailed individual
plans, such as the development plan, test plan, and deployment plan, as well as
schedules for all aspects of the project. Program Management combines these
individual plans and schedules and synchronizes them to create the master project
plan and schedules. The Planning Phase culminates in the Project Plans Approved
Milestone. Passing this milestone indicates that the customer, the project team, and
all stakeholders agree on the details of the plans, including what will be built, how
it will be built, when it will be delivered, and what it will cost.
Planning Phase Tasks

The major migration tasks conducted during the Planning Phase are summarized in
the following list:

20
Developing the solution design and architecture-

The development team begins the design process with the solution design and
architecture and culminates it with a design document that becomes part of the
functional specification.

Validating the technology-

The development team also validates technologies to ensure that they meet the
business needs for the specific solution.

Creating the functional specification-

The project team and Program Management Role create a functional specification
that describes the solution requirements, the architecture, and the detailed design
for all the features. This represents the contract between the project team and
customer.

Developing the project plans-

The Program Management Role and the various teams that make up the project
team develop a collection of plans to define the tasks for all six MSF team roles,
and Program Management consolidates them into a master project plan.

Creating the project schedules-

The Program Management Role and the various teams create milestone-
driven schedules for each individual team role, and Program Management
consolidates them into the master project schedule.

21
3.2.3 Designing Phase: -

This phase is when we make the design decisions of how your site will
look, and how it will work. From our analysis we should have a good idea on your
target audience. Now we are able to decide which technologies are best suited for
your company. Then we develop the user interface and navigation system. Also,
the site will be optimized for the average customer connectivity to the WEB and
well as the configuration of their computer system. The personality, the look and
feel of the website will also be established at this phase. This might be the ideal
time to think over your identity, logo and branding of your company. If you need
to, we could bring in Graphic Designers that would assist with a new image.

3.2.4 Implementation Phase:

In this phase, the production system is installed, initial user training is completed,
user documentation is delivered, and the post implementation review meeting is
held. When this phase is completed, the application is in steady-state production.
Once the system is in steady-state production, it is reviewed to ensure that we met
all of the goals in the project plan for a satisfactory result. The team may be
regrouped again, to include specific expertise in installation and training.

es are drawn between entity sets and the relationship sets they are involved in. If
all entities in an entity set must participate in the relationship set, a thick or double
line is drawn.

22
ENTITY-RELATIONSHIP DIAGRAM:

The Entity-Relationship (E-R) data model was developed to facilitate database

design by allowing specification of an enterprise schema that represents the overall
logical structure of a database. It is a data-oriented model of a system, whereas a
DFD is a process-oriented model. It has three main components: data entities, their
relationships, and their associated attributes.

1. Entity.
It is the most elementary process of an organization about which data is to
be maintained. Every entity has a unique identity, which distinguishes it
from other entities. An entity type is the description of all entities to which a
common definition and common relationships and attributes apply. It is
represented by a rectangular box with the name of the entity written inside.

For example, invoice object has various elements, such as invoice number,
date, quantity, discount, total-price, etc.

Entity

23
 2. Relationship. Entities are connected to each other by relationships. It
indicates how two entities are associated. A diamond notation with the name
of the relationship is represented as written inside.

Relationship

3. Attribute. Each entity type has a set of attributes associated with it. An
attribute is a property or characteristic of an entity that is of interest to the
organized. It is represented by an oval-shaped box with the name of the
attribute written
inside it. The notation for attribute is

Attributes

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 (structured design). 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

24
Process:

Figure: Process

A process shows a transformation or manipulation of data flows within the system.

Data Store:

Figure: Data Store

A data store is a holding place for information within the system:

It is represented by an open ended narrow rectangle.
Data stores may be long-term files such as sales ledgers, or may be short-term
accumulations: for example batches of documents that are waiting tobe processed.
Each data store should be given a reference followed by an arbitrary number.

External Entity:

Figure: External Entity

25
An external entity is a source or destination of a data flow which is outside the area
of study. Only those entities which originate or receive data are represented on a
business process diagram. The symbol used is an oval containing a meaningful and
unique identifier.

Data Flow:

Figure: Data flow

A data flow shows the flow of information from its source to its destination. A data
flow is represented by a line, with arrowheads showing the direction of flow.
Information always flows to or from a process and may be written, verbal
electronic. Each data flow may be referenced by the processes or data stores at its
head and tail, or by a description of its contents.

1. The DFD is also called as bubble chart. It is a simple graphical formalism

that can be used to represent a system in terms of input data to the system,
various processing carried out on this data, and the output data is generated
by this system.

2. The data flow diagram (DFD) is one of the most important modeling tools. It
is used to model the system components. These components are the system
process, the data used by the process, an external entity that interacts with
the system and the information flows in the system.

26
3. DFD shows how the information moves through the system and how it is
modified by a series of transformations. It is a graphical technique that
depicts information flow and the transformations that are applied as data
moves from input to output.

4. DFD is also known as bubble chart. A DFD may be used to represent a

system at any level of abstraction. DFD may be partitioned into levels that
represent increasing information flow and functional detail.

27
 Chapter - 4

TESTING
4.1 TESTING
4.2 TESTING OBJECTIVE
4.3 TEST CASES AND TEST RESULT
1. UNIT TESTING
2. INTEDRATION TESTING
3. VALIDATION TESTING
4. HTML AND CSS VALIDATION PER W3C
5. QUALITY ATTRIBUTE

28
 SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying

to discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub assemblies, assemblies and/or a
finished product It is the process of exercising software with the intent of ensuring
that the
Software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.

4.1– TESTING

Software testing is a critical phase of software quality assurance. It indicates

the ultimate review of specification, design and code generation. Once source code
has been generated, software must be tested to uncover and correct maximum
possible errors, before being delivered. Testing emphasizes on a set of methods for
the creation of test cases that fulfill overall testing objectives.

The primary objectives of software testing are as follows:

1. Testing is a process of executing a program to find an error in it.

2. A good test case should have a high probability of finding an as-yet-

undiscovered error.

3. A test case will be considered successful if it uncovers an as-yet-

undiscovered error.

29
4.2 Testing Objective:
The development of software systems involves a series of production
activities where opportunities for injection of human fallibility are enormous. Error
may begin to occur at very inception of the process where the objectives may be
enormous or imperfectly specified, as well as in later design and development
stages.
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. And it needs to
be done in almost every phase of product development life cycle not just before a
product is handed to a customer.
The following are some attribute of a good test.
 A good test has a high probability of finding error. To achieve this goal the
tester must understand the software and attempt to develop a mental picture
of how the software may fail. Ideally the classes of failure are probed.
 A good test is not redundant
 A good test should be best of bread.
 A good test should be neither too simple nor too complex.

4.3- Test cases and Test Results

1. Unit Testing:

Unit testing aims the verification effort on the smallest unit of software
design i.e., a software component or module. It uses procedural design as a guide
to test major control paths and uncover errors within the module boundary. It is

30
white box oriented and the step can be conducted in parallel for multiple
components.

Unit testing is a dynamic method for verification, where the program is

actually compiled and executed. It is one of the most widely used methods, and the
coding phase is sometimes called “coding and unit testing phase”. The goal of unit
testing is to test modules or “units”, not the whole software system. Unit testing is
most often done by the programmer himself/herself. The goal of unit testing is to
isolate each part of the program and show that the individual parts are correct. A
unit test provides a strict, written contract that the piece of code must satisfy. As a
result, it affords several benefits.

The primary goal of unit testing is to take the smallest piece of testable
software in the application, isolate it from the remainder of the code, and determine
whether it behaves exactly as you expect. Each unit is tested separately before
integrating them into modules to test the interfaces between modules. Unit testing
has proven its value in that a large percentage of defects are identified during its
use.

Unit testing is a software verification and validation method where the

programmer gains confidence that individual units of source code are fit for use. A
unit is the smallest testable part of an application. In procedural programming a
unit may be an individual program, function, procedure, etc., while in object-
oriented programming, the smallest unit is a class, which may belong to a
base/super class, abstract class or derived/child class.

31
 2. Integration testing

Integration testing is a phase of software testing in which individual software

modules are combined and tested as a group. It follows unit testing and precedes
system testing. The major objective of integration testing is to tackle the problem
of interfacing i.e. putting all the acceptable imprecision (view) may be magnified
to unacceptable levels; global data structure can cause problems and to truncate
this list of problems we use integration testing.

Integration testing is a systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors associated with
interfacing. The objective is to take unit tested components and build a program
structure that has been dictated by the design.

Integration testing strategy used is Bottom-Up Integration Testing. In it all

the bottom or low level modules, procedures or functions are integrated and then
tested. After the integration testing of lower level integrated modules, the next
level of modules will be formed and can be used for integration testing. This
approach is helpful only when all or most of the modules of the same development
level are ready. This method also helps to determine the levels of software
developed and makes it easier to report testing progress in the form of a
percentage.

32
 3. Validation Testing:

At the climax of integration testing, software is developed as a package

having all the errors uncovered and corrected. At this time, a final series of
software test may begin. It is called validation testing. Validation succeeds when
software functions in a reasonably expectable manner. Validation attempts to
uncover errors, but the emphasis is on the requirement level i.e. the things that will
be immediately apparent to the customer.

At the validation level, testing focuses on user visible actions and user
recognizable output from the system. Validations testing is said to be successful
when software functions in a manner that can be reasonably expected by the
customer.

A major element of the validation process is a configuration review, which

is conducted to ensure that all software configuration elements have been well
developed, well-cataloged, and have the essential detail to bolster the support
phase of the software life cycle.

4 . HTML and CSS Validation per W3C (World Wide Web Consortium)

i. Coding Standards:

I am very picky about the quality of your HTML and CSS coding. I make sure that
every HTML document and CSS style sheet validates as compliant with the latest
W3C standards. Web pages that use the W3C standards of coding helps ensure that
your web pages will render consistently in all of the major browsers.

33
 ii. Browser Compatibility Testing:

Your website is tested on a variety of browsers to insure proper display and

functionality. I test with Internet Explorer, Mozilla Firefox, Apple Safari, and
Google Chrome. If your webpage content does not display exactly the same in all
of these browsers, I adjust the code until it does!

iii. Grammar & Spell Check:

Before the website is launched, a grammar and spell check is performed to insure
there are no mistakes.

iv. Dead Link Check:

A thorough check for misdirected links and missing files is performed just prior to
as well as after the launch of the website.

v. Forms / Programming;

Any email contact forms and/or programming features included in your project are
tested to confirm they are functioning as required.

34
 5. Quality Attributes:

The software units in a system are modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on modules,
independently of one another, to locate errors. This enables, to detect errors in
coding and logic that are contained within each module. The various controls are
tested to ensure that each performs its action as required.
Data can be lost across any interface, one module can have an adverse
effect on another, sub functions when combined, may not produce the desired
major functions. Integration testing is a systematic testing to discover errors
associated within the interface. The objective is to take unit tested modules and
build a program structure. All the modules are combined and tested as a whole.
This testing provides the assurance that the application is well integrated functional
unit with smooth transition of data.

USER INTERFACE

The user interface is one of the most important parts of any program or a
project because it determines how esaily you can make the program do what you
want. A powerful program with a poorly designed user interface has a little
value.in our project the employee intract with the all program of a system
application. And it is very esay to understand for a employee to make the timesheet
for the monthy bases.and as same as the admin also use the all program of the
system. Admin can do whatever he want.
In our project the three type of user interface.

35
1-command language: The user must know the machine and program-specific
instruction or codes.
2-menus: User chooses the command from list displayed on the screeen.
3-Graphical user interface- User gives commands by selecting and clicking on
icons displays on the screen
virtual part of a computer application or operating system through which a user
interacts with a computer or a software.

SNAPSHOTS:

1. Home page:

36
2. About Us:

3. Event :

37
4. Courses:

5. Gallery:

38
6. Contact :

7. Registration form :

39
8. Footer :

9. Data Table:

40
10. MCA DETAILS :

11. OUR TEAM :

41
STUDENT LOGIN OF COLLEGE MANAGEMENT SYSTEM:
This module of the system will help the students to create his account
where he will find the following options:

He will start to get notifications

Students can pay their fee through the portal and check status

They can find their results and test marks

Students can apply for rechecking of the answer sheet through his
portal.

Students can file a complaint against their teachers if the teacher is not
behaving well.

Students can also file a report if they are facing any ragging issue.

So above are the following points which a student can perform after
getting register on the portal and get a confirmation message from
admin.

DEPOSIT FEES OF COLLEGE MANAGEMENT SYSTEM:

This module of the system will help in maintaining the financial record
of the students and teachers, there is constraint:

It will only provide the information about the fee status of the
students.

Teachers can also see their respective increments through their

portals.

Students can deposit their late fee or any kind of charges through this
portal without standing in line.

42
ASK QUERIES FORUM OF COLLEGE MANAGEMENT SYSTEM :
In this module of the developed system, we will allow the students to
ask their queries. Students and teachers both are allowed to answer
the queries, students can also post problems regarding any subjects or
college rules and regulations.

At this module person who does not belong to the college can also post
his queries and problems to clarify about the aura of the college and
get a better understanding of fee structure before entering the college.

ABOUT US OF COLLEGE MANAGEMENT SYSTEM

This feature will provide the information about the college and
developers so that if you want to get a new design or any kind of
change and suggestion you can come up to us and make you
contribution in this system of online college management.

CONTACT US OF COLLEGE MANAGEMENT SYSTEM

In this section, we have provided the contact number and proper
address so that students and teachers can reach to us and mentioned
their problems to solve it if there is any technical issue related to their
login and logout.

Students can also contact us if they are curious to know something

about our database and how the system is working, we will provide
them with a brief introduction about the system working and welcome
their ideas if any.

Now, let us discuss the ER-Diagram of the system but before that, we
need to explain why we need ER-diagram why ER-diagram is so useful
while developing and designing the system.

An entity relationship model also called an entity-relationship (ER)

diagram, is a graphical representation of entities and their
relationships to each other, typically used in computing regarding the
organization of data within databases or information systems.
It consists of following fields such as:

43
An entity which is represented by rectangle it is a real-world object
used to represent the user admin and other real objects.

ATTRIBUTES OF COLLEGE MANAGEMENT SYSTEM:

Every entity has their attributes such has every car has their
specifications. Oval shape represents it.

In ER-diagrams diagonal is used to represent the relationship of the

between the entities.

Here we will see the ER-diagram and its attributes:

44
Let us discuss the entities one by on with their respective attributes.

Admin:
As we have not discussed this module earlier but here we will discuss
its functionality that how this entity is used in the working of the
application, admin use this application to give the access to the person
who wants to register themselves on the website and add the
legitimate users on the system.

Whenever you will send a request for registration you will get approval
email from the admin so that you can continue and later on you will
get the username and passwords of your choice for security purpose.

As we can see the diagonal which is connected with the admin, these
diagonals show the relationship of admin with different entities.
Admin organizes employees and keeps the record of the fee so that he
comes to know that what kind of employees are working there and
about the fee status of the students, Admin can also connect with
students and teachers.

Event
This entity will keep the records of the happening event in the college
and also help in notifying to the students so that they can participate
in the events which they like to join. The attributes of the event are as
follow:

E_id:
This attribute will uniquely identify the events so that we can add
different events on the portal. If we have different event id then the
event will not overlap.

E_name:
This attribute will give an idea to the participants that what is the
event all about so that they will prepare themselves according to that.

45
Suppose if the event is spell words then they will prepare for that. So,
this is an important attribute for the participants.

E_winner:
This attribute maintains the records of the game winner so that at the
last of the events we can give the award to the winners.

Student
This entity is one of the important attributes which need to be handled
by this system so we will discuss the attributes of this entity in brief
which are as follows:

S_id:
This attribute will help us in uniquely identified the identity of the
student because in college there are many students having the same
name and last name so to distinguish among them we need something
that is in.

This is different for every student so we can use this to maintain the
atomicity in our records.

S_name:
This will tell the name of the students. And also, mentioned on his
card so that teacher can use it to identify the students.

S_branch:
This will inform us about the branch of the student which will help in
maintaining the proper record of the student and give us additional
knowledge about the student’s profile.

S_result:
This attribute will give you the information about the student result,
which will reflect in result section of the portals. The student will also
get there marks through the system after conducting the exams.

46
S_year:
This attribute will tell us about the year of the student that whether he
is 1st-year student or second year so on. This attribute will help us to
decide the fee structure of the student and courses of the students.

S_contact:
This attribute will provide the information of the student so that we
can contact them at any time when we want to inform them something
urgently.

Subjects:
This entity will show the subjects of the students according to the
semester wise. Let us see the attributes of the subjects:

Sub_id:
This will clarify the subject to the students. This will also help in
choosing the subjects.

Sub_name:
This will show the name of the subject, it will define the name of the
subject so that user can use it.

Fee:
This new entity is fee will help us to maintain the fee amount of the
students.

F_id:
Generally, it is known as receipt id which has given by fee department
so that user can check his status.

F_amount:
This attribute will give us the information about the amount of fee we
need to take from any student, and help in upholding the proper
records.

47
Employee:
This attribute will uphold the information about employees of the
college so that we can track their records and take actions related to
that. Employees have an aggregation relationship with teacher and
worker as an employee can be a teacher or a worker.

Their attributes are as follow:

E_id:
This attribute will help to find the unique identity of the employees.

E_name:
This attribute will tell us about the name of the employee so that we
can contact to the employee by their name.

E_DOJ:
This attribute will keep the record of joining of the employee.

Teacher:
This is an important entity let’s see its important attributes

T_subject:
This will describe the teacher’s subject that which subject she will
teach.

T_department:
This will provide us information about the department of the teacher
like CSE, ECE, Mechanical etc.

FEASIBILITY OF COLLEGE MANAGEMENT SYSTEM

Feasibility is a test of system proposal according to its work ability
impact on the organization, ability to meet user needs & effective use
of resources. Three key considerations are involved in the feasibility
analysis are as under

48
Operational feasibility of college management system
PURPOSE:
to find out whether the system will be functional after its development
and installation?

The outcomes of the operational feasibility are:

A system to be developed is a critical need for business purpose only.

Technical feasibility of college management system

PURPOSE:
to examine out whether the current technology is sufficient for the
development of the system.

An estimate is made of whether the identified user needs may be

satisfied using current software and hardware technologies.

The outcomes of the technical feasibility are:

Existing technology supports the system completely

Economic feasibility of college management system

This analysis is most frequently used method for comparing the cost
with benefit or income that is expected from the developed system.

5.CONCLUSION
This is one of the main tasks of the developer to design such an
interface that user can use it easily in one word it should be user
friendly and for this you should have better understanding of the
audience which going to use this application, initially we need to locate
the targeting people that what kind of application do they need.

After getting all this information we should start to design the

application.

49
 6.REFERENCES & BIBLOGRAPHY
6.1 LINKS:

 www.ssitrtm.com
 www.ssitratlam.org

6.2 BOOKS:

 Begining PHP and MYSQL from Novice of professiona by jason gilmore.

 The Joy of Programming - A Beginner,s Guide- By Alan Forbes

50