Yashwantrao Chavhan Maharashtra Open University

A PROJECT REPORT ON (JEWELLARY MANAGEMENT SYSTEM ) SUBMITTED IN

PARTIAL FULFILLMENT OF REQUIREMENTS FOR THE DEGREE OF
BACHELOR OF COMPUTER APPLICATION

(B.C.A CODE P131)

FOR THE ACADEMIC YEAR 2023-24

YASHWANTRAO CHAVAN MAHARASHTRA OPEN UNIVERSITY (Y.C.M.O.U)

SUBMITTED BY: VISHAL SUBHASH KADAM)

UNDER THE GUIDANCE OF STUDY CENTER CODE: 31272

St. Suman Education Society Campus, Near, General Kariappa Bridge Meghdoot,
Rajendra Nagar, Borivali, Mumbai, Maharashtra 400066.
 L N College Of Management and Technology
Borivali (E)
400066
(Affiliated to Yashwantrao Chavan Maharashtra Open
University)

TO WHOMSOEVER IT MAY
CONCERN

This is to certify that student VISHAL KADAM of

L N COLLEGE OF MANAGEMENT AND
TECHOLOGY BORIVALI (E) Has satisfactorily
completed his/her project JEWELLARY
MANAGEMENT SYSTEM during the period date
from and to in the partial fulfillment of BCA.

Project Guide External Examiner Principal

 CERTIFICATE OF EVALUATION

This is to certify that the undersigned have assessed and evaluated the
Project Work titled (JEWELLARY MANAGEMENT SYSTEM) submitted by the
following students.

VISHAL KADAM (2021017001666384)

The project Report has been (accepted/rejected) for the partial

fulfillment of B.C.A. programme.

Signature of the Examiner

Name of the Examiner

 CERTIFICATE OF COMPLETION

This is to certify that the following student of B.C.A have completed the
Project Work Titled(JEWELLARY MANAGEMEN SYSTEM ) under my
guidance and supervision. The Project Report has been written according
to the guidelines given by the Yashwantrao Chavan Maharashtra Open
University.

MR. VISHAL KADAM (2021017001671795)

Signature of the Study Center Coordinator Signature of the Guide

Name of the Study Center Coordinator Name of the Guide

Stamp of the Study Center

 INDEX
SERIAL No TOPIC PAGE NO

1. ACKNOWLEDGEMENT
2. SYNOPSIS
3. OBJECT OF THE SYSTEM
4. SCOPE
5. PROBLEM DEFINITION
6. PROBLEM SOLUTION
7. FEASIBILITY STUDY
8. REQUIREMENT SPECIFICATION
9. SYSTEM DESIGN
10. GANTT CHART
11. ER DIAGRAM
12. CLASS DIAGRAM
13. ACTIVITY DIAGRAM
14. SEQUENCE DIAGRAM
15. USE-CASE DIAGRAM
16. CONTEXT LEVEL DIAGRAM
17. DATA DICTIONARY
18. SYSTEM DEVLOPMENT
19. TESTING METHOLOGY :-
19.1 BLACK BOX TEXTING
19.2 WHITE DIAGRAM
19.3 INTEGRATION TESTING
19.4 SYSTEM TESTING
20. SCREENSHOT
Acknowledgement:

• Express gratitude towards individuals or organizations that

provided support, guidance, or resources during the project.
• Acknowledge the contributions of team members, advisors,
mentors, or sponsors who helped in various aspects of the project.
• Mention any institutions or companies that provided access to
facilities, equipment, or data necessary for the project.
• Reflect on the significance of the support received and its impact
on the successful completion of the project.
• Offer special thanks to anyone who went above and beyond to
assist with the project's development or execution.

Synopsis:

• Provide an overview of the jewelry management system project,

including its purpose and objectives.
• Summarize the key features and functionalities that the system
aims to offer.
• Highlight the target users or audience for the system and the
benefits they will derive from its implementation.
• Briefly mention the technologies or methodologies employed in
developing the system.
• Convey the importance of the project and its potential impact on
the jewelry industry or related domains.
Object of the System:

• Define the primary goals and objectives of the jewelry

