internet service provider

1. INTERNET
SERVICE
PROVIDER

2. •ACKNOWLEDGEMENT
• We deem it a pleasure to acknowledge our sense of gratitude to our project guide Prof.Gunjal.K.S under whom we carried
out the project work. His incisive and objective guidance and timely advice encouraged me with constant flow of energy to continue
the work.
• We shall remain grateful for providing us a strong academic atmosphere by enforcing strict discipline to the project work with
utmost concentration and dedication.
• Our deep sense of gratitude and heartfelt thanks to our parents and our family who supports us for that. We would like also to
thank our all-faculty members for their inspirational help and advice which make this present piece of report in this current shape.
• Lastly, our sincere thanks to all our friends for their coordination in completion of the seminar report.
•
• Ms. Datkhile Pradnya Arun
• Ms. Pande Sairathi Bhausaheb
• Ms. Udamle Rutuja Somnath
• Ms. Kshirsagar Shrushti Jagnnath

3. • Introduction
•To develop an INTERNET SERVICE PROVIDER-CUSTOMER PORTAL, we take care of the customer account
management, service information and customer support, include queries and complaints.
•The current manual or traditional services of accessing ISP services can be time consuming and prone to have
errors.
•The portal consumes these operations, ensuring quicker, more efficient and enhanced customer satisfaction.
•The main intention of introducing this system is to streamline and simplify customer related task for ISP
services. It enables the registration of various customer accounts, management of services like prepaid or
postpaid plans, and allows customer to lodge complaints or enquire seamlessly. Additionally, the portal
provides real time updates on user accounts, billing information and service status for customer.

4. •1.1 MOTIVATION
•Before we get into the thick of things we would like to add a few heartfelt Words for who was part of this project in numerous ways, people who gave unending support right the stage and the project idea was
conceived.
•First, we say thanks to our Respected Principal Dr.Bhaskarrao Shelke. who always inspire & cheers us for achieving the goals & objectives. We would like to thank the HOD Prof. K. S. Gunjal whose right guidelines &
suggestions motivates us for doing our duties & responsibilities, we also thanks to the all teaching & non-teaching staff members, who guides & cooperates us directly or indirectly for completion of this project report.
•We express my sincere thanks and all of the faculty members of B.Sc. (Computer Science) specially my internal project guide, Prof.A.K.Pathan, Prof.M.V.Tambe For their guidance and support thought the project.
•And finally, heartfelt appreciations to those countless friends who made us to develop deeper and deeper into the extent that we know firmly believe that experience is an attitude, philosophy of life.
• Yours Sincerely,
• Ms. Datkhile Prdanya Arun
• Ms. Pande Sairathi Bhausaheb
• Ms. Udamle Rutuja Somnath
• Ms. Kshirsagar Shrushti Jagnnath

5. •1.2 Problem Statement
•The current system for managing customer accounts and services for our Internet Service Provider (ISP) is manual, time-consuming, and prone to errors. Customers
are unable to easily access their account information, view their billing and usage history, or submit support tickets. This leads to a poor customer experience,
increased support costs, and decreased customer satisfaction.
•Specific Problems:
•1. Manual Account Management: Customer account information is stored in multiple, disparate systems, making it difficult to access and update.
•2. Limited Customer Visibility: Customers are unable to easily view their account information, billing history, and usage data.
•3. Inefficient Support Process: Customers must contact support via phone or email, leading to long wait times and resolution delays.
•4. Error-Prone Billing and Payment: Manual billing and payment processes lead to errors, late payments, and missed payments

6. •Purpose And goals
•1.Customer Experience: Provide customers with easy access to their account information, billing history, and usage data.
•2.Increase Efficiency: Automate manual processes, reducing errors and increasing productivity.
•3. Enhance Support: Provide customers with multiple support channels, including online ticket submission and self-service resources.
•4.Reduce Costs: Decrease support costs by reducing the volume of support requests and improving first-call resolution rates.
•5. Scalability: Design the system to scale with the growing number of customers and support requests

