Table of Contents

Sr. No. Description Page

No.

1.0 Introduction 4-5

1.1 Purpose 6
1.2 Scope 7

1.3 Definition, Acronyms, and Abbreviations 7

1.4 References 8
1.5 Technologies to be used 9

1.6 Overview 10
2.0 Overall Description 11
2.1 Product Perspective 11

2.2 Software Interface 12

2.3 Hardware Interface 12

2.4 Product Function 13

2.5 User Characteristics 13

2.6 Constraints 14

2.7 Architecture Design 14

2.8 Use Case Model Description 15

2.9 Class Diagram 16

Sequence Diagrams
2.10 Database Design 17-20

2.11.1 ER Diagram 21-22

2.11.2 Schema
2.12 Assumptions 23
and
 Dependencies
3.0 Specific Requirements 23
3.1 Use Case Reports 23-25
3.2 Supplementary Requirements 26
 Abstract

The project “ONLINE NOTIFICATIONS” assists the students in posting

and reading academic articles , Subjective notes.Using this online system , one can
can enhance technicual as well as subjective knowledge by reading articles . you can
manage all your information from a single database file. Within the file, divide your
data into separate storage containers called tables; view, add, and update table data
using online forms; it includes forums, Post and comments and some FAQs on the
related topics, through which we can create networking with other existing users.

This website includes the whole profile of the GPT students, it also gives the
relevant information or notices about various events to the students of GPT. This
website uses the Java platform for the development of the project. It is made very user
friendly and easy to use.
 ACKNOWLEDGEMENT

We are greatly indebted to my/our seminar guide guide’s name for his/her able
guidance throughout this work. It has been an altogether different experience to work
with him/her and we would like to thank him/her for his/her help, suggestions and
numerous discussions.

We gladly take this opportunity to thank Dr. Mrs. Rajurkar A. M. (Head of

Computer Science & Engineering, MGM’s College of Engineering, Nanded).

I/We are heartily thankful to Dr. Mrs. Lathkar G. S. (Director, MGM’s College of
Engineering, Nanded) for providing facility during progress of seminar; also for her
kindly help, guidance and inspiration.

Last but not least we are also thankful to all those who help directly or
indirectly to develop this seminar and complete it successfully.

With Deep Reverence,

GOVINDA KANKAL
SURAJ KAWADKAR
[TECSE-I]
 Chapter 1

Introduction

1.1 Project definition: Online Notification

Online Notification is a forum where college students and faculties can post
and read various articles, thus promoting literary insight. Articles can be searched by
anybody in the world.

The Program can also include feature of categorizing articles, one can give
feedback, Rate the article, one can Search article by category or topic as well. Topics
get sorted by constraint of most viewed and tags are attached to article by number of
reads.

The project is an effort to build a professionally look /featured online forum,

with an user friendly Interface and lot of features to grab visitors and provide them lot
at a place.

Creating and managing an Online Notification where college students and

faculties can post and read various articles, thus promoting literary insight. Articles
can be searched by anybody in the world.

When a project is started an initial investigation is carried out. During this

phase of study users need has recognized and other requirements are determined.
Once the problem has been defined a study is carried out to select the best system i.e.
a feasible system that meets performance requirements. So Feasibility is the
determination of whether or not a project is worth doing and the process followed in
making this determination is called a Feasibility Study. In order to conduct the
feasibility study we have seven distinct, but inter-related types of feasibility, these are
Technical feasibility, Operational feasibility, Economical feasibility, Social
feasibility, Management feasibility, Legal feasibility and Time feasibility.

This is concerned with specifying equipment (hardware) and software that will
successfully satisfy the user requirement. It considers the following facts:

 The facility to produce outputs in a given time.

 Response time under certain conditions.

 Ability to process a certain volume of transaction at a particular speed.

 Facility to communicate data to distant location.

While examining technical feasibility, huge importance is given to the

configuration of the proposed system. The configuration should give the complete
picture about the system’s requirement such that what kind of hardware is required
and how these units are interconnected so that they could operate and communicate
smoothly.

Configurations will be pursued that satisfies the key technical requirements

but represent different levels of ambition and cost.

