UNIVERSITY OF SCIENCE AND TECHNOLOGY

MEGHALAYA
RIBHOI 9TH MILE, MEGHALAYA

A PROJECT REPORT
On
MONTFORT SCHOOL WEBSITE

In partial fulfillment of the degree of BCA from

University Of Science &Technology, Meghalaya

Submitted By:
Md Noorain
2019/BCA/0022
Department of Computer Science & Electronics
UNIVERSITY OF SCIENCE &TECHNOLOGY
MEGHALAYA

CERTIFICATE FROM HOD

This is to certify that the project work, entitled “MONTFORT SCHOOL

WEBSITE”, carried out by Md.Noorain bearing University Roll No 2019/BCA/0022
respectively in partial fulfilment for the award of the degree of Bachelor of Computer
Application from University of Science and Technology Meghalaya.
They have worked under my supervision of our faculty, Department of Computer
Science. The report submitted is genuine & no part of this report has been submitted
anywhere for the degree from any University.

Dr.Bhairab Sharma
HOD

Department of Computer Science & Electronics

University of Science and Technology,

Meghalaya
UNIVERSITY OF SCIENCE &TECHNOLOGY
MEGHALAYA

CERTIFICATE FROM GUIDE

This is to certify that the project work, entitled “MONTFORT SCHOOL

WEBSITE” is a bonafide work carried out by MD Noorain, 6th semester student of three
years BCA program at University of Science and Technology Meghalaya. Under my
personal supervision and guidance. The report is worthy of acceptance for the major
project of BCA 6th semester.
All helps received have been duly acknowledged and no part of this report has
been reproduced for any other degree and diploma.

PRIYANKA SHARMA
Asst. Professor

Department of Computer Science & Electronics

University of Science and Technology,

Meghalaya
 SELF DECLARATION

This is to certify that the project work, entitled “MONTFORT SCHOOL WEBSITE” is a
bonafide work carried out by MD Noorain, 6th semester student of three years BCA program
under the guidance and supervision of Asst. Professor, Priyanka Sharma, Department of
Computer Science & Electronics, University of Science and Technology Meghalaya. This
dissertation has not been submitted in part or full in any other university for any degree.

MD NOORAIN

2019/BCA/0022

BCA 6th SEMESTER

 ACKNOWLEDGEMENT

I feel immense pleasure in expressing my sincere thanks and gratitude to my project guide
PRIYANKA SHARMA Sir Asst. Professor of Science & Electronics Department of University
of Science And Technology, Meghalaya for his valuable guidance and constant encouragement
throughout the entire project work entitled “MONTFORT SCHOOL WEBSITE” without
which this project would never been possible.

I also express my honest, thanks and gratitude to Mr.M Hoque, Chancellor of University
of Science And Technology, Meghalaya (USTM) for giving me the chance to complete BCA 6th
Semester under University of Science And Technology, Meghalaya. I also thank all other faculty
members for their kind co-operation and help to success my project. At last I also express my
thanks to all of my friends those who give me the constant inspiration for fulfillment of the
project.

MD NOORAIN

2019/BCA/0022

BCA 6th SEMESTER

 ABSTRACT

1. Title: The title of the project is "MONTFORT SCHOOL WEBSITE".

2. Aim of the Project: The main aim of the project is to develop such a system which will keep
the total information of the school with proper data and security.

3. Purpose: 6th Semester major project required for the partial fulfillment of BCA 6th semester
at USTM, MEGHALAYA.

4. Duration of the project: 5 and half months approx.

5. Session: 2019-22

6. Place of the project: MONTFORT SCHOOL, 10th Mile, Guwahati, Assam-781023

7. Project done by: MD NOORAIN

8. Roll No: 2019/BCA/0022

9. Guided by: PRIKANKA SHARMA

10. Software specification:

 Operating System: Microsoft Windows 7.

 FRONT END: PHP

 BACK END TOOL: MY SQL

 Design: HTML,CSS

11. Hardware specification:

 Intel core i3 based PCs.

 500 GB HDD.
 CONTENTS

Chapter 1: Introduction

 Introduction of the Project

 Objective of the Project

 Problem Statement