7. •Project scope and limitations
•
• Scope:
•1. Customer Portal: The project will develop a secure, user-friendly portal for customers to access their account information, billing history, and usage
data.
•2. Account Management: The project will automate account management processes, including billing, payment, and usage tracking.
•3. Support Ticketing: The project will implement an online support ticketing system, allowing customers to submit and track support requests.
•4. Knowledge Base: The project will develop a knowledge base with self-service resources, including FAQs, tutorials, and troubleshooting guides.
•5. Integration: The project will integrate the customer portal with existing ISP systems, including billing, payment, and support ticketing systems

8. • Limitations:
•
1. Technical Constraints: The project will be limited by the technical capabilities of the existing ISP systems and infrastructure.
•
2. Data Security: The project will need to ensure the security and integrity of customer data, which may limit the scope of the
project.
•
3. Customer Adoption: The project will require customers to adopt the new portal and support ticketing system, which may be a
limitation.
•
4. Support Resources: The project will require additional support resources, including training and documentation, which may be
a limitation.
•
5. Timeline: The project will need to be completed within a limited timeline, which may limit the scope of the project.
•
6. Budget: The project will need to be completed within a limited budget, which may limit the scope of the project.
•
7. Third-Party Integration: The project may require integration with third-party systems, which may be a limitation.
•
8. Scalability: The project will need to ensure that the new portal and support ticketing system can scale to meet the needs of a
growing customer base.

9. •Objectives
•The primary objective of an internet service provider (ISP) project is to provide reliable, high-quality internet connectivity to
individuals, businesses, and organizations. This includes:
•
• Broadband Access: Ensuring widespread availability of broadband internet services to enable communication, information
access, and participation in the digital economy.
• Connectivity: Connecting users to the global network of the internet, enabling them to access websites, applications, online
services, and digital content.
• Speed and Performance: Delivering fast and consistent internet speeds to support a wide range of activities, including
streaming media, video conferencing, online gaming, and file downloads/uploads.
• Reliability: Maintaining a robust network infrastructure and implementing redundancy measures to minimize downtime and
ensure uninterrupted internet access for customers.
• Scalability: Designing the network architecture and service offerings to accommodate growth in user demand, bandwidth
requirements, and technological advancements

10. •2) System Analysis
•
•The System Analysis means analysis of current existing system and collection of information about the system. Next to evaluate
the collected information, to find a new improved system would be needed or not
• 2.1 Existing System
•Before the implementation of an ISP Management System, many Internets Service Providers
•(ISPs) relied on manual and disjointed processes to manage their operations.
•1. Manual Customer Management: Customer onboarding, subscription management, and account updates were handled
manually, leading to inefficiencies and potential errors in
•customer data.
•2. Billing and Invoicing Complexity: Billing processes were manual and time-consuming, with the generation of invoices prone
to errors. Managing varied subscription plans and tracking payments for a growing customer base became increasingly
challenging.

11. •2.2 Scope and limitations of existing System
• Scope:
•
• Network Infrastructure: The ISP's existing system likely includes a network infrastructure consisting of routers,
switches, servers, and other hardware necessary for delivering internet services.
• Service Offerings: This system encompasses the range of internet plans and packages offered to customers, including
different speeds, data caps, and pricing options.
• Customer Management: It includes processes and systems for customer registration, billing, account management,
and support services.
• Technical Support: This involves mechanisms for troubleshooting connectivity issues, handling customer inquiries, and
providing technical assistance.
• Quality of Service (QoS): The existing system may have provisions for ensuring a certain level of QoS, including
bandwidth management, traffic prioritization, and service level agreements (SLAs).
• Security Measures: It likely incorporates security measures such as firewalls, intrusion detection/prevention systems,
and data encryption to safeguard the network and customer data.

12. •Limitation:
• Infrastructure Constraints: Limited availability of high-speed internet infrastructure in
certain areas can constrain the ISP's ability to offer faster services to all customers.
• Technical Challenges: Issues such as network congestion, hardware failures, and
compatibility issues with customer equipment can impact service reliability and performance.
• Regulatory Compliance: Compliance with government regulations and industry standards,
such as data privacy laws and net neutrality regulations, can impose limitations on the ISP's
operations and service offerings.
• Competition: Competition from other ISPs in the market can limit the ISP's ability to attract
and retain customers, as well as influence pricing strategies and service innovations.
• Geographical Limitations: Geographical factors such as terrain, distance from network
infrastructure, and environmental conditions can affect the availability and quality of internet
services in certain areas.