Since cost plays quite an important role in deciding the new system, it must be
identified and estimated properly. So economic analysis is the most frequently used
technique for evaluating the effectiveness (economical feasibility) of a proposed
system. To determine the economical feasibility of the system a cost/benefit analysis
is to make. This procedure is to determine the benefits and savings that are expected
from a proposed system and compare them with costs. Four facts that play an
important role in deciding economical feasibility of the proposed system are as
follows:

 Cost-saving benefits

 Cost-avoidance benefits

 Improved-performance benefits

 Improved - information benefits.

Hence the proposed system is economically feasible.

It is mainly related to human organizational aspects. The points to be considered are:

 What changes will be brought with the system?

 What organizational structures are disturbed?

 What new skills will be required?

 Do the existing Employees members have these skills if not, can they be trained?

1.2 EXISTING SYSTEM:

The existing systems of Online Notification of various colleges provides lots

of features but all these Websites are public. Anyone can have an account on these.
Such Websites are not secured for updation of critical information about college. Due
to this, a private Website for College has been established. Only Administrator can
post Article earlier but now student can also share ideas.

1.3 PROPOSED SYSTEM:

Online Notification website has various benefits with which we all are quite
familiar. The proposed system has been established for college students, faculty and
guests. In this Website, only the authorized users can login. Many features like all
other Websites has been tried to be implemented. The flexibility of this system will
definitely help Students to communicate with each other very easily.

2.3 Purpose:
Creating and managing an Online Notification where college students and
faculties can post and read various articles, thus promoting literary insight. Articles
can be searched by anybody in the world. Factors behind the motivation of this
system are:

1. Not all students make it to the printed magazine.

2. Creativity of students needs to be nurtured.

Creating a user-friendly interactive place where students/faculties can share their

ideas.

1.2 Scope:

 The Scope of the ONLINE NOTIFICATION includes:

User must have a valid User Id and password to login to the system.
 If a wrong password is given thrice in succession, that account will be locked and the

 customer will not be able to use it. When an invalid password is entered a warning is
given

to the user that his account is going to get locked.

 Search Engine for all the articles posted till date. Accessible by anybody.

 Essential steps to be taken to prevent authenticity infringement.

 Articles to be distributed in categories. Can overlap 2 or more categories. Articles to

be associated with suitable tags by the registered users at the time of posting, so that
they are searchable.

 The home page to consist of attractive essential features like: most read articles,
editor’s pick, recently posted articles, highest rated articles, article of the month,
college news, etc.

 Archives to be maintained.

 Interactive feedback to be supported to enhance the user experience.

 Guests can read articles, rate them and comment on them. They can also access other
optional features (amenities like Word of the day, etc.) but can’t post articles unless
they sign in as registered users.

 Automatic commenting on articles by spammers/automatic bots to be defied.

 College Students/Faculties can only register as members (through unique IDs).

 Alumni registration to be supported.

 Registered members, Moderators and Administrators are allowed to post articles.

 Articles can be downloaded in various formats.

 Registered users, Moderators, and Admins will have their own profile, where they can
edit info for the world to see. Useful “updated” info related to their activities to be
available at their profiles.
Chapter 2

Requirement Analysis and Specification Analysis

2.1 Specific Requirements

2.1.1 Admin use-case report

Fig 2.1.1 Admin use-case report

Description:

The admin can perform the functions which are displayed above. The admin
takes care of the server upgrade and maintenance, website security to prevent
spamming and hacks. The admin also takes care of the design and analysis of the
website with the moderator. The role of selecting the moderators and updating them is
done by the administrator. He creates a backup of the entire data of the website on a
separate cloud for security purposes.
2.1.2 Alumni use case report

Fig 2.1.2 Alumni use case report

Description:

The alumni will enjoy limited functions on the website. The alumni can report
articles, view profile of professors, rate articles, and edit his own profile.

2.1.3 Guest use case report

Fig 2.1.3 Guest use case report

Description:

The guest does not enjoy all benefits like a registered user. The guestfunctions
will be limited to viewing articles and viewing the campus news. The guest cannot
rate or comment on articles posted on the online magazine website.

2.2 Registered users use case report

Fig. 2.2.1 Registered users use case report

Description:

A registered user enjoys maximum privileges on the online website. The

registered user category belongs to current students and faculty. The registered user
can have his own profile, rate and comment on articles which are posted. Submitting
articles and updating the profiles are also a part of the functions which the registered
user can perform.
2.3 Moderator use case report