management system.
• Specify what the system intends to achieve, such as improving
inventory management, sales tracking, or customer relationship
management.
• Identify the stakeholders who will benefit from the system, such as
jewelry store owners, employees, or customers.
• Outline the desired outcomes or results expected from the
implementation of the system.
• Emphasize the value proposition of the system and how it
addresses the needs or challenges of its users.

Scope:

• Define the boundaries of the project in terms of features,

functionalities, and deliverables.
• Specify what aspects of jewelry management will be covered by
the system, such as inventory control, sales management, or
customer engagement.
• Clarify any limitations or exclusions regarding the scope of the
project, such as specific types of jewelry or business processes
that will not be addressed.
• Discuss any potential expansion or scalability considerations for
future iterations of the system.
• Align the project scope with the available resources, timeline, and
budget constraints.

Problem Definition:
• Identify the challenges or pain points faced by jewelry businesses
that the system aims to address.
• Describe common issues in jewelry management, such as
inefficient inventory tracking, lack of sales insights, or poor
customer engagement.
• Provide real-world examples or anecdotes to illustrate the
significance of the identified problems.
• Highlight the impact of these problems on the performance,
profitability, or customer satisfaction of jewelry businesses.
• Emphasize the need for a comprehensive solution to overcome
these challenges and improve overall operations.

Problem Solution:

• Present the proposed solution offered by the jewelry management

system to address the identified problems.
• Outline how the system's features and functionalities directly target
and resolve the key pain points in jewelry management.
• Explain the advantages or benefits of implementing the system,
such as increased efficiency, accuracy, or profitability.
• Illustrate how the system streamlines processes, enhances
decision-making capabilities, and improves the overall customer
experience.
• Emphasize the value proposition of the system as a practical and
effective solution for jewelry businesses.
Feasibility Study:

• Conduct an assessment of the technical, economic, and

operational feasibility of implementing the jewelry management
system.
• Evaluate the technical requirements and constraints associated
with developing and deploying the system.
• Analyze the financial implications of the project, including initial
investment, operating costs, and potential returns on investment.
• Consider the organizational readiness and capacity to adopt and
support the system within the jewelry business.
• Identify any risks or challenges that may impact the feasibility of
the project and propose mitigation strategies.

Requirement Specification:

• Detail the functional requirements of the jewelry management

system, including specific features, functionalities, and user
interactions.
• Specify the non-functional requirements, such as performance,
security, scalability, and usability criteria.
• Define the system interfaces with external components or
stakeholders, such as integration with existing software or
hardware systems.
• Document any constraints or assumptions that may influence the
design and development of the system.
• Prioritize requirements based on their importance and relevance to
the overall objectives of the project.
System Design:

• Develop an architectural overview of the jewelry management

system, including its components, modules, and layers.
• Define the relationships and interactions between different system
elements, such as databases, user interfaces, and business logic
components.
• Create detailed design specifications for each module or
component, outlining their functionality, interfaces, and
dependencies.
• Consider factors such as scalability, flexibility, and maintainability
in the system design.
• Use appropriate design methodologies, such as object-oriented
design or service-oriented architecture, to structure the system
effectively.

Gantt Chart:

• Create a timeline of project tasks, activities, and milestones using

a Gantt chart format.
• Break down the project into smaller, manageable tasks and assign
them to specific team members or resources.
• Define the start and end dates for each task and establish
dependencies between them to sequence the work effectively.
• Allocate resources, such as personnel, budget, and equipment, to
each task based on their requirements and priorities.
• Monitor progress against the Gantt chart regularly and make
adjustments as needed to stay on track with the project timeline.
ER Diagram:

• Entity-Relationship (ER) diagrams represent the data model of the