13. •2.3 Project perspective and features:
•From a project perspective, an Internet Service Provider (ISP) project would typically involve several key features:
• Network Infrastructure: Building and maintaining the network infrastructure including routers, switches, cables, and other hardware necessary
for providing internet connectivity.
• Broadband Access: Offering various types of broadband access such as DSL, cable, fiber optic, and wireless connections to residential and
commercial customers.
• Service Plans: Providing a range of service plans with different speeds, data caps, and pricing options to cater to the needs of different customers.
• Customer Support: Offering customer support services including technical assistance, troubleshooting, and billing inquiries.
• Billing and Payment Systems: Implementing billing and payment systems for managing customer subscriptions, invoicing, and collecting
payments.
• Network Security: Ensuring the security of the network infrastructure and protecting customer data from cyber threats such as hacking and
malware.
• Quality of Service (QoS): Ensuring reliable and high-quality internet service by managing network traffic, minimizing latency, and optimizing
bandwidth usage.
• Regulatory Compliance: Adhering to regulations and standards set by government authorities and industry bodies related to internet service
provision, privacy, and data protection.
• Infrastructure Expansion: Planning for future growth and expansion of the network infrastructure to accommodate increasing demand for
internet services.
• Marketing and Sales: Developing marketing strategies to attract new customers and retain existing ones, as well as managing sales channels and
promotions.

14. •2.4 Software & Hardware Requirement
•
• Requirements:
• Hardware
•
• Device name : LAPTOP-OOUHJEMJ
• Processor : i5 6th
gen with Graphics 3.30GHz
• Installed RAM: 8.00 GB (7.35 GB usable)
• System type : 64-bit operating system,
x64-based processor
•2.Software
•
• Language : JAVA
• Database : My SQL
• IDLE : Eclipse
• Operating System: Window 10

15. 3) System
design:
E-R Diagram

16. Class
Diagram

17. Object
Diagram

18. Use-case
Diagram:

19. Sequence
Diagram:

20. Activity
Diagram

21. State chart
Diagram

22. Collaboratio
n Diagram:

23. Deployme
nt
Diagram

24. 3.2 User
interface
(Input and
Output Screen)

28. 3.3 Output and report testing
System Testing
• System testing involves unit testing, integration testing, white-
box testing, black-box testing. Strategies for integration software
components into afunctional product include the bottom-up
strategy, the top-down strategy, and sandwich strategy. Careful
planning and scheduling are required to ensure that modules that
will be available for integration into evolving software product when
needed a serious of testing are performed for the proposed system
before the system is ready for user acceptance testing.
•1 UNIT TESTNG
•Instead of testing the system as a whole, Unit testing focuses on
the modules that make up the system. Each module is taken up
individually and tested for correctness in coding and logic.
•The advantages of unit testing are:
• Size of the module is quite small and that errors can easily are
located.
• Confusing interactions of multiple errors in wide different parts
of the software is eliminated.
• Modules level testing can be exhaustive.

29. • INTEGRATION TESTING
•
•It tests for the errors resulting from integration of modules. One specification of integration testing is whether parameters match on
both sides of type, permissible ranges and meaning. Integration testing is functional black box test method. It includes testing each
module as an impenetrable mechanism for information. The only concern during integration testing is that the modules work together
properly.
•
•2 WHITE BOX TESTING (CODE TESTING)
•
•The code-testing strategy examines the logic of the program. To follow this testing method, the analyst develops test cases that result
in executing every instruction in the program or module so that every path through the program is tested. A path is a specific
combination of conditions that is handled by the program. Code testing does not check the range of data that the program will accept.
• Exercises all logical decisions on their true or false sides.
• Executes all loops at their boundaries and within these operational bounds.