Chapter 2: Requirement Analysis

 Requirement Analysis

 Tools And Technology Used

Chapter 3: Analysis and System Design

 Introduction
 Logical Design
 Physical Design
 GUI Design
 Symbol used in DFD
 Context Diagram
 Dataflow diagram
 Entity- Relationship Modeling
 Symbol used in ER Diagram
 Entity-Relationship Diagram
 Data Dictionary
 Database Design
 Structure Chart

Chapter 4: System Testing and Testing Report

 Testing and Types

 Testing Report

Chapter 5: Documentation Future scope of the software

Conclusion

References
 LIST OF FIGURES

Serial No Figures Page No

1 Context Diagram
2 1st Level DFD
3 Entity Relationship Diagram
4 Structure Chart

LIST OF TABLES

Serial No Figures Page No

1 Context Diagram
2 Database Design
 CHAPTER 1

INTRODUCTION
 INTRODUCTION

Today computerized processing of data is an activity of almost every organization. Every

organization requires an efficient system that allows management to take decision based on
information gathered for the purpose.

The project website for Montfort School Guwahati controls all the information of the
school. The project is very helpful to provide the details , which are related to school faculty ,
admission procedure and also the various other facility offered by the school. The student can
apply for their admission and also give feedback.

AIM & OBJECTIVE

The main aim of the project is to develop such a system which will keep total information of the
school with proper data and security.

The objective of the system is to provide one platform where student can know all about the
school and decide if he/she should apply in it. If the student finds the school suitable for
themselves , then can also apply for it from the very same platform.

The Primary Objective Of The Project Are :

i. To Store all the information the school.

ii. To be able to apply for admission.
iii. To submit feedback from students.
iv. Update existing records.
v. Delete any unused data.
 PROBLEM STATEMENT

This project gives a detailed idea of the various aspects of maintaining process in an organization
bringing out the implementation of computerizing the data and supplying information .Even
though it appears simple to keep the data manually; in actual it is quite difficult to maintain the
data of the faculties. The main problem we face is the loss of data in form of papers due to
displacement or mishandling. Moreover data are always required to be updated which is not easy
to do with a little work force. And in such large firm it is very important to maintain the data
updated, accurate and in an organized manner.

The primary purpose of computerization of SCHOOL DESIGNING may be summarized as

follows:

 Ensure correct information of data.

 Ensure that data are not lost. Ensure easy update of data.

 Ensure quick retrieval of data.

 Ensure simple apply system.

 Ensure a simple system with greater advantages.

 Ensure real-life scenario.

 CHAPTER 2
REQUIREMENT ANALYSIS
 REQUIREMENT ANALYSIS

Requirement analysis is the first step in the system development life cycle. This requirement
emphasizes on the identification of the system as per as the end user is concerned. This is the
user or system adviser request to change, create, improve or enhance a manual or automated
existing system. During the preparation the initial information has to receive form customers and
service advisors. This helps in defining what are the requirements of the end user and goals of the
new system. The objective is to decide whether the request is valid and feasible to build a system.

Analysis is a detailed study of the various operations performed by a system and their
relationships with and outside the system. A key question is: What must be done to solve the
problem? One aspect of analysis is defining the boundaries of the system and determining
whether or not the system should consider other related systems. During analysis data are
collected on the available files, decision points, and transactions handled by the system. Data
flow diagrams and questionnaires are examples. Bias in data collection and interpretation can be
problem.

• Requirement gathering and analysis

• Requirement specification

Requirement gathering activity typically involves interviewing the end-users and service advisors
and studying the existing documents to collect all possible information regarding the system.

A requirement analysis involves obtaining a clear and through understanding of the system to be
developed.

The computer aided automation convenient and the efficient system of the Restaurant
management are only used by star restaurant management, but existing system can be applied to
general restaurant management, therefore the restaurant system that can be applied to general
management shall be develop fulfilling non-functional requirements such as

A. Input requirement

• Accuracy
• Consistency

B. Performance requirement

 The system shall be reliable

 If unable to process the request then appropriate error message shall display on the screen
 Responses to view information shall be quick

C. Safety requirement

 The details of the restaurant service and customer shall be maintain properly
  The database shall be keep backup