jewelry management system, showing entities, their attributes, and
the relationships between them.
• Identify entities relevant to the jewelry management system, such
as customers, products, orders, and suppliers.
• Define the attributes for each entity, specifying the data fields or
properties associated with them.
• Establish relationships between entities, such as one-to-many,
many-to-many, or one-to-one relationships, to reflect how they are
connected.
• Use cardinality notation to indicate the minimum and maximum
occurrences of entities in a relationship.
• Ensure that the ER diagram accurately captures the data structure
and relationships required to support the functionalities of the
jewelry management system.
• Validate the ER diagram against the system requirements and
make revisions as necessary to ensure completeness and
correctness.
• ER diagrams serve as a blueprint for database design and
implementation, guiding the creation of database tables, keys, and
constraints.
• ER diagrams help stakeholders, including developers and
business analysts, understand the data model and its implications
for the system's behavior and functionality.
• ER diagrams facilitate communication and collaboration among
project team members by providing a visual representation of the
system's data architecture.
Class Diagram:

• Class diagrams depict the static structure of the jewelry

management system, showing classes, their attributes, methods,
and relationships.
• Identify classes representing key entities or components in the
system, such as Product, Customer, Order, Payment, etc.
• Define attributes for each class, representing the properties or
characteristics of objects belonging to that class.
• Specify methods or operations associated with each class,
representing the behaviors or actions that objects of that class can
perform.
• Establish relationships between classes, such as associations,
generalizations, aggregations, or compositions, to depict how they
are connected.
• Use multiplicity notation to indicate the cardinality of associations
between classes.
• Class diagrams provide a blueprint for object-oriented design,
guiding the implementation of classes and their interactions in the
system.
• Validate the class diagram against the system requirements and
make revisions as needed to ensure consistency and
completeness.
• Class diagrams serve as a visual tool for communication and
collaboration among developers, designers, and stakeholders,
facilitating a shared understanding of the system's design.
• Class diagrams help identify opportunities for abstraction,
encapsulation, inheritance, and polymorphism, enabling the
creation of modular, reusable, and maintainable code.
 • Class diagrams complement other design artifacts, such as
sequence diagrams and activity diagrams, by providing a structural
perspective on the system's architecture.

Activity Diagram:

• Activity diagrams model the flow of activities or processes in the

jewelry management system, illustrating how tasks are performed
and controlled.
• Identify the major activities or tasks involved in jewelry
management, such as product management, order processing,
inventory tracking, etc.
• Represent each activity as a rounded rectangle on the activity
diagram, labeling them with descriptive names.
• Use arrows to depict the flow of control between activities,
indicating the sequence in which they are performed.
• Include decision points or branches in the activity diagram to
represent conditional logic or alternative paths in the workflow.
• Use symbols such as forks, joins, and merge nodes to illustrate
concurrency and synchronization in the activity diagram.
• Include swimlanes or partitions to organize activities based on the
roles or responsibilities of actors involved in the process.
• Validate the activity diagram against the system requirements and
make revisions as needed to ensure clarity and correctness.
• Activity diagrams help stakeholders visualize and understand the
sequence of actions and decision points in the jewelry
management system's workflows.
• Activity diagrams serve as a basis for implementation, providing
developers with guidance on how to translate the system's logic
into executable code.
 • Activity diagrams facilitate communication and collaboration
among project team members by providing a common visual
language for discussing system behavior and functionality.

Sequence Diagram:

• Sequence diagrams illustrate the interactions between objects or

components in the jewelry management system, showing the
sequence of messages exchanged over time.
• Identify the actors or objects participating in the interactions, such
as users, system components, external systems, etc.
• Represent each object as a vertical lifeline on the sequence
diagram, with messages exchanged between them depicted as
horizontal arrows.
• Label each message with a description of the operation being
performed or the information being exchanged.
• Use numbering to indicate the sequence of messages and
interactions on the sequence diagram.
• Include loops, branches, and alternative paths in the sequence
diagram to capture conditional logic or repeated interactions.
• Use activation bars to depict the duration of time during which an
object is actively processing a message.
• Validate the sequence diagram against the system requirements
and make revisions as needed to ensure accuracy and
completeness.
• Sequence diagrams help stakeholders understand the dynamic
behavior of the jewelry management system, including the order of
operations and the flow of information.
 • Sequence diagrams serve as a blueprint for implementation,
guiding developers in writing code to support the interactions
depicted in the diagram.
• Sequence diagrams facilitate communication and collaboration
among project team members by providing a visual representation
of system interactions that is easy to understand and discuss.