Fig 2.3.1 Moderator use case report

Description:
The moderator forms the centre of the entire scenario of the online magazine
website. He has various functions to perform. The moderator posts the word of the
day on the website, updates the campus news and events, posts thought of the day and
update the library section. The moderator will also, confirm membership, and will
have the privilege of disabling a profile and renewing the password if required. The
moderator can block certain offensive articles of required. The final verdict of
selecting the article or rejecting it lies with the moderator. Hence, the moderator
forms the most import part of the use case diagram.
2.4 Class Diagram

Fig.2.4.1 Class Diagram

2.5 Sequence Diagrams

2.5.1 Sign-up Sequence

Fig 2.5.1.1 Sign-up Sequence

2.5.2 Report Article Sequence

2.5.2.1 Fig Report Article Sequenc

 2.5.3 Article posting Sequence

Fig 2.5.3.1 Article posting Sequence

2.6 Use Case

Reports:
Administrator :-

o He is the super user responsible for managing clients of the system, taking system
backup, generating reports, maintaining organization details.

 Manage Clients: The Administrator assigns new users when a new client joins the

 online magazine. Also he can delete an account when any of the clients leave the
college
 organization.

 Maintain Organization Details: The Administrator maintains entire details of the

organization that includes details of the clients, entrepreneur details etc.

 Take System Backup: The Administrator Backup the database in order to prevent

loss of data on system crashes. He can backup entire database or a particular section..

 Generate Reports: : Responsible for checking the logs of different system users for
 and maintaining the integrity of the system.

Manage Clients :-

 Name Of Use-Case: Manage clients.

 Description:

 The Administrator assigns new users when a new client joins the online
 bank. Also he can delete an account when any of the clients leave the bank
organization.

 Preconditions:

 Administrator is already logged in.

Create account

Manage client

Delete account

 Name Of Use-Case: Maintain organizational details

 Description: The Administrator should maintain all the organizational details.

 Preconditions:

o Administrator is already logged in.

 Entrepreneur_details

details

client_details

 Name Of Use-Case: Take System backup.

 Description: The Administrator Backup the database in order to prevent loss of data

 on system crashes. He can backup entire database or a particular section.

 Preconditions:

 Administrator is already logged in.

 Name Of Use-Case: Generate Reports.

 Description: The Administrator is responsible for checking the logs of different

clients

 for auditing and maintaining the integrity of the system.

 Preconditions:
 Administrator is
already
 logged in.

Customer :
Ordinary customers have a user name & password with which they can login into
their account.

 Name Of Use-Case: Login.

 Description: Customer must provide a valid User Id and password to login to the

 System

 Preconditions:

 Customer must have a valid User Id and password to login to the system.

2.7 Supplementary Requirements:

2.7.1 Performance Requirements

System can withstand even though many no. of customers request the desired
service. Access is given to only valid users of college who requires the services such
as upload article, download article, newsletters, thoughts of day ,etc.

2.7.2 Safety Requirements

By incorporating a robust and proven DB2 UDB into the system, reliable
performance and integrity of data is ensured. There must be a power backup for
server system. Since the product is of 24x7 availability there should be power backup
for server which provides the information .Every day the data should be backup even
when the operation of an user is not successful i.e., while performing the operation
power failure occurs then data sho

2.7.3 Overview:

 The SRS will include two sections, namely:

 Overall Description: This section will describe major components of the system,
 interconnections, and external interfaces.

 Specific Requirements: This section will describe the functions of actors, their
roles in the system and the constraints faced by the system.

2.8 E-R DIAGRAM

 Fig 2.8.1 E-R DIAGRAM

2.9 Use Case Diagram :

Description and the priority of this system :-

When we consider the online Notification in this we provide the details of

how to access the magazine without going to the bank through internet.

When we consider the priority of this project it is mainly of medium cost,

efficient

to user access data, provides the required data, safe and secure one .we can know the

details of our account

Fig 2.9.1 Use Case Diagram
Chapter 3

Implementation

3.1 Definitions, Acronyms, and Abbreviations:

•HTML (Hyper Text Markup Language): It is used to create static web pages.

•DBMS(Database Management System ): It is a database management

system that provides a flexible and efficient database platform to raise a
strong "on demand" business applications.

3.2 Product Perspective:

The client will have client interface in which he can interact with the banking