30. •3 BLACK BOX TESTING (SPECIFICATION TESTING)
•To perform specification testing, the analyst examines the specification, starting from what the program should do and how is should perform under various
conditions. Then test cases are developed for each condition or combinations of conditions and submitted for processing. By examining the results, the analyst can
determine whether the programs perform according to its specified requirements. This testing strategy sounds exhaustive. If every statement in the program is
checked for its validity, there doesn’t seem to be much scope for errors.
•Testing Objectives
The prime objective of system testing is to test code with intention to find errors. This objective also demonstrates that the software functions are working according
to software requirements specification (SRS) with regards to functionality, features, facility and performance. It should be noted that, however testing will detect error
in written code, but it will not show an error if the code does not address a specific requirement stipulated in SRS but not coded in program.
•
•Testing Principles
• Testing should be traceable to the customer requirements stipulated in the SRS. Test cases should be designed soon as soon as the SRS is finalized and frozen.
• Test cases should be planned from lower-level components and taken to higher level.
• Test cases should address at least all critical key functions, features, facilities and performance needs stipulated in SRS.
• Test cases should not leave behind any fatal errors.

31. •Advantages
•
• Computerized system is completely automated thus user can operate
easily.
• Time required is very less to makes and search the records.
• Computerized system generates online reports.
• It reduces the data consistency and redundancy.
• Computerized system is very helpful to display all records.

34. • 5) Drawbacks And Limitations
• Infrastructure Costs: Building and maintaining the necessary infrastructure, such as fiber optic cables or satellite equipment, can be expensive.
• Geographic Limitations: ISPs may struggle to provide reliable service in remote or rural areas due to infrastructure challenges or low
population density.
• Bandwidth Constraints: ISPs must manage bandwidth effectively to ensure consistent and fast internet speeds for all customers, which can be
challenging during peak usage times.
• Regulatory Compliance: ISPs must comply with various regulations related to data privacy, net neutrality, and telecommunications, which can
vary by region and add complexity to operations.
• Technical Issues: Network outages, equipment failures, and other technical issues can disrupt service and require prompt resolution to
maintain customer satisfaction.
• Competition: ISPs often face competition from other providers, which can lead to pricing pressures and the need to differentiate through
service quality or additional offerings.
• Customer Support: Providing timely and effective customer support can be challenging, especially during periods of high demand or when
dealing with technical issues.
• Security Concerns: ISPs must protect customer data and networks from cyber threats, such as hacking or malware, which requires ongoing
investment in security measures and expertise.
• Scalability: As demand for internet services grows, ISPs must continually invest in infrastructure upgrades and expansion to meet customer
needs, which can strain resources and require careful planning.
• Economic Factors: Economic downturns or changes in consumer behavior can impact the demand for internet services and affect the financial
viability of ISP projects

35. • 6) Future Enhancement
• Improved Infrastructure: Investing in advanced technologies such as fiber optics, 5G networks, or satellite
internet to provide faster and more reliable connectivity.
• Expansion to Unserved Areas: Extending service coverage to underserved or rural areas to bridge the digital
divide and ensure equitable access to high-speed internet.
• Enhanced Customer Experience: Implementing self-service portals, mobile apps, and chatbots for customer
support to streamline interactions and improve satisfaction.
• Advanced Network Management: Deploying software-defined networking (SDN) and network function
virtualization (NFV) to optimize network performance, scalability, and flexibility.
• Security Enhancements: Strengthening cybersecurity measures through advanced threat detection, encryption,
and authentication mechanisms to protect customer data and networks.

36. •
7) Bibliography
• Before and at the time of developing the project following books are feared which
gear us seem
• important guidelines for designing and developing the project and project reports.
• Reference Books: -
• ➢ Database System Concept
• ➢ Software Engineering
• ➢ PHP Book
• ➢ Java Programming
• Web Sites: -
• www.google.co.in

37. •8) Conclusion
•Recap of project objectives: Summarize the goals and objectives set at the beginning of the
project.
• Accomplishments: Highlight the achievements and milestones reached during the project
implementation phase.
• Challenges overcome: Discuss any obstacles or challenges faced and how they were
addressed.
• Deliverables: Review the deliverables produced, such as infrastructure improvements,
network enhancements, customer service improvements, etc.
• Impact: Evaluate the impact of the project on the ISP's operations, customer satisfaction,
revenue, etc.
• Lessons learned: Reflect on lessons learned throughout the project that can be applied to
future initiatives.
• Recommendations: Provide recommendations for future improvements or areas of focus
based on the project experience.
• Acknowledgments: Thank individuals or teams involved in the project for their contributions.
• Outlook: Discuss potential future developments or expansions based on the project's
success

38. THANK YOU