Use-Case Diagram:

• Use-case diagrams model the interactions between actors (users)

and the jewelry management system, illustrating the system's
functionalities from a user's perspective.
• Identify the actors or users interacting with the system, such as
customers, employees, administrators, etc.
• Define the use cases representing the system's functionalities or
features, such as browsing products, placing orders, managing
inventory, etc.
• Represent actors as stick figures and use cases as ovals on the
use-case diagram, connecting them with lines to indicate
interactions.
• Include relationships such as associations, generalizations, or
extends between use cases to capture dependencies or variations
in functionality.
• Use stereotypes such as <<include>> and <<extend>> to denote
the relationships between use cases.
• Validate the use-case diagram against the system requirements
and make revisions as needed to ensure completeness and
consistency.
 • Use-case diagrams help stakeholders understand the high-level
functionality of the jewelry management system and its interactions
with different user roles.
• Use-case diagrams serve as a basis for requirement analysis and
validation, ensuring that the system's functionalities align with the
needs and expectations of users.
• Use-case diagrams facilitate communication and collaboration
among project team members by providing a visual representation
of system features and user interactions that is easy to
comprehend and discuss.

16. SCREENSHOT
PERT Chart

CONTEXT LEVEL DIAGRAM

 SYSTEM DEVLOPMENT

System Development begins with several key phases and processes

Requirements Gathering and Analysis:
identify and document the functional and non-functional requirements of
the ORMS.
Analyze existing processes and systems to identify areas for improvement
and automation.
System Designing's
Find the architecture and components of the ORMS based on the
requirements gathered.
Define the system's modules, interfaces, and data structures.
Create prototypes to visualize the user interface and user

Development:
Implement the ORMS according to the design specifications.
Develop the backend logic, database schema, and frontend components.
Use appropriate programming languages, frameworks, and tools to build
the system.
Follow coding standards, best practices, and version control processes to
ensure code quality and maintainability.

Testing:
Conduct various types of testing to validate the functionality, performance,
and reliability of the ORMS.
Perform unit testing to test individual components and modules.
Conduct integration testing to ensure seamless communication and
interaction between system modules.
Execute system testing to evaluate the system as a whole and verify its
compliance with requirements.
Perform user acceptance testing (UAT) with stakeholders to validate the
system against their expectations.

Maintenance and Support:

Monitor the performance and usage of the ORMS in production
environments.
Address any bugs, issues, or feature requests reported by users.
Regularly update and maintain the system to ensure compatibility,
security, and reliability.
Plan for future enhancements and updates based on feedback and
changing business requirements.

Throughout the system development process, it's essential to engage

,prioritize requirements, and maintain clear communication to ensure the
successful delivery of the JEWELLARY Management System. Additionally,
following an agile or iterative approach can help adapt to changing
requirements and deliver value incrementally.
 TESTING METHOLOGY

Testing is a crucial aspect of ensuring the quality, reliability, and

functionality :-

Test Planning:
Clearly defining the goals and objectives of testing, such as verifying
functionality, ensuring reliability, and validating performance.
Determining the scope of testing, including what features, functionalities,
and aspects of the system will be tested, as well as any specific areas or
modules that require special attention.
Selecting the testing approach or methodology to be used, such as
waterfall, agile, or hybrid models. This includes deciding on the types of
testing to be performed, such as unit testing, integration testing, system
testing, and user acceptance testing.
Developing a high-level test strategy outlining the overall approach to
testing, including test techniques, tools, and environments to be used.
TESTING METHODOLOGY DIAGRAM :-
 BLACKBOX TESTING

Black-box testing involves testing the system's functionality without

considering its internal code structure. Testers focus solely on the system's
inputs, outputs, and behavior, simulating various user interactions to
ensure that the system meets its requirements and functions correctly.