D. Security requirement

 Only authorized users can access the system with user_id/c_id and password
 TOOLS & TECHNOLOGIES USED

Software specification:
 Operating system: Microsoft Windows 10
 Front End Tool: PHP
 Design: HTML, CSS
 Back End Tools: MySQL

Hardware Specification:
 Intel core i3 based Pc
 1TB HDD
 4Gb RAM
 Mouse General
 Keyboard General
 CHAPTER 3
ANALYSIS & SYSTEM DESIGN
 ANALYSIS & SYSTEM DESIGN

INTRODUCTION:

System Design is a solution of "how to" approach to the creation of a new system. This important
phase is composed of many steps. It provides the understanding and procedural detail necessary
for implementing the system recommended in the feasibility study. Emphasis is on translating the
performance requirement into design specification.

Design is the most challenging and creative phase of the System Development Life Cycle
(SDLC). System Design includes detail concentration on the technical and other specifications
that make system operational. The System design goes through two phases of development.
These steps of development are:

1) Logical Design

2) Physical Design.

Logical Design:

Logical Design reviews the present physical system; prepares input and output specifications;
makes audit, security and control specification; details the implementation plan and prepares a
logical design walkthrough.

We know that the Data Flow Diagram shows the logical flow of the system and define the
boundaries of the system. Logical design specifies the user need at level of detail that virtually
determines the information flow into and out of the system and the required data resources.

Logical Design describes the inputs, outputs databases and procedures. All in format that
meets the user requirements.

Physical Design:

Input design is a critical part of any system design. Inaccurate input data are most common cause
of error in data processing. Data entry error can be controlled by input design. Input design is the
process of converting user oriented input to computer based formats. The goal of designing input
data is to make data entry as easy, logical and free from d errors as possible.

While entering data the operator needs to know the following:

 The allocated space for each field.

 Field sequence, which most match that in the source document.

 The format in which the adapt field entered

GUI Design:

The Graphical User Interface or GUI is a graphic based user interface that allows user to select
files, programs or commands by pointing to pictorial representation the screen rather than by
typing long, complex commands form a command prompt. GUI also provides additional
opportunities to enhance the interface of application system. The user interacts with the program
in What-you-see-is-what-you-get (i.e. WYSIWYG) fashion.

Programs operate within windows on the screen, so that more than one program can operate at a
time. Windows can drag around the screen, resized, maximized to fill the screen or minimized to
make them shrink down almost nothing, completely under the user's control.
SYMBOLS USED IN DATA FLOW DIAGRAM

TO SHOW THE INPUT AND OUTPUT

TO INDICATE A PROCESS

TO SHOW THE DATA FLOW

TO INDICATE STORAGE
CONTEXT DIAGRAM
1ST LEVEL DATA FLOW DIAGRAM
 ENTITY RELATIONSHIP DIAGRAM

As 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 in
regard to the organization of data within databases or information system.

As entity-relationship model (ER model for short) describe interrelated things of interest in a
specific domain of knowledge. A basic ER model is composed of entity types (which classify
the things of interest) and specifies relationships that can exist between instances of those entity
types.

In Software Engineering, an ER model is commonly formed to represent things that a business