system. It is a web based interface which will be the web page of the banking

application. Starting a page is displayed asking the type of customer he is whether

ordinary or a corporate customer. Then the page is redirected to login page where

the user can enter the login details. If the login particulars are valid then the user

is taken to a home page where he has the entire transaction list that he can perform

with the bank. All the above activities come under the client interface.

The administrator will have an administrative interface which is a GUI so that he

can view the entire system. He will also have a login page where he can enter the
login

particulars so that he can perform all his actions. This administrative interface
provides

different environment such that he can maintain database & provide backups for the

information in the database. He can register the users by providing them

withusername
,password & by creating account in the database. He can view the cheque book
request

& perform action to issue the cheque books to the clients.

 3.3 Interface

3.3.1 Software Interface:

 User on Internet : Web Browser, Operating System (any).

 Application Server : WAS

 Data Base Server : DB2

 Network : Internet

 Development Tools : WSAD (J2EE,Java,Servlets,HTML), DB2, OS(Windows),

3.3.2 Hardware Interface:

CLIENT SIDE

Processor Ram Disc Space

Internet Explorer Intel core I3 4 GB 1 TB

7.0

SERVER SIDE

Web sphere Intel core I3 4 GB 1 TB

application server

V5.0

DB2 V8.1 Intel core I3 4 GB 1 TB

 (Excluding data
size)

3.4 Product Functions:

 Search Engine for all the articles posted till date. Accessible by anybody.
 Essential steps to be taken to prevent authenticity infringement.
 Articles to be distributed in categories. Can overlap 2 or more categories. Articles to
be associated with suitable tags by the registered users at the time of posting, so that
they are searchable.

 The home page to consist of attractive essential features like: most read articles,
editor’s pick, recently posted articles, highest rated articles, article of the month,
college news, etc.
 Archives to be maintained.
 Interactive feedback to be supported to enhance the user experience.
 Guests can read articles, and comment on them. They can also access other optional
features (amenities like Word of the day, etc.) but can’t post articles unless they sign
in as registered users.

 College Students/Faculties can only register as members (through unique IDs).

 Alumni registration to be supported.

 Registered members and Administrators are allowed to post articles.

 Articles can be downloaded.

 Registered users, and Admins will have their own profile, where they can edit info for
the world to see. Useful “updated” info related to their activities to be available at
their profiles.
 Moderators will have associated categories, according to which to-be-validated-
articles will be posted to them on their profiles. On rejection, he will have to provide a
reason for the same, which will be forwarded to the concerned user.

 Mails to be sent on rejection/acceptance of articles.

3.4 User Characteristics:

User should be of particular college. He/she should be student or faculty Of that

college. They can post articles,download articles,etc.

3.5 Constraints:
 Login and password is used for identification of customer’s account and there is no
facility for non users to login.
 This system works only on a single server.
 GUI is only in English
 Limited to HTTP/HTTPS protocols
3.6 Activity Diagram For Overall System

Fig 3.6.1 Activity Diagram For Overall System

3.6.2 User login Activity

Fig 3.6.2.1 User login Activity

Description:
The user enters a username and password. If the username and password is
verified then the user login is successful and user is redirected to the home-page. If
the login is not successful then the user can either renter his password and username
(the user can do this for only a maximum of 3 times) or he can click on forgot
username/password. Then a security question is asked. If that is verified, then an
email is sent on the user's mail id else the request is forwarded to the admin.
3.6.3 Managing Accounts Activity

Fig 3.6.3.1 Managing Accounts Activity

Description:

 A registered user (admin, moderator, alumni, faculty, student) can manage

their accounts by doing the following
 Change password

 Delete account

 Edit details
3.6.4 Rate and comment activity

Fig 3.6.4.1 Rate and comment activity

Description:

If a user is a registered user then he can comment or rate an article

but if it is guest then he cannot rate or comment an article. This shows that
an alumni will not be able to comment or rate on an article.
3.6.5 Report Comment Activity

Fig 3.6.5.1 Report Comment Activity

Description:

If the user is a registered user then he can report a comment. Then a

notice is forwarded to moderator to report the comment. The moderator can
either remove the comment or ignore the request to report that comment. In
case the user is a guest then he cannot report a comment.
3.6.6 Registration Activity

Fig 3.6.6.1 Registration Activity