Functionality Testing:
Test the core functionalities of the system, such as user registration, room
booking, reservation management, check-in/check-out processes, and
payment processing.
Ensure that users can perform tasks smoothly and that the system responds
appropriately to their inputs.
Verify that all features work as expected across different browsers and
devices.
User Interface Testing:
Evaluate the user interface for consistency, clarity, and ease of use.
Check for proper navigation, layout alignment, and responsiveness across
various screen sizes.
Verify that buttons, links, and menus function correctly and that error
messages are displayed appropriately.
Integration Testing:
Test the interactions between different modules or components of the
system, such as the reservation system, payment gateway, and user
database.
Verify that data is passed correctly between modules and that integrated
functionalities work seamlessly.
Security Testing:
Assess the security measures implemented in the system to protect user
data, such as encryption, authentication, and authorization mechanisms.
Test for vulnerabilities such as SQL injection, cross-site scripting (XSS), and
session hijacking.
Verify that sensitive information (e.g., credit card details) is handled
securely.
Performance Testing:
Evaluate the system's performance under different load conditions to
ensure scalability and responsiveness.
Test for factors such as response times, throughput, and resource
utilization.
Identify and address any bottlenecks or performance issues that may arise.
Compatibility Testing:
Ensure that the system functions correctly across different browsers (e.g.,
Chrome, Firefox, Safari) and operating systems (e.g., Windows, macOS,
iOS, Android).
Test for compatibility with various devices, including desktops, laptops,
tablets, and smartphones.
Accessibility Testing:
Verify that the system complies with accessibility standards (e.g., WCAG)
and is usable by people with disabilities.
Test for features such as keyboard navigation, screen reader compatibility,
and text contrast.
Usability Testing:
Conduct usability tests with real users to gather feedback on the system's
usability, user experience, and overall satisfaction.
Identify areas for improvement and make adjustments to enhance the user
interface and workflow.
By performing comprehensive black-box testing, you can ensure that your
JEWELLARY management system meets the needs of users, functions
reliably, and delivers a seamless experience for both guests and
administrators.
 System Methodology

Developing an JEWELLARY Management System requires a structured

methodology to ensure the successful delivery of a robust, user-friendly,
and efficient platform. Here's a proposed system methodology for
developing an JEWELLARY Management System:

Requirements Gathering:
Begin by gathering requirements from stakeholders, including resort
owners, managers, staff, and potential guests.
Identify the core functionalities and features required for the system, such
as reservation management, property operations, guest services, analytics,
and security.

System Analysis and Design:

Analyze the gathered requirements to define the system architecture, data
models, and user interface design.
Determine the technology stack and frameworks to be used for
development, considering factors such as scalability, security, and
interoperability.
Create wireframes, mockups, and prototypes to visualize the system's
layout and functionality and gather feedback from stakeholders.

Development:
Implement the system based on the defined architecture and design.
Follow best practices for coding, including modularization, code
documentation, and version control.
Develop the backend logic for functionalities such as reservation
management, property operations, user authentication, and data
management.
Implement the frontend user interface, ensuring responsiveness,
accessibility, and ease of use across devices and browsers.

Testing:
Conduct rigorous testing to validate the functionality, usability,
performance, and security of the system.
Perform functional testing to ensure that all features work as expected and
meet the specified requirements.
Conduct usability testing with real users to gather feedback on the user
interface and user experience.
Test the system's performance under different load conditions to ensure
scalability and responsiveness.
Perform security testing to identify and mitigate potential vulnerabilities and
threats.

Deployment:
Deploy the system to a staging environment for final testing and validation.
Prepare documentation and user guides to assist users in navigating and
using the system effectively.
Coordinate with stakeholders to plan and execute the system's deployment
to the production environment.
Monitor the system closely during the initial deployment phase to address
any issues or concerns that arise.

Maintenance and Support:

Provide ongoing maintenance and support to address any bugs, issues, or
feature requests that arise post-deployment.
Monitor system performance and security regularly and implement updates
and patches as needed.
Offer training and support to users and administrators to ensure they can
effectively utilize the system's features and functionalities.
Continuous Improvement:
Collect feedback from users and stakeholders to identify areas for
improvement and enhancement.
Use analytics and user data to inform decisions about future updates and
features.
Continuously iterate on the system to incorporate new technologies,
address emerging trends, and meet evolving user needs.

ITERATIVE MODEL

Applying an iterative model to the development of an JEWELLARY