needs to remember in order to perform business processes. Consequently, the ER model become
an abstract model, that define a data or information structure which can be implement databases,
typically a relational database.`

Entity-relationship modeling was developed for database design by peter hen and published in a
1976 paper. However, variants of the idea existed previously. Some ER models show super and
subtype entities connected by generalization relationships, and an ER model can be used also in
the specification of domain-specific ontology’s.
 SYMBOLS USED IN ER-DIAGRAM

SYMBOL MEANING

Strong entity

Weak entity

Attribute

Primary key attribute

Foreign key

Multivalve attribute
 Derived attribute

Composite Attribute

Relationship

Weak relationship

Total/Full participation

Partial participation

1:1
1:M Cardinality ratio

M:1
M:N
ER-DIAGRAM
 DATA-DICTIONARY

S.NO FIELD DESCRIPTION SOURCE TABLE

1 form_no Admission form no apply
2 A_charge Annual charge fee
3 A_fee Admission fees fee
4 Address Address apply
5 C_fee fee
6 Caste apply
7 Class apply
8 class student
9 Class fee
10 Cno student
11 Computer_fee fee
12 Dept teacher
13 Designation teacher
14 Dob student
15 doc apply
16 Email student
17 F_name apply
18 gender apply
19 Gender student
20 M_fee fee
21 M_name apply
22 msg feedback
23 N_date notice
24 N_file notice
25 N_name notice
26 N_no notice
27 Name feedback
28 O_fee fee
29 Phone feedback
30 Photo teacher
31 Qualification teacher
32 R_fee fee
33 Reg_no student
34 Religion apply
35 S_name apply
36 T_id teacher
37 T_name teacher
38 Taddress teacher
39 total fee
40 Tution_fee fee
 DATABSE DESIGN

1.apply

Field Name Data Type Size Key

form_no Varchar 10 Primary key
S_name Varchar 50 Not null
F_name Varchar 50 Not null
M_name Varchar 50 Not null
gender Varchar 10 Not null
Religion Varchar 50 Not null
Caste Varchar 50 Not null
Dob Varchar 50 Not null
Address Varchar 100 Not null
Cno Varchar 50 Not null
Email Varchar 50 Not null
Class Varchar 20 Not null
Studied_last Varchar 20 Not null
Photo Varchar 50 Not null
doc Varchar 50 Not null

2.student

Field Name Data Type Size Key

Reg_no varchar 40 Primery key
S_name varchar 50 Not null
F_name varchar 50 Not null
M_name varchar 50 Not null
Gender varchar 50 Not null
Dob varchar 50 Not null
Address varchar 100 Not null
Cno bigint 20 Not null
Email varchar 50 Not null
class varchar 50 Not null
3.teacher

Field Name Data Type Size Key

T_id varchar 40 Primary key
T_name varchar 50 Not null
Dept varchar 40 Not null
Gender varchar 40 Not null
Taddress varchar 50 Not null
T_cno bigint 20 Not null
T_email varchar 50 Not null
Qualification varchar 50 Not null
Designation varchar 50 Not null
Photo varchar 30 Not null

4.fee

Field Name Data Type Size Key

Class varchar 40 Primary key
R_fee decimal 10,2 Not null
A_fee decimal 10,2 Not null
C_fee decimal 10,2 Not null
A_charge decimal 10,2 Not null
Tution_fee decimal 10,2 Not null
T_fee decimal 10,2 Not null
M_fee decimal 10,2 Not null
C_fee decimal 10,2 Not null
Computer_fee decimal 10,2 Not null
O_fee decimal 10,2 Not null
total decimal 10,2 Not null

5.notice

Field Name Data Type Size Key

N_no Varchar 40 Primary key
N_name Varchar 50 Not null
N_file Varchar 50 Not null
N_date varchar 50 Not null
5.feedback

Field Name Data Type Size Key

Name Varchar 40 Not null
Email Varchar 50 Not null
Phone Bigint 20 Not null
msg varchar 100 Not null
 STRUCTURE CHART

A Structure chart (SC) in software engineering and organization theory is a chart which shows
the breakdown of a system to its lowest manageable levels. They are used in structured
programming to arrange program module into a tree. Each module is represented by a box, which
contains the module’s name.

MONTFORT SCHOOL
WEBSITE

FACULTY APPLICATION NOTICE APPLICATION

FEES
 CHAPTER 4
TESTING AND IMPLEMENTATION
 SOFTWARE TESTING

Software Testing is a method to check whether the actual software product matches expected
requirements and to ensure that software product is Defect free. It involves execution of
software/system components using manual or automated tools to evaluate one or more
properties of interest. The purpose of software testing is to identify errors, gaps or missing
requirements in contrast to actual requirements.

Some prefer saying Software testing as a White Box and Black Box Testing. In simple terms,
Software Testing means the Verification of Application Under Test (AUT). This tutorial
introduces testing software to the audience and justifies its importance.

Software Testing is Important because if there are any bugs or errors in the software, it can
be identified early and can be solved before delivery of the software product. Properly tested
software product ensures reliability, security and high performance which further results in
time saving, cost effectiveness and customer satisfaction.

The testing process can be illustrated using the following diagram:

UNIT TESTING

SUB-SYSTEM TESTING

SYSTEM TESTING

ACCEPTING TESTING
UNIT TESTING

Unit Testing is a software testing technique by means of which individual units of software i.e.
group of computer program modules, usage procedures and operating procedures are tested to
determine whether they are suitable for use or not. It is a testing method using which every
independent modules are tested to determine if there are any issue by the developer himself. It is
correlated with functional correctness of the independent modules.Unit Testing is defined as a
type of software testing where individual components of a software are tested.

Unit Testing of software product is carried out during the development of an application. An
individual component may be either an individual function or a procedure. Unit Testing is
typically performed by the developer.

In SDLC or V Model, Unit testing is first level of testing done before integration testing. Unit
testing is such type of testing technique that is usually performed by the developers. Although
due to reluctance of developers to tests, quality assurance engineers also do unit testing.

Objective of Unit Testing:

 To isolate a section of code.

 To verify the correctness of code.
 To test every function and procedure.
 To fix bug early in development cycle and to save costs.
 To help the developers to understand the code base and enable them to make changes
quickly.
 To help for code reuse.

Advantages of Unit Testing:

 Unit Testing allows developers to learn what functionality is provided by a unit and
how to use it to gain a basic understanding of the unit API.
 Unit testing allows the programmer to refine code and make sure the module works
properly.
 Unit testing enables to test parts of the project without waiting for others to be
completed.
SUBSYSTEM TESTING:

Subsystem verification testing is performed as a prelude to system testing. It is performed in the

operational environment using installed system hardware and software. Testing at the subsystem
level should be performed:

a. When different developers, vendors, or contractors have been responsible for delivering
stand-alone subsystems.
b. When the complete functionality of a subsystem could not be tested at a lower level
because it had not been fully integrated with the necessary communication infrastructure.
c. When it was previously impossible to connect to the field devices for the testing phase.

Testing at the subsystem level has distinct benefits over delaying that testing to the higher level
system testing:

 The test procedures and test personnel can concentrate on a limited set of system
requirements and functionality.
 Problems encountered during the test can be resolved independent of other testing.
 Testing can be completed in a shorter time span and with fewer resources and disruption
to other operations.
 Acceptance can be incrementally achieved and vendors paid for completed work.

SYSTEM TESTING:

System Testing is a type of software testing that is performed on a complete integrated system to
evaluate the compliance of the system with the corresponding requirements. In system testing,
integration testing passed components are taken as input. The goal of integration testing is to
detect any irregularity between the units that are integrated together. System testing detects
defects within both the integrated units and the whole system. The result of system testing is the
observed behaviour of a component or a system when it is tested. System Testing is carried out
on the whole system in the context of either system requirement specifications or functional
requirement specifications or in the context of both. System testing tests the design and
behaviour of the system and also the expectations of the customer. It is performed to test the
system beyond the bounds mentioned in the software requirements specification (SRS). System
Testing is basically performed by a testing team that is independent of the development team that
helps to test the quality of the system impartial. It has both functional and non-functional testing.
System Testing is a black-box testing.

Different Types of System Testing

There are more than 50 types of System Testing. For an exhaustive list of software testing types
click here.

Below I have listed types of system testing a large software development company would
typically use

1. Usability Testing– mainly focuses on the user’s ease to use the application, flexibility in
handling controls and ability of the system to meet its objectives
2. Load Testing– is necessary to know that a software solution will perform under real-life
loads.
3. Regression Testing– involves testing done to make sure none of the changes made over
the course of the development process have caused new bugs. It also makes sure no old
bugs appear from the addition of new software modules over time.
4. Recovery testing – is done to demonstrate a software solution is reliable, trustworthy and
can successfully recoup from possible crashes.
5. Migration testing- is done to ensure that the software can be moved from older system
infrastructures to current system infrastructures without any issues.
6. Functional Testing – Also known as functional completeness testing, Functional Testing
involves trying to think of any possible missing functions. Testers might make a list of
additional functionalities that a product could have to improve it during functional testing.
7. Hardware/Software Testing – IBM refers to Hardware/Software testing as “HW/SW
Testing”. This is when the tester focuses his/her attention on the interactions between the
hardware and software during system testing.
WHITE BOX TESTING:

White Box Testing is software testing technique in which internal structure, design and coding
of software are tested to verify flow of input-output and to improve design, usability and security.
In white box testing, code is visible to testers so it is also called Clear box testing, Open box
testing, Transparent box testing, Code-based testing and Glass box testing.
It is one of two parts of the Box Testing approach to software testing. Its counterpart, Black box
testing, involves testing from an external or end-user type perspective. On the other hand, White
box testing in software engineering is based on the inner workings of an application and revolves
around internal testing.

The term “White Box” was used because of the see-through box concept. The clear box or White
Box name symbolizes the ability to see through the software’s outer shell (or “box”) into its inner
workings. Likewise, the “black box” in “Black Box Testing” symbolizes not being able to see the
inner workings of the software so that only the end-user experience can be tested.

Advantages of White Box Testing

 Code optimization by finding hidden errors.

 White box tests cases can be easily automated.
 Testing is more thorough as all code paths are usually covered.
 Testing can start early in SDLC even if GUI is not available.

Disadvantages of White Box Testing

 White box testing can be quite complex and expensive.

 Developers who usually execute white box test cases detest it. The white box testing by
developers is not detailed can lead to production errors.
 White box testing requires professional resources, with a detailed understanding of
programming and implementation.
 White-box testing is time-consuming, bigger programming applications take the time to
test fully.
BLACKBOX TESTING:

Black Box Testing is a software testing method in which the functionalities of software
applications are tested without having knowledge of internal code structure,
implementation details and internal paths. Black Box Testing mainly focuses on input and
output of software applications and it is entirely based on software requirements and
specifications. It is also known as Behavioral Testing.

Types of Black Box Testing

There are many types of Black Box Testing but the following are the prominent ones –

 Functional testing – This black box testing type is related to the functional requirements
of a system; it is done by software testers.
 Non-functional testing – This type of black box testing is not related to testing of
specific functionality, but non-functional requirements such as performance, scalability,
usability.
 Regression testing – Regression Testing is done after code fixes, upgrades or any other
system maintenance to check the new code has not affected the existing code.

Tools used for Black Box Testing:

Tools used for Black box testing largely depend on the type of black box testing you are doing.

 For Functional/ Regression Tests you can use – QTP, Selenium

 For Non-Functional Tests, you can use – Load Runner, Jmeter

Acceptance Testing:

Acceptance Testing is the final level of software testing. The main aim of this testing is to
determine the working process of the system by satisfying the required specifications and it is
acceptable for delivery. It is also known as End-User Testing. It also works under the Black Box
Testing Method.

Types of Acceptance Testing:

User Acceptance Testing (UAT): The name itself says that it is from the user point of view. It
helps to determine whether the system is working for the user with the given specific
requirements. Here, the user refers to whom the system is going to handle after completion of all
the testing levels. Usually, customers or customer’s customers will perform this testing.

Business Acceptance Testing (BAT): It helps to check whether the system satisfies the
business requirements and specifications. The main aim of this testing is to help in increasing
business profits by considering market strategies and technologies.

Contract Acceptance Testing (CAT): The name itself says that it helps to test the product with
all acceptance test cases within the contract period of time. The contract may be like payment
will be done before the product goes live or after the product goes live.

Regulation Acceptance Testing (RAT): If testing undergoes all the rules and regulations that
are released by the government then it is said to be RAT. Not even a single violation has not to
be found while performing this testing if any occurs then the whole product will be going under
failure. So, it is the most important and complicated testing type.

Operational Acceptance Testing (OAT): This testing mainly used to determine the product’s
compatibility, reliability, stability, etc., before it is going to live.

Alpha Testing: Specialized Testers will perform this testing to check any bugs have occurred.
Also, they help to give suggestions to improve product usability in a controlled manner.

Beta Testing: Beta Testing helps to grab the bugs or any issues of a product. End-Users will
perform this testing with an uncontrolled manner.
 CHAPTER 5
DOCUMENTATION