Desciption :

Initially student/faculty is made to fill mandatory fields filled in registration form.

Once the user clicks submit, the details are verified. If the details are incomplete then
t he user is informed to fill the complete details and is redirected to the page where the
details have to be filled. If the details that are filled are complete then it is checked
whether it’s a new user or already existing user. If its an already existing user then the
user is asked to renter the details. If it is a new user then the user will create a
username and a password. Then if it is a valid username and password then he/she
is registered and is redirected to the home page.
 3.6.7 Submit Article Activity

Fig 3.6.7.1 Submit Article Activity

Description:

If a user intends to post an article then he creates article and submits it in the
appropriate category. The article is then received by the moderator of that particular
category in which the article has been added . The moderator can

 reject the article if he founds some unacceptable stuff in it

 he can simply approve the article

 he can put the article in a different category if he feels the article is not apt for the
category it was submitted for. Then this is verified by the user who submitted the
article. The user can either verify the category change or submit the article or he does
not verify the category change and withdraws the article.
 Chapter 4
Language Implementation and Results
4.1 Database Design:

Following Tables are created in first module:

How to Write Test Cases: Sample Template with Examples

 What is a Test Case?

A Test Case is defined as a set of actions executed to verify a particular feature or
functionality of the software application. A test case is an indispensable component of
the Software Testing LifeCycle that helps validate the AUT (Application Under Test).

 Test Scenario Vs Test Case

Test scenarios are rather vague and cover a wide range of possibilities. Testing is all
about being very specific.
For a Test Scenario: Check Login Functionality there many possible test cases are:
 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 a User ID is Empty & Login Button is
pressed, and many more
This is nothing but a Test Case.

Login

Field Name DataType Size Key Description

Username Varchar 20 Primary key User name

Password Varchar 20 password

4.1.1 Login table

users

Field Name DataType Size Key Description

 id Varchar 20 Name

username Varchar 20 name

Firstname Varchar 100 name

Lastname Varchar 20 name

email Varchar 30 Primary key email

password Varchar 20 password

4.1.2 User table

Posts

DataType Size Key

Id Int 10 Primary Key

Title Char 50

Author Char 50

Postdate Varchar 20

Image Clob

Content Varchar 150

Update_on Date

Status Varchar 20

Tag Varchar

4.1.3 Posts table

Chapter 5

Test Cases-Results
How to Write Test Cases: Sample Template with Examples
What is a Test Case?
A Test Case is defined as a set of actions executed to verify a particular
feature or functionality of the software application. A test case is an
indispensable component of the Software Testing LifeCycle that helps
validate the AUT (Application Under Test).

Test Scenario Vs Test Case

Test scenarios are rather vague and cover a wide range of possibilities.
Testing is all about being very specific.

For a Test Scenario: Check Login Functionality there many possible test
cases are:

 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 a User ID is Empty & Login
Button is pressed, and many more

This is nothing but a Test Case.

Step 1) A simple test case for the scenario would be

Test Case # Test Case Description

1 Check response when valid email and password is entered

Step 2) In order to execute the test case, you would need Test Data. Adding it below

Test Test Case Description Test Data

Case #

1 Check response when valid email Email: abc@email.com Password:

and password is entered lNf9^Oti7^2h

Identifying test data can be time-consuming and may sometimes require creating test
data afresh. The reason it needs to be documented

Te Test Case Description Test Data Expected

st Result
Ca
se
#

1 Check response when valid email Email: abc@email.co Login

and password is entered m should be
Password: successful
lNf9^Oti7^2h

Te Test Test Data Expected Actual Pass/F

st Case Result Result ail
Ca Descrip
se tion
#

1 Check Email: abc@email.com  Login should be Login Pass

respons Password: successful was
e when lNf9^Oti7^2h success
valid ful
email
and
passwor
d is
 entered

Step 3) In order to execute a test case, a tester needs to perform a specific set of
actions on the AUT. This is documented as below:

Test Test Case Description Test Steps Test Data

Case #

1 Check response when valid email 1) Enter Email Email:abc@email.com

and password is entered Address Password:
2) Enter lNf9^Oti7^2h
Password
3) Click Sign in

Many times the Test Steps are not simple as above, hence they need
documentation. Also, the author of the test case may leave the organization or
go on a vacation or is sick and off duty or is very busy with other critical tasks.
A recently hire may be asked to execute the test case. Documented steps will
help him and also facilitate reviews by other stakeholders.