Management System involves breaking down the development process into
smaller, manageable cycles or iterations. Each iteration involves the
complete cycle of planning, designing, implementing, testing, and
evaluating a subset of features or functionalities. Here's how the iterative
model can be applied to the development of an JEWELLARY Management
System:

Planning Phase:
Identify the overall goals and objectives of the JEWELLARY Management
System.
Define the scope of the project and prioritize the features and functionalities
to be developed.
Break down the project into smaller iterations, each focused on delivering
specific features or enhancements.
Iteration Planning:
For each iteration, conduct detailed planning to identify the specific
features or user stories to be implemented.
Define the acceptance criteria for each feature to ensure that it meets the
stakeholders' requirements.
Estimate the time and resources required for the iteration and allocate tasks
to the development team.

Design Phase:
Design the architecture, database schema, and user interface for the
features to be implemented in the current iteration.
Create wireframes, mockups, and prototypes to visualize the user interface
and gather feedback from stakeholders.
Define the technical specifications and requirements for the development
team.

Implementation Phase:
Develop the features and functionalities defined in the iteration plan,
following the technical specifications and design guidelines.
Write clean, modular, and well-documented code using best practices and
coding standards.
Conduct code reviews and collaborate closely with the development team
to ensure consistency and quality.

Testing Phase:
Conduct thorough testing of the implemented features to identify and
address any defects or issues.
Perform functional testing to ensure that the features meet the specified
requirements and acceptance criteria.
Conduct usability testing with real users to gather feedback on the user
interface and user experience.
Test the system's performance, security, and scalability to ensure that it
meets the desired standards.

Evaluation and Feedback:

Review the results of testing and evaluation to assess the quality and
completeness of the implemented features.
Gather feedback from stakeholders, including users, resort owners, and
managers, to identify areas for improvement and refinement.
Use the feedback to prioritize enhancements and adjustments for future
iterations and iterations.

Iterative Refinement:
Based on the feedback and evaluation results, iterate on the system to make
refinements, enhancements, and additions.
Plan and execute subsequent iterations to address additional features,
improvements, and optimizations.
Continue to iterate on the system in cycles, gradually refining and enhancing
its features and capabilities over time.

.
 FUTURE ENHANCEMENTS

Further enhancing an JEWELLARY Management System involves identifying

opportunities for improvement, adding new features, and refining existing
functionalities to better meet the needs of users and stakeholders. Here are
some areas for further enhancement:

User Experience Improvements:

Conduct usability studies and gather feedback from users to identify pain
points and areas for improvement in the user interface and workflow.
Enhance navigation, layout, and accessibility to make the system more
intuitive and user-friendly.
Implement responsive design to ensure a seamless experience across
devices and screen sizes.

Advanced Reservation Management:

Introduce advanced features for reservation management, such as dynamic
pricing based on demand, availability forecasting, and flexible booking
options.
Implement automated reservation reminders, confirmations, and follow-
ups to improve communication with guests and reduce no-shows.

Enhanced Property Operations:

Integrate IoT (Internet of Things) devices for smart room controls, energy
management, and maintenance monitoring to optimize property operations
and reduce costs.
Implement RFID or NFC technology for keyless entry systems and secure
access control throughout the resort.
Personalized Guest Experiences:
Implement guest profiling and segmentation to personalize the guest
experience based on preferences, past behavior, and demographics.
Offer tailored recommendations, promotions, and incentives to enhance
guest satisfaction and loyalty.

Advanced Analytics and Reporting:

Enhance the system's analytics capabilities to provide deeper insights into
guest behavior, revenue trends, and operational performance.
Implement customizable dashboards and reports for resort owners and
managers to track key metrics and make data-driven decisions.

Integration with External Systems:

Integrate with third-party systems and services, such as online travel
agencies (OTAs), property management systems (PMS), and payment
gateways, to streamline operations and expand distribution channels.
Implement APIs (Application Programming Interfaces) for seamless data
exchange and interoperability with external systems.

Mobile App Development:

Develop a mobile app for guests to access resort services, make
reservations, check-in/out, and receive notifications and updates on their
mobile devices.
Offer mobile apps for resort staff to manage operations, access real-time
information, and communicate with guests and colleagues on the go.

