CRM FINAL DOCS changes(1)
CRM FINAL DOCS changes(1)
PROJECT REPORT
ON
“Academic CRM”
SUBMITTED
TO
THROUGH
THE HEAD OF DEPARTMENT
YSPM’S YASHODA TECHNICAL CAMPUS,
SATARA
A.Y 2024-2025
Yashoda Shikshan Prasarak Mandal’s
YASHODA TECHNICAL CAMPUS, SATARA
Faculty of MCA
A.Y 2024-25
Vision Statement:
Mission Statement:
1. "To provide students and faculty with continuous learning opportunities, enabling them to
2. acquire higher qualifications and expertise in the field of computer applications."
3. “To deliver quality education through innovative teaching methods, fostering academic
competency, credibility, research and integrity in computer application.”
4. “To prepare students with the skills and mindset to address the evolving needs of the
industry and society.”
1. PEO I: Technical Expertise: Implement fundamental domain knowledge of core courses for
developing effective computing solutions by incorporating creativity andlogical reasoning.
2. PEO II: Successful Career: Deliver professional services with updated technologies in
Computer application based career.
3. PEO III: Interdisciplinary and Life Long Learning: team work with effective
communication & time management in the profession. Undergo higher studies,
certifications and technology research as per market needs.
Certificate
Place: Satara
Date:
DECLARATION
Place: Satara
Date:
Signature
Place: Satara
Date:
Signature
Mr. Ajinkya Milind Jagtap
INDEX
Sr. No Content Page No.
INTRODUCTION TO PROJECT
1.1 Introduction
1 1.2 Existing System 1-4
1.3 Need and scope of Computer System
1.4 Organization Profile
PROPOSED SYSTEM
2 2.1 Objectives 5 - 10
2.2 Requirement Engineering
SYSTEM DIAGRAM
3.1 Data Flow Diagram(DFD)
3 3.2 Entity Relationship Diagram(ERD) 11 - 21
3.3 Use Case Diagram(UCD)
3.4 Activity Diagram
3.5 Sequence Diagram
SYSTEM DESIGN
4.1 Database Design
4 22 - 46
4.2 Input Design & its samples
4.3 Output Design (on screen)
IMPLEMENTATION
5.1 System Requirement - Hardware – Software
5 47 -51
5.2 Installation process
5.3 User Guideline
REPORTS 52 -54
6
CONCLUSION AND SUGGESTIONS
7.1 Conclusion
7 55 - 56
7.2 Limitations
7.3 Suggestion
ANNEXURES
8.1 Source Code
8 8.2 Joining Report, Progress Report, Student 57 -73
65-
guide Meet Record
REFRENCES 74
9
YSPM’S YTC, Faculty of MCA, Satara.
Academic CRM
1.1 Introduction:
relationships to give enterprises a competitive edge in the market. Robust and feature-rich
custom Academic CRM software enables businesses of any size to overcome most
in India, we believe that creating and integrating an advanced Academic CRM software
solution is one of the integral parts of an organization’s growth. With our rich experience
communication. Integrated with all these features and high-end data analysis tools.
The existing system is a manual system. The module is designed to replace manual
system and make data storage easy and reliable.
The system is designed in such a way that it overcomes the drawbacks of
existing manual system. The drawbacks of existing manual system are following below.
Lot of paper work and storage space is needed to keep backup or information.
The Organization does not any computer system, all work done manually
by the people in the organization. The records are maintained in file and all required
documents are written manually by the organization. The record store in file is creating a
hectic in the office and therefore there is need for the computerization.
Its advantages as described as below :
Due to computerization system become error less, as well as file become easy, so
that computerization is easy.
The Scope of system are boundaries of system, here this system helps the
Admin to maintain large data about users,client,vendor and payment entries details
also Employee to maintain large data about Candidate and enquiries,clients,vendors
and Account & Finance department.
Managing Client Details :- All registered client details can be managed easily.
Managing Vendor Details :-All registered vendor details can be managed easily.
Payment Entry Details:-The Business Petty cash entry, Client payment entry,
Employee payment entry,Vendor payment entry details are stored.In petty cash
product rate and product quantity according to product bill is automatically
calculated.In Client/Vendor/Employee payment entry the payment mode option is
available in that Net-banking, Cash, Cheque and UPI payment any one of them
transaction details stored easily.
Email id : [email protected]
Goals : Anvistar ITS Pvt. Ltd. is one of the Private Company, which
deals in the development ACADEMIC CRM.
2.
The main objectives of the proposed desktop application are to reduce the
manual work and making easy.
The system removes possibility of any erroneous reading to occur as it first
validates the fed it reduce manual paperwork.To provide fast access.This system is time
saving.
The proposed system effectively maintains whole data.The system works
fast,save time and gives more accurate data processing .The Academic CRM system
provide best services to Customers by maintaining a many details securely.
This system is helpful to store all records of employees,clients and vendors
are stored and managed easily.
This desktop application can be accessed by admin and employee.Using this
system maintaining all records effectively.This desktop application is useful for quickly
access the data of any registered clients,employee , vendor or even the payment entry details.
Academic CRM system is designed to achieve one or more objectives. The main
objective of
that system to overcome some problems that comes during existing system.
The main objective of the project is to develop software that facilitates the data storage
and data maintenance.
To store the record of the candidate,client, and vendor , the employee (user) that has
the privileges to access, modify and delete any record.
2.2Requirement Engineering:
The process to gather the software requirements from client, analyzed and document
them is known as requirement engineering.
The goal of requirement engineering is to develop and maintain sophisticated and
descriptive system requirements specification.
Requirement Engineering Process : It is a four step process, which included.
1. Requirement Gathering.
2. Fact Finding Techniques
3. Feasibility Study
4. Software Requirement Specification.
2.2.1
This is the first important phase for the project development. In that
I’am note down what are expectations and information about the project of Academic
CRM and on this basis of the requirements I have made a list of requirements.
1) Security:
2) Reliability:
3) Maintainability:
4) Availability:
5) Portability:
C. Feasibility Study :
The Feasibility Study is the one that lets our proposed work to put into real action.
This relates with whether our system performance is best or not. The feasibility study play
a major role in the analyse of the system. The feasibility study forms the basis of the
system.
The feasibility study is carried out in the following aspect as follows:
1)Technical Feasibility :-
If the system processes huge amount of data then the system is technically
feasible. Technical evaluation must also access whether the existing system can be upgraded
to use the new technology and whether the organization has the expertise to use.
2)Economic Feasibility :-
Economic feasibility consider the cost effectiveness of the project.This is often
called a cost benefit analysis.The benefit is always expected to be over the cost.The software
and hardware reuiredfor the system is easily available. No additional cost will be incurred
also beneficial to cost analysis of system, because of automation.
Economically, the system is capable of purchasing the required setup. The
system will also reduce lots of paper work, chances of error, processing time and
provide consistent information. This will lead to better output and will save lots of money to
prove its feasibility.
3)Operational Feasibility :-
Operational feasibility consider the acceptability of the system.The project can
be rejected due to operational non feasibility.Will the system be used if it developed and
implemented ? The system will provide timely information and status of various activities
to manage of the system.
2. Non-functional Requirements :-
2.1 Performance :-
The system should provide quick access of data.
The system should handle a large number of records more efficiently.
A) Software Requirements :
The software requirements are description of features and functionalities of the
target system.To develop this desktop application following software specification is used.
I. CLIENT SIDE:
B) Hardware Requirements :
I. CLIENT SIDE:
0.0
I. Admin :
Login
Registration
II. Employee:
Login
I. Admin :
II. Employee :
I. Admin :
II. Employee :
I. Admin :
II. Employee :
Fetch
Show Acknowledgement Send Acknowledgement and
Save
Details
Fetch and
Show Acknowledgement Save
Send Acknowledgement Details
Logout vendor_payment_
entry
Add Petty Cash Entry details Valid Petty Cash Entry Pettycash_entry
details
Fetch
Show Acknowledgement Send Acknowledgement and
Save
Details
vendor_payment_
Log Out
entry
4.
A) Login
Field Description
Log_ID Login Id
username User Name
password Password
B) New User
Field Description
USER_ID User Id
FNAME First Name
LNAME Last Name
PHONENO Phone Number
EMAIL Email Id
USERNAME User Name
PASSWORD Password
C) Enquiry
Field Description
ENQ_ID Enquiry Id
FNAME First Name
LNAME Last Name
BRANCH Branch
PHONENO Phone Number
EMAILID Email Id
Gender Gender
CAN_INFO Candidate Information
SUGG_Info Suggestion Information
STATUS Status
D) Candidate Registration
Field Description
REG_ID Registration Id
FNAME First Name
LNAME Last Name
BRANCH Branch
PHONENO Phone Number
EMAILID Email Id
REG_FOR Registration For
TRANINING_COST Training Cost
GST Goods And Services Tax
FINAL_COST Final Cost
E) Client Registration
Field Description
CLI_ID Group id
COMP_Name Group master code
COMP_LOCATION Group master Name
COMP_OWNER Company Owner Name
PHONENO Phone Number
COMP_WEBSITE Company Website
ADDRESS Address
COMP_PNAME Company Person Name
CONT_DESG Contact Designation
F)Vendor Registration
Field Description
VEN_ID Vendor Id
COMP_NAME Company Name
VNAME Vendor Name
PHONENO Phone Number
COMP_WEBSITE Company Website
ADDRESS Address
TYPE_OF_SERVICES Type Of Services
EMAIL Email Id
Field Description
PET_ID Petty Cash Entry Id
PDATE Present Date
DNAME Department Name
PNAME Product Name
PRATE Product Rate
PQUANTITY Product Quantity
PBILL Product Bill
ENAME Employee Name
DESC_OF_NEED Description Of Need
Field Description
PET_ID Petty Cash Entry Id
PDATE Payment Date
DNAME Department Name
PNAME Product Name
PRATE Product Rate
PQUANTITY Product Quantity
PBILL Product Bill
ENAME Employee Name
DESC_OF_NEED Description Of Need
Field Description
CP_ID Client Payment Id
PAYMENT_DATE Payment Date
FNAME First Name
LNAME Last Name
PAYMENT_FOR Payment For
PAYMENT_MODE Payment Mode
PAYMENT_AMT Payment Amount
PAY_ENTRY_BY Employee Name
Field Description
VP_ID Vendor Payment Id
PAYMENT_DATE Payment Date
CNAME Company Name
CSERVICES Company Services
OWNER_FNAME Owner First Name
OWNER_LNAME Owner Last Name
PAYMENT_FOR Payment For
PAYMENT_MODE Payment Mode
PAYMENT_AMT Payment Amount
PAY_ENTRY_BY Payment Entry By
4.3 Inputs:
Fig 1.0: The "Admin Login" enable secure access to enter the system by
requiring admin username and password.This system can be access only one
admin.
3. Successfully Login-
Admin Home Page (Admin Dashboard) :
Admin successfully login to admin dashboard in which admin can
add new CRM system users(employee) also manage them.Admin can also view
and manage clients and vendors details also admin can manage petty cash entry
and,employee,clients and vendors payment entries details.
In that the all vendor payment records are getting from employee .When employee
add/create new details of vendor payment that stored and manage both sides admin and
employee.
In that the all client payment records are getting from employee .When employee
add/create new details of client payment that stored and manage both sides admin and
employee.
Fig 1.0: The "Employee Login" enable secure access to enter the system by
requiring employee username and password.This system can be access only
registered employee.
2. Successfully Login-
Employee Home Page (Employee Dashboard) :
Employee successfully login to employee dashboard in which employee can
add new enquiries for candidate also manage them. Employee can also add,
view and manage clients and vendors details also petty cash entry
and,employee,clients and vendors payment entries details.
10.Logout Successfully -
4.3 Outputs:
Fig: - Admin can edit, update and manage users details in the CRM Users Detail section
Fig: - Employee can add, update and manage enquiries details in the All Inquiries Details.
Fig- Admin & Employee can manage all petty cash details.
Fig- Admin & Employee can manage all client payment entry details.
Fig- Admin & Employee can manage all vendor payment entry details.
Fig- Admin & Employee can manage all employee payment entry details.
5.
A) Software Requirements :
The software requirements are description of features and functionalities of the
target system.To develop this desktop application following software specification is used.
I. CLIENT SIDE:
B) Hardware Requirements :
I. CLIENT SIDE:
II.SERVER SIDE:
XAMPP is the most popular software package which is used to set up a PHP
development environment for web services by providing all the required
software components.
I. Admin
There is one admin for this application. Here all authorities of report
management were only handled by admin. Admin can add or delete the CRM user, and
can see, generate all reports related to the registered client,employee and vendor also
all payment entry details.
Functions related to Admin Module:
1. Login :
Here admin can login to system.
6.Manage All Employee Payment , Client Payment & Vendor Payment Entry Details:
Edit/Update employee payment,client payment and vendor payment entry
details.
Delete details
II. Employee :
1. Login :
Here employee can login to system.
7.Manage All Employee Payment , Client Payment & Vendor Payment Entry
Details:
Edit/Update employee payment,client payment and vendor payment entry
details.
Add employee payment,client payment and vendor payment entry details.
Delete details
6.
1) User Registration Report: This is a user report.And admin can access and
manage employees(user) details.
2) Client Details Report: This is a client report.And admin can access and manage clients
details.
3) Vendor Details Report: This is a vendor report.And admin can access and manage vendors
details.
4) Petty Cash Details Report: This is a petty cash report.And admin can access and manage
petty cash details.
5) Client Payment Details Report: This is a client payment report.And admin can access and
manage client payment details.
6) Vendor Payment Details Report: This is a petty cash report.And admin can access and
manage client payment details.
7) Employee Payment Details Report: This is a petty cash report.And admin can access and
manage client payment details.
7.1 Conclusion:
The project entitled Academic CRM was completed successfully. Based on this
research
thesis entitled ―Academic CRM which was developed and had solved the problems that
were identified
in current system .
The system has been developed with much care and free of errors and at the same
time it is
efficient and less time consuming. The purpose of this project was to develop a desktop
application
and enhance the CRM system.
1) System helps to store all the data about the customer orders details in computer and there
is no need to
do paper work.
2) Data is going to be preserved carefully for longer period hence proper backup is required
otherwise there
is chance of losing entries or data
3) This system is design to solve problems of maintaining all records of employees and
candidate also maintaining all records, it provides a single source of information that helps
to maintain data .
3) CSV option is not available in table record so data cannot forward to excel sheet.
7.3 Suggestions:
1) In future mode of payment can be made online
5) All Payments record all show in graphical format like pie chart.
if(document.f1.username.value.length<5 || document.f1.username.value.length>10 )
{
alert("Username must be 5 to 10 Long ");
document.f1.username.focus();
return false;
}
//validation for password
if(document.f1.pass.value.length<5 || document.f1.pass.value.length>10 )
{
alert("Password must be 5 to 10 Long ");
document.f1.pass.focus();
return false;
}
}
</script>
</head>
<body>
<div class="login">
<div id="loginform">
<form name="f1" action="loginauthentication.jsp" method="post">
<table align="center" cellpadding="4">
<tr>
<th><h3>CRM LOGIN</h3></th>
</tr>
<tr class="user-box">
<td> <input type="text" name ="uname" placeholder="Username" class="inputclass" autocomplete="off"></td>
</tr>
<tr class="user-box">
<td> <input type="password" name ="pass" placeholder="Password" class="inputclass" autocomplete="off"></td>
</tr>
<tr>
<td> <button type="submit" class="buttonclass" onclick="return validate()">Log In</button></td>
</tr>
<tr>
</tr>
</table>
</form>
</div>
</div>
</body>
else if(rs.next())
{
if(rs.getString("USERNAME").equals(uname) && rs.getString("PASSWORD").equals(pass))
{
response.sendRedirect("Dashboard_emp.jsp");
}
}
else
{
response.sendRedirect("loginFail.jsp");
}
catch(Exception e)
{
out.println(e);
}
%>
var data=/^[a-zA-Z]+$/;
if(!document.f1.fname.value.match(data))
{
alert("Please enter valid First Name ");
document.f1.fname.focus();
return false;
}
if(!document.f1.lname.value.match(data))
{
if(document.f1.phoneno.value.length!=10)
{
alert("You have entered invalid Phone No");
document.f1.phoneno.focus();
return false;
}
if(document.f1.username.value.length<5 || document.f1.username.value.length>10 )
{
alert("Username must be 5 to 10 Long ");
document.f1.username.focus();
return false;
}
if(document.f1.pass.value.length<5 || document.f1.pass.value.length>10 )
{
alert("Password must be 5 to 10 Long ");
document.f1.pass.focus();
return false;
}
}//end of function
</script>
</head>
<body>
<ul>
<li><a href="" class="brandname"><font color='#86C232'>AITS</font> CRM </a></li>
</ul>
<tr>
<td>Phone No</td>
<td><input type="number" name="phoneno" class="inputclass"></td>
</tr>
<tr>
<td>Email</td>
<td><input type="email" name="email" class="inputclass" autocomplete="off" ></td>
</tr>
<tr>
<td>Username</td>
<td><input type="text" name="username" class="inputclass" autocomplete="off"></td>
</tr>
<tr>
<td>Password</td>
<td><input type="password" name="pass" class="inputclass" autocomplete="off"></td>
</tr>
<tr>
<td align="center" colspan="2">
</td>
</tr>
</table>
</form>
</body>
</html>
Student Name:
Guide Name:
Contact No.
Topic:
Industry Name: -
Designation:-
Contact No:-
YSPM’S YTC,
71 Faculty of MCA, Satara. 71
Academic CRM
Signature of Signature of
Sr. No Date Description of Discussion Guide Student
1
10
11
12
Books:
Websites:
www.DataHub.com
www.Salesforce.com
www.Wekipedia.com