Step 4) The goal of test cases is to check behavior the AUT for an expected result.
This needs to be documented as below

Step 5) That apart your test case -may have a field like, Pre - Condition which
specifies things that must in place before the test can run. For our test case, a pre-
condition would be to have a browser installed to have access to the site under test. A
test case may also include Post - Conditions which specifies anything that applies
after the test case completes. For our test case, a postcondition would be time & date
of login is stored in the database

5.1 Login Testcases

Test Case ID 1 Test Case Description Test the login functionality in magazine
Created By pradeep Reviewed By sajjad Version 2.1

Tester's Name sajjad Date Tested September 8, 2019 Test Case Pass
and (Pass/Fail/Not
pradeep Executed)

S# Prerequisites: S# Test Data

1 Access to Chrome Browser 1 Userid = superadmin

2   2 Pass = superadmin

3   3  

4   4  

Test Verify on entering valid userid and password, the customer can
Scenario login

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended

1 Navigate to homepage window homepage pass

localhost/demo9

2 Enter Userid & Credential can be As Expected Pass

Password entered

3 Click Submit Cutomer is logged in As Expected Pass

4        

         

         

5.2 Posts testcases

Test Case ID 1 Test Case Test the post functionality in posts section
Description

Created By Pradeep Reviewed By sajjad Version 2.1

Tester's Name sajjad and pradeep Date Tested October 8, 2019 Test Case Pass
(Pass/Fail/Not
 Executed)

S# Prerequisites: S# Test Data

1 Access to Chrome Browser 1 Userid = superadmin

2   2 Pass = superadmin

3   3  

4   4  

Test Verify on entering valid userid and password, the customer

Scenari can login
o

Step # Step Details Expected Results Actual Results Pass / Fail / Not executed /
Suspended

1 Navigate to localhost/demo9/posts posts window posts window pass

2 Enter project desciption and title and posts shown on post posts shown on post window Pass
upload image window

3 Click Submit post displayed As Expected Pass

4        

         

         

Chapter 6
Conclusion
I learned a lot by doing this project :

 Web Browser: Google Chrome, Mozilla Firefox

 Languages used: HTML, CSS, JAVA SCRIPT, PHP,Bootstrap

 Servers Used: XAMP Server

 Database: MySQL
 So during this project I learned all the above things. Before this
project, I had no idea about Java Script, PHP and MySQL for making a web
application. Although I had little bit knowledge of HTML and CSS before.
But now I learned a lot about Java Script, PHP and MySQL and got
knowledge of using Java Script, PHP and MySQL for developing web
application. Now I prefer to work on command line rather than graphically. I
learned how to work on XAMP Server. If I talk about the project, Online
Notifications has reduced lot of manual work. It has made notifying each and
every user very easy and that too with no time and place restrictions
The future scope of the project is that it can be used as any news giving application or
it can be used to advertise your products, telling the customers about new schemes
and products coming to your shop. This application of Online Notice Board can be
further extended to include the following features:
1. Categorization of Notice: Notices can be categorized in different categories, so that
it’s possible for user to easily manage the notices. Categorization can also be done by
making groups. Defining the notice to be circulated in a particular group can make it
more secure.
2. Documents and PDF files: The attachments can be further improved to include PDF
files or Doc files. Then there will not be much need to send images with the notices.
A single file would serve all the purposes.
3. Feedback:Feedback on the notices can also be taken. It can increase communication
among connected members and any issue can be easily sorted out on the spot.

References

 Feasibility Analysis Guide, Department of Computer Science, Cornell

University

 Drewry, Tony, Logical Data Structures (LDSs) - Getting started, University of

West of England, 2005

 Prof. H. Levent AKIN, Department of Computer Engineering, Boğaziçi

University, Istanbul, Turkey

 IEEE Recommended Practice for Software Requirement Specifications, IEEE

Standard 830–ISM4331
 IEEE Recommended Practice for Software Design Descriptions, IEEE Standard
1016–1998

 https://www.w3schools.com/php/default.asp

 https://www.tutorialspoint.com/php/index.htm

 https://www.w3schools.com/php/php_mysql_intro.asp

 https://en.wikipedia.org/wiki/PHP