Security and Compliance Enhancements:

Strengthen security measures to protect sensitive data and prevent
unauthorized access or breaches.
Ensure compliance with industry regulations and standards, such as GDPR
(General Data Protection Regulation) and PCI DSS (Payment Card Industry
Data Security Standard).

Customer Support and Training:

Provide comprehensive customer support and training resources to help
users and administrators effectively use and maximize the value of the
system.
Offer online tutorials, knowledge bases, and interactive training sessions to
onboard new users and address common questions and issues.

By further enhancing the JEWELLARY Management System in these areas,

you can improve efficiency, enhance guest satisfaction, and drive business
growth for resort owners and managers. It's essential to prioritize
enhancements based on user feedback, market trends, and business
objectives to ensure that the system continues to evolve and meet the
evolving needs of the resort industry.

Technology Description
1 HTML

HTML stands for HYPER TEXT MARKUP LANGUAGE, which is most widely
used language on web to develop web pages. HTML refers to the way in which Web pages
(HTML documents) are linked together. Thus, the link available on a web page is called
Hypertext.

HTML was created by Berners-Lee in late 1991 but “HTML 2.0” was the first
standard HTML specification which was published in 1995. HTML 4.01 was a major version
of HTML and it was published in late 1999. Though HTML 4.01 version is widely used but
currently we are having HTML-5 version which is an extension to HTML 4.01, and this version
was published in 2012.

As its name suggests, HTML is a Mark-up Language which means you use HTML
to simply “mark-up” a text document with tags that tells a web browser how to structure it to
display.

Originally, HTML was develop with the intent of defining the structure of
documents like heading, paragraph, lists, and so forth to facilitate the sharing of scientific
information between researchers. Now, HTML is being widely used to format web pages with
the help of different tags available in HTML.

2 CSS

Cascading Style Sheet is a style sheet language used for describing

the presentation of a document written in a markup language Although most often used to
set the visual style of web page and user interfaces written in HTML and XHTML, the
language can be applied to any XML document, including plain XML, SVG and XUL,
and is applicable to rendering in speech, or on other media. Along with HTML
and JavaScript, CSS is a cornerstone technology used by most websites to create visually
engaging webpages, user interfaces for web applications, and user interfaces for many
mobile applications.

CSS is designed primarily to enable the separation of document content from

document presentation, including aspects such as the layout, colors, and fonts. This
separation can improve content accessibility, provide more flexibility and control in the
specification of presentation characteristics, enable multiple HTML pages to share
formatting by specifying the relevant CSS in a separate .css file, and reduce complexity
and repetition in the structural content.

The CSS specifications are maintained by the World Wide Web

Consortium (W3C). Internet media type (MIME type) text/css is registered for use with
CSS by RFC 2318 (March 1998). The W3C operates a free CSS validation service for
CSS documents
 CSS has a simple syntax and uses a number of English keywords to specify the
names of various style properties .A style sheet consists of a list of rules. Each rule or
rule-set consists of one or more selectors, and a declaration block.

3 Bootstrap

Bootstrap is a free and open-source, front-endweb framework for

designing websites and web applications. It contains HTML- and CSS-based design
templates for typography, forms, buttons, navigation and other interface components, as
well as optional JavaScript extensions. Unlike many web frameworks, it concerns itself
with front-end development only.

Bootstrap is modular and consists of a series of less stylesheets that

implement the various components of the toolkit. These stylesheets are generally
compiled into a bundle and included in web pages, but individual components can be
included or removed. Bootstrap provides a number of configuration variables that control
things such as color and padding of various components.

Since Bootstrap 2, the Bootstrap documentation has included a customization

wizard which generates a customized version of Bootstrap based on the requested
components and various settings.

As of Bootstrap 4, Sass is used instead of less for the stylesheets.Each

Bootstrap component consists of an HTML structure, CSS declarations, and in some cases
accompanying JavaScript code.

4 My SQL

MySQL is an open source RDBMS that relies on SQL for processing the data
in database. MySQL provides APIs for the languages like C, C++, Eiffel, JAVA, Perl,
PHP and Python. MySQL is most commonly used for web applications and for embedded
applications and has become a popular alternative to proprietary database system because
of its speed and reliability. MySQL can run on UNIX, Windows and Mac OS.

MySQL is an essential part of almost every open source PHP application.

Good examples for PHP/MySQL-based scripts are phpBB, os Cmmerce and Joomla. One
of the most important things about using MySQL is to have a MySQL specialized host.

MySQL is the most popular Open Source Relational SQL database

management system. MySQL is one of the best RDBMS being used for developing web
based software applications.

MySQL is an open source relational database management system (RDBMS)

based on Structured Query Language (SQL). MySQL runs on virtually all platforms,
including Linux, UNIX, and Windows. Although it can be used in a wide range of
applications, MySQL is most often associated with web-based applications and online
publishing and is an important component of an enterprise stack called LAMP. LAMP is
a Web development platform that uses Linux as the operating system, Apache as the Web
server, MySQL as the relational database management system and PHP as the object
oriented scripting language. (Sometimes Perl or Python is used instead of PHP.)

5 PHP

The PHP Hypertext Preprocessor (PHP) is a programming language that

allows web developers to create dynamic content that interacts with databases. PHP is
basically used for developing web based software applications. This tutorial helps you to
build your base with PHP. PHP started out as a small open source project that evolved as
more and more people found out how useful it was. Rasmus Lerdorf unleashed the first
version of PHP way back in 1994.

• PHP is a recursive acronym for "PHP: Hypertext Preprocessor".

• PHP is a server side scripting language that is embedded in HTML. It is
used to manage dynamic content, databases, session tracking, even build
entire e-commerce sites.
 • It is integrated with a number of popular databases, including MySQL,
Postgre SQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
• PHP is pleasingly zippy in its execution, especially when compiled as an
Apache module on the Unix side. The MySQL server, once started,
executes even very complex queries with huge result sets in record-setting
time.
• PHP supports a large number of major protocols such as POP3, IMAP, and
LDAP.
PHP4 added support for Java and distributed object architectures (COM
and CORBA), making n-tier development a possibility for the first time.
• PHP is forgiving: PHP language tries to be as forgiving as possible.
• PHP Syntax is C-Like.

6 JavaScript

JavaScript is a lightweight, interpreted programming language. It is designedfor

creating network-centric applications. It is complimentary to and integrated with Java.
JavaScript is very easy to implement because it is integrated with HTML. It is open and cross-
platform.

JavaScript is a high-level, dynamic, untyped, and interpreted programming

language. It has been standardized in the ECMA Script language specification.
Alongside HTML and CSS, it is one of the three core technologies of World Wide Web content
production; the majority of websites employ it and it is supported by all modern Web browsers
without plug-ins. JavaScript is prototype-based with first-class functions, making it a multi-
paradigm language, supporting object-oriented, imperative, and functional programming
styles.It has an API for working with text, arrays, dates and regular expressions, but does not
include any I/O, such as networking, storage, or graphics facilities, relying for these upon the
host environment in which it is embedded.

Despite some naming, syntactic, and standard library similarities, JavaScript and
Java are otherwise unrelated and have very different semantics. The syntax of JavaScript is
actually derived from C, while the semantics and design are influenced by the Self and Scheme
programming languages.

JavaScript is also used in environments that are not Web-based, such as PDF
documents, site-specific browsers, and desktop widgets. Newer and faster JavaScript virtual
machines (VMs) and platforms built upon them have also increased the popularity of JavaScript
for server-side Web applications. On the client side, JavaScript has been traditionally
implemented as an interpreted language, but more recent browsers perform just-in-time
compilation. It is also used in game development, the creation of desktop and mobile
applications, and server-side network programming with runtime environments such as
Node.js.

CONCLUSION

While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and resources –
that would generate a proper System While making the system, an eye has been kept on
making it as user-friendly, as cost-effective and as flexible as possible. As such one may
hope that the system will be acceptable to any user and will adequately meet his/her needs.
As in case of any system development processes where there are a number of
shortcomings, there have been some shortcomings in the development of this system also.
The project is still under modification.