A PROJECT REPORTED ON

Blockchain-Integrated Workflow Management:

Ensuring Security, Transparency, and Efficiency
ABSTRACT:

This application integrates five comprehensive modules to enhance operational efficiency,

ensure secure data handling, and facilitate seamless collaboration among stakeholders. The
system begins with the Admin Module, where the administrator uploads detailed user data for all
modules, initiating the workflow. The Client Module enables clients to make project
modifications, including algorithm enhancements, which are then forwarded to the admin for
validation. Approved modifications are dynamically assigned to employees based on workload
and expertise, ensuring optimized resource allocation. In the Employee Module, employees
update project requirements and enhancements. If access to specific secure components is
needed, employees send a request to the admin. The admin, in turn, forwards the request to the
Secure Management Module, ensuring a layered and secure access control process. The Secure
Management Module plays a critical role in access verification, utilizing a robust key
management system. The module employs SHA-256 blockchain encryption to securely handle
data and transactions, ensuring integrity, immutability, and traceability of the project workflow.
Once access is granted, management reviews the employee's updates and provides feedback.
Employees incorporate these changes into the project. The system ensures all stakeholders have
visibility into project progress while safeguarding sensitive data. The system concludes with
comprehensive reporting, where the final project updates are communicated to the admin. A
blockchain-powered data module is integrated into the application to maintain a secure, tamper-
proof record of all modifications, ensuring transparency and trust across the workflow. This
integration of blockchain technology ensures that data is not only secure but also transparent,
offering a reliable and immutable trail of project updates. Each module works in synergy to
create a seamless experience, from the initial data upload by the admin to the final project review
and report generation. The application’s dynamic assignment feature ensures that tasks are
distributed effectively, leveraging algorithms that take into account employee availability and
expertise. This reduces project turnaround time and enhances overall productivity. Secure access
protocols, reinforced by blockchain encryption, provide a multi-layered security framework that
minimizes the risk of unauthorized data access. The modular design of the application allows for
easy scalability and adaptability to diverse organizational needs, making it a robust solution for
businesses of all sizes. Moreover, the comprehensive reporting functionality provides
stakeholders with a clear overview of project milestones and progress, fostering accountability
and informed decision-making. The application’s reliance on SHA-256 blockchain for secure
data handling not only enhances trust but also aligns with modern data security standards. By
integrating these advanced technologies and efficient workflows, the HR Management Web
Application stands out as a cutting-edge solution for modern organizational challenges. This
scalable, secure, and efficient platform addresses dynamic needs while ensuring robust data
security and operational transparency.
 CONTENTS

• INTRODUCTION
• INTRODUCTION TO PROJECT
• PURPOSE OF THE PROJECT

• SYSTEM ANALYSIS
• INTRODUCTION
• ANALYSIS MODEL
• SDLC PHASES
• HARDWARE & SOFTWARE REQUIRMENT
• INPUT AND OUTPUT
• LIMITATIONS
• EXISTING STSTEM
• SOLUTION OF THESE PROBLEMS IN PROPOSED SYSTEM

• FEASIBILITY REPORT
• TECHNICAL FEASIBILITY

• OPERATIONAL FEASIBILITY

• ECONOMIC FEASIBILITY

• SOFTWARE REQUIREMENT SPECIFICATIONS

• FUNCTIONAL REQUIREMENTS

• NON-FUNCTIONAL REQUIREMENTS

• PERFORMANCE REQUIREMENTS

• SYSTEM DOVELOPEMENT ENVIRONMENT

• INTRODUCTION TO JAVA

• SERVLETS,JSP
 • JDBC

• HTML,JAVASCRIPT

• FRAMEWORKS

• SYSTEM DESIGN
• INTRODUCTION
• NORMALIZATION
• SYSTEM ARCHITECTURE
• E-R DIAGRAM
• FLOW DIAGRAM
• DFD SYMBOLS
• ACTIVITY DIAGRAM
• USE CASE DIAGRAM
• SEQUENCE DIAGRAM
6.10 CLASS DIAGRAM

• OUTPUT SCREENS

• CODING

• SYSTEM TESTING AND IMPLEMENTATION

• INTRODUCTION

• STRATEGIC APPROACH OF SOFTWARE TESTING

• TESTING PROCEDURES

• SYSTEM SECURITY
10.1. INTRODUCTION

• SECURITY IN SOFTWARE

• CONCLUSION & FUTURE ENHANCEMENT

 CHAPTER-1

1.1 INTRODUCTION TO PROJECT

Managing human resources in modern organizations requires a sophisticated, secure, and

efficient approach to handle complex workflows, enhance collaboration, and safeguard sensitive
data. The HR Management Web Application addresses these needs by integrating advanced
technologies, dynamic task allocation algorithms, and blockchain-powered security protocols.
The application is structured around five key modules: Admin, Client, Employee, Secure
Management, and Management, each contributing to a seamless project lifecycle. From initial
data uploads and task assignments to real-time project updates and secure access control, the
system ensures that stakeholders can collaborate effectively while maintaining transparency and
trust. Leveraging SHA-256 blockchain encryption, the platform guarantees data integrity and
immutability, creating a tamper-proof audit trail of all project interactions. The dynamic task
allocation algorithm optimally assigns tasks based on employee skills and availability, reducing
project turnaround time and maximizing productivity. With real-time collaboration features,
comprehensive reporting, and a scalable modular design, the application is adaptable to
businesses of all sizes. This innovative system not only enhances operational efficiency but also
aligns with modern data security standards, making it a robust solution for evolving HR
management challenges. By addressing the limitations of traditional systems — such as manual
task allocation, fragmented communication, and inadequate data protection — the HR
Management Web Application stands as a cutting-edge platform ready to transform
organizational workflows and foster sustainable growth.
• PURPOSE OF THE SYSTEM

1. Streamlined Workflow: All modules (admin, client, manufacture, testing, and recycle)
are integrated for seamless operations.
2. Quality Assurance: Testing ensures product reliability, and recycled products are
revalidated to maintain quality standards.
3. Nanotechnology Integration: Nanoparticle usage in manufacturing enhances the safety
equipment's durability and functionality.
4. Secure Communication: RSA encryption secures sensitive data, safeguarding
organizational operations from unauthorized access.
5. Client Transparency: Clients can securely access their reports, fostering trust and
collaboration.
CHAPTER-2
 SYSTEM ANALYSIS

2.1 INTRODUCTION

The system design of the HR Management Web Application is carefully structured to provide a
seamless, secure, and efficient solution for modern organizational challenges. It integrates
advanced technologies, dynamic task allocation algorithms, and blockchain-powered security to
ensure smooth workflows, robust data protection, and enhanced collaboration among
stakeholders. The application is built around five core modules: Admin, Client, Employee,
Secure Management, and Management, each contributing to the overall project lifecycle. The
Admin Module manages user data, validates client requests, and assigns tasks based on
employee skills and workload using an intelligent allocation algorithm. The Client Module
allows clients to submit project requirements and modifications, which are reviewed by the
admin for validation and distribution. The Employee Module enables team members to view
tasks, update progress, and request access to secure components. Access requests flow through
the Secure Management Module, which verifies and grants access using SHA-256 blockchain
encryption, maintaining a tamper-proof log of interactions. The Management Module oversees
project updates, provides feedback, and reviews employee submissions to ensure alignment with
client expectations. The application’s data flow design ensures organized and secure data
handling. Users submit data through a web interface, which is validated and stored in a secure
database. The system dynamically allocates tasks, processes access requests, logs interactions,
and generates comprehensive reports for stakeholders. Blockchain encryption safeguards project
data, while role-based access control (RBAC) restricts data visibility based on user roles. Inputs
are validated to prevent malicious entries, preserving data accuracy. The modular design
enhances scalability and flexibility, allowing organizations to customize the system as their
needs evolve. By structuring the application around secure, efficient, and collaborative design
principles, the HR Management Web Application delivers a future-ready solution that enhances
organizational workflows, fosters

2.2 ANALYSIS

SOFTWARE DEVELOPMENT LIFE CYCLE

INTRODUCTION:

The System Development Lifecycle framework is designed to outline a complete

development and implementation process suitable for developing complex applications. SDLC is
a process followed for a software project, within a software organization. It consists of a detailed
plan describing how to develop, maintain, replace and alter or enhance specific software. The life
cycle defines a methodology for improving the quality of software and the overall development
process.

• Business – legislation regulatory requirements, policy, SOP’s, guidelines etc.

• Process – how the business is implemented

• Data – the core business data elements collected for the business

• Application – the gate to the business collecting

• Infrastructure- the servers, network, workstations, etc.

2.3 SDLC Phases:

Stage 1: Scheduling and Requisite investigation:
Requirement analysis is the most important and fundamental stage in SDLC. It is
performed by the senior members of the team with inputs from the customer, the sales
department, market surveys and domain experts in the industry. This information is then used to
plan the basic project approach and to conduct product feasibility study in the economical,
operational, and technical areas.

Planning for the quality assurance requirements and identification of the risks associated
with the project is also done in the planning stage. The outcome of the technical feasibility
study is to define the various technical approaches that can be followed to implement the project
successfully with minimum risks.

Stage 2: Significant necessities:

Once the requirement analysis is done the next step is to clearly define and document the
product requirements and get them approved from the customer or the market analysts. This is
done through .SRS. . Software Requirement Specification document which consists of all the
product requirements to be designed and developed during the project life cycle.

Stage 3: Scheming the product design:

 SRS is the reference for product architects to come out with the best architecture for the
product to be developed. Based on the requirements specified in the SRS, usually more than one
design approach for the product architecture is proposed and documented in a DDS - Design
Document Specification.

This DDS is reviewed by all the important stakeholders and based on various parameters
as risk assessment, product robustness, design modularity, budget and time constraints, the best
design approach is selected for the product.

Stage 4: Structure or Mounting the Product:

In this stage of SDLC the actual development starts and the product are built. The
programming code is generated as per DDS during this stage. If the design is performed in a
detailed and organized manner, code generation can be accomplished without much hassle.
Developers have to follow the coding guidelines defined by their organization and
programming tools like compilers, interpreters, debuggers [Link] used to generate the code.
Different high level programming languages such as C, C++, Pascal, Java, and PHP are used for
coding.

Stage 5: Testing the Product:

This stage is usually a subset of all the stages as in the modern SDLC models, the testing
activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing
only stage of the product, where product defects are reported, tracked, fixed and retested, until
the product reaches the quality standards defined in the SRS.

Stage 6: Consumption in the Market and Safeguarding:

Once the product is tested and ready to be deployed it is released formally in the
appropriate market. Sometime product deployment happens in stages as per the organizations.
Business strategy. The product may first be released in a limited segment and tested in the real
business environment (UAT- User acceptance testing).

The product may be released as it is or with suggested enhancements in the targeting

market segment. After the product is released in the market, its maintenance is done for the
existing customer base.

2.4 HARDWARE AND SOFTWARE REQUIREMENTS

Developing Kit

Processor RAM Disk Space

Eclipse Computer with a 2GB Minimum 20 GB

2.6GHz processor or
higher

Database

MySQL 5.0 Intel Pentium Minimum 512 MB Minimum 20 GB

processor at 2.6GHz Physical Memory; 1
or faster GB Recommended

HeidiSQL 8.3 Intel Pentium Minimum 512 MB Minimum 20 GB

processor at 2.6GHz Physical Memory; 1
 or faster GB Recommended

Software Requirements:

• Front end : core java, css, js, servlet

• Web application : J2ee Frameworks, Hibernate

• Back end : MySQL 5.1

OVERVIEW OF SOFTWARE ENGINEERING:

Software is more than just a program code. A program is an executable code, which serves
some computational purpose. Software is considered to be collection of executable
programming code, associated libraries and documentations. Software, when made for a
specific requirement is called software product.

Engineering on the other hand, is all about developing products, using well-defined, scientific
principles and methods.
Software engineering is an engineering branch associated with development of software
product using well-defined scientific principles, methods and procedures. The outcome of
software engineering is an efficient and reliable software product.

Definitions
IEEE defines software engineering as:

(1) The application of a systematic, disciplined, quantifiable approach to the development,

operation and maintenance of software; that is, the application of engineering to software.

(2) The study of approaches as in the above statement.

Fritz Bauer, a German computer scientist, defines software engineering as:

Software engineering is the establishment and use of sound engineering principles in order to
obtain economically software that is reliable and work efficiently on real machines.

Software Evolution
The process of developing a software product using software engineering principles and
methods is referred to as software evolution. This includes the initial development of software
and its maintenance and updates, till desired software product is developed, which satisfies the
expected requirements.

Evolution starts from the requirement gathering process. After which developers create a
prototype of the intended software and show it to the users to get their feedback at the early
stage of software product development. The users suggest changes, on which several
consecutive updates and maintenance keep on changing too. This process changes to the
original software, till the desired software is accomplished.

Even after the user has desired software in hand, the advancing technology and the changing
requirements force the software product to change accordingly. Re-creating software from
scratch and to go one-on-one with requirement is not feasible. The only feasible and economical
solution is to update the existing software so that it matches the latest requirements.
Software Evolution Laws
Lehman has given laws for software evolution. He divided the software into three different
categories:

• S-type (static-type) - This is a software, which works strictly according to

defined specifications and solutions. The solution and the method to achieve it, both are
immediately understood before coding. The s-type software is least subjected to changes
hence this is the simplest of all. For example, calculator program for mathematical
computation.

• P-type (practical-type) - This is a software with a collection of [Link] is

defined by exactly what procedures can do. In this software, the specifications can be
described but the solution is not obvious instantly. For example, gaming software.

• E-type (embedded-type) - This software works closely as the requirement of real-

world environment. This software has a high degree of evolution as there are various
changes in laws, taxes etc. in the real world situations. For example, Online trading
software.

E-Type software evolution

Lehman has given eight laws for E-Type software evolution -

• Continuing change - An E-type software system must continue to adapt to the real world
changes, else it becomes progressively less useful.

• Increasing complexity - As an E-type software system evolves, its complexity tends to

increase unless work is done to maintain or reduce it.

• Conservation of familiarity - The familiarity with the software or the knowledge about
how it was developed, why was it developed in that particular manner etc. must be
retained at any cost, to implement the changes in the system.
 • Continuing growth- In order for an E-type system intended to resolve some business
problem, its size of implementing the changes grows according to the lifestyle changes of
the business.

• Reducing quality - An E-type software system declines in quality unless rigorously

maintained and adapted to a changing operational environment.

• Feedback systems- The E-type software systems constitute multi-loop, multi-level

feedback systems and must be treated as such to be successfully modified or improved.

• Self-regulation - E-type system evolution processes are self-regulating with the

distribution of product and process measures close to normal.

• Organizational stability - The average effective global activity rate in an evolving E-

type system is invariant over the lifetime of the product.

Software Paradigms
Software paradigms refer to the methods and steps, which are taken while designing the
software. There are many methods proposed and are in work today, but we need to see where in
the software engineering these paradigms stand. These can be combined into various categories,
though each of them is contained in one another:
Programming paradigm is a subset of Software design paradigm which is further a subset of
Software development paradigm.

Software Development Paradigm

This Paradigm is known as software engineering paradigms where all the engineering concepts
pertaining to the development of software are applied. It includes various researches and
requirement gathering which helps the software product to build. It consists of –

• Requirement gathering

• Software design

• Programming

Software Design Paradigm

This paradigm is a part of Software Development and includes –

• Design

• Maintenance

• Programming

Programming Paradigm
This paradigm is related closely to programming aspect of software development. This includes
–

• Coding

• Testing

• Integration

Need of Software Engineering

The need of software engineering arises because of higher rate of change in user requirements
and environment on which the software is working.
 • Large software - It is easier to build a wall than to a house or building, likewise, as the
size of software become large engineering has to step to give it a scientific process.

• Scalability- If the software process were not based on scientific and engineering
concepts, it would be easier to re-create new software than to scale an existing one.

• Cost- As hardware industry has shown its skills and huge manufacturing has lower down
the price of computer and electronic hardware. But the cost of software remains high if
proper process is not adapted.

• Dynamic Nature- The always growing and adapting nature of software hugely depends
upon the environment in which user works. If the nature of software is always changing,
new enhancements need to be done in the existing one. This is where software
engineering plays a good role.

• Quality Management- Better process of software development provides better and

quality software product.

Characteristics of good software

A software product can be judged by what it offers and how well it can be used. This software
must satisfy on the following grounds:

• Operational

• Transitional

• Maintenance

Well-engineered and crafted software is expected to have the following characteristics:

Operational
This tells us how well software works in operations. It can be measured on:

• Budget
 • Usability

• Efficiency

• Correctness

• Functionality

• Dependability

• Security

• Safety

Transitional
This aspect is important when the software is moved from one platform to another:

• Portability

• Interoperability

• Reusability

• Adaptability

Maintenance
This aspect briefs about how well a software has the capabilities to maintain itself in the ever-
changing environment:

• Modularity

• Maintainability

• Flexibility

• Scalability

In short, Software engineering is a branch of computer science, which uses well-defined

engineering concepts required to produce efficient, durable, scalable, in-budget and on-time
software products.
SOFTWARE DEVELOPMENT LIFE CYCLE
The Software Development Life Cycle is a process that ensures good software is built.
Each phase in the life cycle has its own process and deliverables that feed into the next
phase. There are typically 5 phases starting with the analysis and requirements gathering
and ending with the implementation. Let’s look in greater detail at each phase:

Stage 1: Scheduling and Requisite Analysis

During the discovery phase our team conducts a detailed requirement
analysis and creates a work-breakdown structure.

Stage 2: Scheming the product design

We identify the design and architecture of the project. SRS is the reference for product
architects to come out with the best architecture for the product to be developed.
 Stage 3: Structure or Mounting the Product
In this stage of SDLC the actual development starts and the product is built. Different
high level programming languages such as C, C++, Pascal, Java, C# and PHP are used
for coding.

Stage 4: Testing the Product

Testing is the last phase of the Software Development Life Cycle before the software is
delivered to customers. During testing, experienced testers start to test the system against
the requirements.

Stage 5: Consumption in the Market and Safeguarding

Once the product has been fully tested and no high priority issues remain in the software,
it is time to deploy to production where customers can use the system.

2.5 Input and Output

The HR Management Web Application incorporates a well-structured input and output design to
ensure secure data handling, accurate information processing, and seamless communication
between system entities. This design is essential for capturing reliable data and generating
meaningful outputs that drive project progress and decision-making.

Input Design
Input:

 Entities, including administrators, clients, and employees, must register and authenticate
their accounts to access the system. User credentials and relevant details are securely
stored in a database, ensuring robust identification and access control.
 Clients upload project requirements and proposed modifications, such as algorithm
enhancements or resource specifications, through an intuitive interface.
 Employees provide updates on project tasks, request access to secure components, and
submit final deliverables.

Purpose: The input design aims to capture and manage accurate, reliable data, serving as the
foundation for efficient project management and secure data handling.

Input States:

 Users maintain their data within a secure database (e.g., MySQL Server, SQL Server)
that aligns with organizational requirements.
 The system dynamically processes inputs, validates data integrity, and routes the
information to the appropriate modules.

Input Media:

 Users interact with the application through an interface designed for easy data entry and
management.
 Admins oversee input validation, manage access requests, and trigger secure workflows.
 The Secure Management Module ensures all sensitive inputs are encrypted, preventing
unauthorized access or tampering.

Output Design

Output:

 Only authenticated and authorized users can access project data, ensuring controlled and
secure information usage.
  The system automatically calculates relevant project metrics, such as task completion
rates, workload distribution, and security logs.
 Employees receive real-time feedback on project enhancements, while clients can track
progress through detailed status updates.
 The application generates comprehensive reports summarizing project milestones, access
logs, and final deliverables, fostering transparency and accountability.

2.6 LIMITATIONS

 Inefficient Task Allocation and Resource Management: Traditional systems often rely on
manual processes for task assignment, which can lead to imbalances in workload distribution.
Without automated algorithms, task allocation is prone to errors, resulting in delays and
inefficiencies in project execution.

 Lack of Real-Time Collaboration and Transparency: Existing systems generally lack an

integrated platform for real-time updates and collaboration among clients, employees, and
management. Clients face difficulties in tracking project progress, and employees are unable to
access and update project information seamlessly, leading to poor communication and
transparency.

 Inadequate Data Security and Access Control: Data security in traditional systems is often
not robust, with insufficient measures to protect sensitive information from unauthorized access.
Without encryption technologies like blockchain, the integrity of data and project updates cannot
be guaranteed, making the system vulnerable to tampering.

 Limited Scalability and Adaptability: Traditional HR management systems often struggle

to scale with growing organizational needs. They lack the flexibility to adapt to dynamic project
requirements or integrate new technologies, limiting their ability to handle increasing
complexities or changing business environments effectively.

2.7 PROBLEMS IN EXISTING SYSTEM

The existing system for HR management often lacks the integration of advanced technologies and
seamless workflows, leading to inefficiencies in task allocation, collaboration, and data security. In
traditional systems, admins manually manage user data and task assignments, which can result in delays
and uneven workload distribution. Clients may face difficulties in communicating project modifications
or tracking progress, as there is no streamlined platform to facilitate real-time updates or collaboration.
Employees often encounter challenges in accessing secure components or submitting project updates due
to inadequate access control mechanisms. Additionally, management struggles to oversee and review
project enhancements effectively, as traditional systems lack a centralized reporting [Link]
security in existing systems is also a significant concern, with sensitive information being prone to
unauthorized access or tampering. Without robust encryption methods, the integrity of project updates
and access requests cannot be guaranteed.

2.8 PROPOSED SYSTEM

The proposed HR Management Web Application is designed to address the limitations of

traditional systems by integrating advanced technologies and modular workflows. It uses an
algorithm-driven approach for task allocation, ensuring optimal resource utilization by
dynamically assigning tasks based on employee skills and project requirements. The application
enables real-time collaboration, allowing clients, employees, and management to track project
progress and make necessary updates [Link] SHA-256 blockchain encryption, the
system guarantees data security by providing tamper-proof access logs and ensuring the integrity
of project modifications. This blockchain integration enhances transparency and trust among
stakeholders. The Secure Management Module ensures robust access control, validating and
granting secure access only to authorized [Link] system's modular design makes it highly
scalable and adaptable, allowing organizations to customize the application according to their
unique needs. It ensures smooth collaboration across various roles, from client communication to
project review, providing a clear and transparent overview of project milestones. By leveraging
advanced algorithms and secure technologies, the proposed system improves operational
efficiency, reduces delays, and ensures data integrity.

Advantage of Proposed System:

 Efficient Task Allocation: The algorithm-driven task assignment ensures optimal resource
utilization by dynamically matching tasks to employees based on their skills, workload, and
project deadlines, reducing errors and improving productivity.
 Real-Time Collaboration: Clients, employees, and management can collaborate seamlessly
in real-time, ensuring transparency and improving communication across all stages of the
project, from modification to final delivery.

 Enhanced Data Security: With the integration of SHA-256 blockchain encryption, the
system ensures data integrity, providing a tamper-proof record of project updates, access logs,
and modifications, thereby enhancing security.

 Transparent Audit Trail: Blockchain technology creates an immutable audit trail, allowing
stakeholders to track all system interactions, ensuring transparency and accountability in the
project workflow.
 CHAPTER-3

FEASIBILITY REPORT

3.1 Technical Feasibility

 Blockchain Integration: The incorporation of blockchain technology ensures data

security and integrity, making it technically feasible to securely record and store
information related to HR processes, employee data, and project updates. This enhances
system reliability and protects against unauthorized data manipulation.
  User-Friendly Interface: The implementation of an intuitive and accessible interface
makes the application easy to navigate, allowing stakeholders to manage tasks, track
progress, and access relevant project information without extensive training.
 Real-Time Updates: The system’s ability to deliver real-time updates ensures that users
have access to the most current data regarding task assignments, project modifications,
and access requests, supporting informed decision-making.
 Scalability: The web application's modular design allows for seamless scalability,
ensuring it can accommodate increasing user traffic, expanding data volume, and
evolving business requirements as organizations grow.

3.2 Operational Feasibility

 Accessibility: A responsive and user-friendly design ensures that all stakeholders,

including admins, clients, and employees, can easily access and use the platform across
devices, facilitating smooth interactions and streamlined workflows.
 Reliability: Real-time collaboration and blockchain-powered security features contribute
to system reliability, ensuring that critical data remains accurate, accessible, and tamper-
proof, even as the platform scales.
 Trust and Accountability: By leveraging blockchain for immutable data records, the
application fosters trust among users, promoting ethical practices and enhancing
accountability in task management and decision-making processes.
 Efficiency in Workflow Management: The dynamic task allocation algorithm optimizes
resource utilization, reducing bottlenecks and delays. This ensures that projects are
executed on time and resources are distributed effectively, further enhancing operational
feasibility.

3.3 Economic Feasibility

• Cost Reduction: By streamlining processes and reducing overhead costs associated with
traditional record-keeping methods, the web application contributes to economic
feasibility by improving operational efficiency and cost-effectiveness.
• Revenue Generation: Enhancing brand reputation and consumer loyalty through
transparency and trust-building measures can lead to increased sales and revenue
generation for cosmetic manufacturers using the platform.

• Market Efficiency: By facilitating informed consumer choices and promoting market

transparency, the web application promotes economic feasibility by fostering market
efficiency and competitiveness within the cosmetic industry.
CHAPTER-4
 SOFTWARE REQUIREMENT
SPECIFICATION

4.1 INTRODUCTION

The purpose of this document is to present a detailed description of the Web

application system. It will explain the purpose and features of the system, the interfaces of the
system, what the system will do, the constraints under which it must operate and how the system
will react to external stimuli. This document is intended for both the stakeholders and the
developers of the system and will be proposed to the Regional Historical Society for its approval.

PURPOSE
The purpose of this Software Requirement Specification (SRS) is to help the project. It is
provided with some requirements which are used in the Transaction Mercator System. All parts;
design, coding and testing will be prepared with helping of SRS. The purpose of this document is
to detail the requirements placed on the Transaction Mercator System and serves as a contract
between the customer and the developers as to what is to be expected of the stock exchange, and
how the components of the system are working with each other with external systems.

This document will be checked by the group member’s supervisor and it will corrected by
members if supervisor orders.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

• Developing the system, which meets the SRS and solving all the requirements of the
system?

• Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.

• Submitting the required user manual describing the system interfaces to work on it and
also the documents of the system.

• Conducting any user training that might be needed for using the system.

• Maintaining the system for a period of one year after installation.

• FUNCTIONAL REQUIREMENTS:

• Following is a list of functionalities of the browsing enabled system.

• An Activity with a UI that allows you to browser settings. Provide a second Activity that
allows users to access the share with permission from the administrator. Handle activity
lifecycle appropriately. A precondition for any points in this part of the grade is code that
compiles and runs.
 • Your application should allow a user to browse the shares, buy and sell the shares with
specific metadata. The assignment requires you to create a UI for browsing and a UI for
integrating the two.
• The Net beans provide a number of useful layout components, views, and tools that you
may want to use to create your location browser. As with the final project, you should
design your application to only use the buttons on the Key board and mouse as input.
Your application should use the Key board, Mouse and keywords.

4.2 NON-FUNCTIONAL REQUIREMENTS:

• The system should be supported Net beans. The member should use the System browser.
Each member should have a separate system.
• The system should ask the username and password to open the application. It doesn’t
permit to unregistered user to access the System.
• The system should have Role based System functions access. Approval Process has to be
defined.
• The system should have Modular customization components so that they can be reused
across the implementation.
• These are the mainly following:
• Secure access of confidential data. 24 X 7 availability
• Better component design to get better performance at peak time
• Flexible service based architecture will be highly desirable for future extension

4.3 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the [Link]

specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into required
environment. It rests largely in the part of the users of the existing system to give the required
specifications because they are the people who finally use the system. This is because the
requirements have to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system once it has been
designed and on the other hand designing a system, which does not cater to the requirements of
the user, is of no use.

The requirement specification for any system can be broadly stated as given below:

• The system should be able to interface with the existing system

• The system should be accurate
• The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
CHAPTER-5
SYSTEM DEVELOPEMENT ENVIRONMENT

5.1 INTRODUCTION TO JAVA

About Java:

Initially the language was called as “oak” but it was renamed as “Java” in [Link] primary
motivation of this language was the need for a platform-independent (i.e. Architecture neutral)
language that could be used to create software to be embedded in various consumer electronic
devices.
 • Java is a programmer’s language
• Java is cohesive and consistent
• Except for those constraints imposed by the Internet environment. Java gives the
programmer, full control
Finally Java is for Internet Programming where c was to System Programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of
objects that can move about freely in Cyberspace. In a network, two categories of objects are
transmitted between the server and the personal computer. They are passive information and
Dynamic active programs. In the areas of Security and probability. But Java addresses these
concerns and by doing so, have opened the door to an exciting new form of program called the
Applet.

Applications and applets. An application is a program that runs on our Computer under the
operating system on that computer. It is more or less like one creating, using C or C++.Java’s
ability to create Applets makes it important. An Applet I son application, designed to be
transmitted over the Internet and executed by a Java-compatible web browser. An applet I
actually a tiny Java program, dynamically downloaded across the network, just like an image.
But the difference is, it is an intelligent program, not just a media file. It can be reacted to the
user input and dynamically change.

Java Architecture

Java architecture provides a portable, robust, high performing environment for development.
Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then
interpreted on each platform by the run-time environment. Java is a dynamic system, able to load
code when needed for a machine in the same room or across the planet.

When you compile the code, the Java compiler creates machine code (called byte code) for
a hypothetical machine called a Java Virtual Machine (JVM). The JVM is supposed to be
executed the byte code. The JVM is created for the overcoming the issue of probability. The
code is written and compiled for one machine and interpreted on all [Link] is
called a Java Virtual Machine.

Compiling and interpreting Java source code.

During run-time the Java interpreter tricks the byte code file into thinking that it is
running on a Java Virtual Machine. In reality this could be an Intel Pentium windows 95 or

Sun SPARCstation running Solaris or Apple Macintosh running system and all could receive
code from any computer through the internet and run the Applets.

Simple:

Java was designed to be easy for the Professional programmer to learn and to use effectively. If
you are an experienced C++ Programmer. Learning Java will oriented features of C++. Most of
the confusing concepts from C++ are either left out of Java or implemented in a cleaner, more
approachable manner. In Java there are a small number of clearly defined ways to accomplish a
given task.

Object oriented

Java was not designed to be source-code compatible with any other language. This allowed the
Java team the freedom to design with a blank state. One outcome of this was a clean, usable,
pragmatic approach to objects. The object model in Java is simple and easy to extend, while
simple types, such as integers, are kept as high-performance non-objects.

Robust

The multi-platform environment of the web places extraordinary demands on a program, because
the program must execute reliably in a variety of systems. The ability to create robust programs.
Was given a high priority in the design of Java. Java is strictly typed language; it checks your
code at compile time and runtime.

Java virtually eliminates the problems of memory management and deal location, which is
completely automatic. In a well-written Java program, all run-time errors can and should be
managed by your program.

5.2 SERVLETS/JSP

A Servlet is a generic server extension. Java classes that can be loaded dynamically to expand
the functionality of a server. Servlets are commonly used with web servers. Where they can take
the place CGI scripts.

A Servlet is similar to proprietary server extension, except that it runs inside a Java Virtual
Machine (JVM) on the server, so it is safe and portable Servlets operate solely within the domain
of the server.

Unlike CGI and Fast CGI, which use multiple processes to handle separate program or
separate requests, separate threads within the web server process handle all servlets. This means
that servlets are all efficient and scalable.

Servlets are portable; both across operating systems and also across web servers. Java
Servlets offer the best possible platform for web application development.

Servlets are used as a replacement for CGI scripts on a web server; they can extend any sort
of server, such as a mail server that allows servlets extend its functionality, perhaps by
performing a virus scan on all attached documents or handling mail filtering tasks.

Servlets provide a Java-based solution used to address the problems currently associated
with doing server-side programming including inextensible scripting solutions platform-specific
API’s and incomplete interface.

Servlets are objects that conform to a specific interface that can be plugged into a Java-
based server. Servlets are to the server-side what applets are to the server-side what applets are to
the client-side-object byte codes that can be dynamically loaded off the net. They differ from
applets in than they are faceless objects(without graphics or a GUI component).They serve as
platform independent, dynamically loadable, pluggable helper byte code objects on the server
side that can be used to dynamically extend server-side functionality.

For example an HTTP servlet can be used to generate dynamic HTML content when you use servlets
to do dynamic content you get the following advantages:

They’re faster and cleaner then CGI scripts

They use a standard API (the servlet API)

They provide all the advantages of Java (run on a variety of servers without needing to be
rewritten)

Attractiveness of servlets:

They are many features of servlets that make them easy and attractive to use these include:

• Easily configure using the GUI-based Admin tool]

• Can Be Loaded and Invoked from a local disk or remotely across the network.
• Can be linked together or chained, so that on servlet can call another servlet or
several servlets in sequence.
• Can be called dynamically from within HTML, pages using server-side include-
tags.
• Are secure-even when downloading across the network, the servlet security model
and servlet and box protect your system from unfriendly behavior.
Advantages of the Servlet API
One of the great advantages of the servlet API is protocol independent. It assumes nothing about:

• The protocol being used to transmit on the net

• How it is loaded

• The server environment it will be running in

These quantities are important, because it allows the Servlet API to be embedded in many
different kinds of servers.

There are other advantages to the servlet API as well these include:

• It’s extensible-you can inherit all your functionality from the base classes made available
to you

• It’s small, simple, and easy to use.

Features of Servlets:

• Servlets are persistent. Servlet is loaded only by the web server and can maintain
services between requests.

• Servlets are fast. Since servlets only need to be l\loaded once, they offer much better
performance over their CGI counterparts.

• Servlets are platform independent.

• Servlets are extensible Java is a robust, object-oriented programming language, which

easily can be extended to suit your needs.

• Servlets are secure

 • Servlets are used with a variety of clients.

Every servlet must implement the [Link] interface. Most servlets implement it by
extending one of two [Link] or [Link]. A
protocol-independent servlet should subclass Generic-Servlet. While an Http servlet should
subclass HttpServlet, which is itself a subclass of Generic-servlet with added HTTP-specific
functionality.

Unlike a java program, a servlet does not have a main () method, Instead the server in the
process of handling requests invoke certain methods of a servlet. Each time the server
dispatches a request to a servlet, it invokes the servlets Service () method.

A generic servlet should override its service () method to handle requests as appropriate
for the servlet. The service() accepts two parameters a request object and a response object.
The request object tells the servlet about the request, while the response object is used to
return a response

In Contrast. an Http servlet usually does not override the service () method. Instead, it overrides
do Get () to handle GET requests and do Post () to handle Post requests. An Http servlet can
override either or both of these modules the service() method of HttpServlet handles the setup
and dispatching to all the do XXX() methods. Which is why it usually should not be overridden

The remainders in the javax. servlet and Java. servlet. http. The package is largely supported
class’s. TheServletRequest and ServletResponse classes in Java. servlet is provided access to
generic server requests and responses while HttpServletRequest and HttpServletResponse classes
in [Link] provide access to generic server requests and responses while
HttpServletRequest and HttpServletResponse in [Link] provide access a HTTP
requests and responses. The [Link] provide contains an HttpSession class that
provides built-in session tracking functionality and Cookie class that allows quick setup and
processing Http Cookies.
Loading Servlets:

Servlets can be loaded from their places. From a directory that is in the CLASSPATH. The
CLASSPATH of the Java Webserver includes service root/classes/, which is where the system
classes reside

From the <SERVICE_ROOT/servlets/directory. This is not in the server’s class path. A class
loader is used to create servlet form this directory. New servlets can be added-existing servlets
can be recompiled and the server will notice these changes. From a remote location. For this a
code base like [Link] is required in addition to the servlet’s class name.
Refer to the admin GUI docs on servlet section to see how to set this up.

Loading Remote Servlets

Remote servlets can be loaded from:

• Configuring the admin Tool to setup automatic loading of remote servlets.

• Selection up server side include tags in .html files

Invoking Servlets

A servlet invoker is a servlet that invokes the “server” method of a named servlet. If the servlet is
not loaded into the server, then the invoker first loads the servlet (either form local disk or from
the network) and the then invokes the “service” [Link] like applets, local servlets in the
server can be identified by just the class [Link] other words, if a servlet name is not absolute. It
is treated as local.

A Client cans Invoke Servlets in the Following Ways:

• The client can ask for a document that is served by the servlet.
 • The client(browser) can invoke the servlet directly using a URL, once it has been
mapped using the SERVLET ALIASES Section of the admin GUI

• The servlet can be invoked through server side include tags.

• The servlet can be invoked by placing it in the servlet/directory

• The servlet can be invoked by using it in a filter chain

The Servlet Life Cycle:-

The Servlet life cycle is one of the most exciting features of [Link] life cycle is a powerful
hybrid of the life cycles used in CGI programming and lower-level NSAPI and ISAPI
programming.

The Servlet life cycle allows servlet engines to address both the performance and resource
problems of CGI and the security consents of low level server API programming.

The servlet life cycle is highly flexible Servers have significant leeway in how they choose to
support servlets. The only hard and fast rule is that a servlet engine must conform to the
following life cycle contract:

• Create and initialize the servlets

• Handle zero or more service for clients

• Destroy the servlet and then garbage collects it.

It’s perfectly legal for a servlet t be loaded, created an initialized in its own JVM, only
to be destroyed a garbage collected without handling any client request or after handling just one
request

The most common and most sensible life cycle implementations for HTTP servlets are:
Single Java virtual machine and astatine persistence.

Init and Destroy:-

 Just like Applets servlets can define init () and destroy () methods, A servlets init
(ServiceConfig) method is called by the server immediately after the server constructs the servlet
instance. Depending on the server and its configuration, this can be at any of these times

• When the server states

• When the servlet is first requested, just before the service() method is invoked

• At the request of the server administrator

The init () method is typically used to perform servlet initialization creates or loading objects
that are used by the servlet in the handling of its request. In order to provide a new Servlet any
information about itself and its environment, a server has to call a servletsinit () method and pass
an object that implement the ServletConfig interface.

This ServletConfig object supplies a servlet with information about its initialization
parameters. These parameters are given to the servlets and are not associated with any single
[Link] can specify initial values, such as where a counter should begin counting, or
default values, perhaps a template to use when not specified by the request,

The server calls a servlet destroy () method when the servlet is about to be unloaded. In the
destroy () method, a Servlet should free any resources it has acquired that will not be garbage
collected. The destroy () method also gives a servlet a chance to write out its unsaved. Cached
information or any persistent information that should be read during the next call to init ().

USER AUTHORIZATION:

One way to perform session tracking is to leverage the information that comes with User
authorization. When a web server restricts access to some of its resources to only those clients
that log in using a recognized username and password. After the client logs in, the username is
available to a servlet through getRemoteUser ().
When use the username to track the session. Once a user has logged in, the browser remembers
her user name and resends the name and password as the user views new pages on the site. A
servlet can identify the user through her username and they’re by Track her session.

The biggest advantage of using user authorization to perform session tracking is that it’s easy to
implement. Simply tell the protect a set of pages, and use getRemoteUser() to identify each
client. Another advantage is that the technique works even when the user accesses your site form
or exits her browser before coming back.

The biggest disadvantage of user authorization is that it requires each user to register for an
account and then log in each time the starts visiting your site. Most users will tolerate registering
and logging in as a necessary evil when they are accessing sensitive information, but it’s all
overkill for simple session [Link] problem with user authorization is that a user cannot
simultaneously maintain more than one session at the same site.

Hidden Form Fields:

One way to support anonymous session tracking is to use hidden from the fields. As the name
implies, these are fields added to an HTML, from that are not displayed in the client’s browser,
they are sent back to the server when the form that contains them is submitted.

In a sense, hidden form fields define constant variables for a form. For a servlet receiving a
submitted form, there is no difference between a hidden field and a visible filed.

As more information is associated with a client’s session. It can become burdensome to pass it
all using hidden form fields. In these situations, it’s possible to pass on just a unique session ID
that identifies as a particular client session.

That session ID can be associated with complete information about its session that is stored on
the server.
The advantage of hidden form fields is their ubiquity and support for anonymity. Hidden fields
are supported in all the popular browsers, they demand on special server requirements, and they
can be used with clients that haven’t registered or logged in.

The major disadvantage with this technique, however, is that works only for a sequence of
dynamically generated forms, the technique breaks down immediately with static documents,
emailed documents bookmarked documents and browser shutdowns.

URL Rewriting:

URL rewriting is another way to support anonymous session tracking, With URL rewriting every
local URL the user might click on is dynamically modified. Or rewritten, to include extra,
information. The extra information can be in the form of extra path information, added
parameters, or some custom, [Link] change. Due to the limited space available in
rewriting a URL, the extra information is usually limited to a unique session.

Each rewriting technique has its own advantage and disadvantage

Using extra path information works on all servers, and it works as a target for forms that use
both the Get and Post methods. It does not work well if the servlet has to use the extra path
information as true path information

The advantages and disadvantages of URL. Rewriting closely match those of hidden form
fields, The major difference is that URL rewriting works for all dynamically created documents,

such as the Help servlet, not just forms. With the right server support, custom URL rewriting can
even work for static documents.

Persistent Cookies:
A fourth technique to perform session tracking involves persistent cookies. A cookie is a bit of
information. Sent by a web server to a browser that can later be read back form that browser.
When a browser receives a cookie, it saves the cookie and there after sending the cookie back to
the server each time it accesses a page on that server, subject to certain rules. Because a cookie’s
value can uniquely identify a client, cookies are often used for session tracking.

Persistent cookies offer an elegant, efficient, easy way to implement session tracking.
Cookies provide as automatic an introduction for each request, as we could hope for. For each
request, a cookie can automatically provide a client’s session ID or perhaps a list of clients'
performance. The ability to customize cookies gives them extra power and versatility.

The biggest problem with cookies is that browsers don’t always accept cookies sometimes
this is because the browser doesn’t support cookies. More often it’s because the browser doesn’t
support cookies. More often it’s because the user has specifically configured the browser to
refuse cookies.

The power of servlets:

The power of servlets is nothing but the advantages of servlets over other approaches,
which include portability, power, efficiency, endurance, safety, elegance, integration,
extensibility and flexibility.

Portability:

As servlets are written in Java and conform to a well defined and widely accepted API. They are
highly portable across operating systems and across server implementation
 We can develop a servlet on a Windows NT machine running the Java web server and later
deploy it effortlessly on a high-end UNIX server running Apache. With servlets we can really
“write once, serve everywhere”

Servlet portability is not the stumbling block it so often is with applets, for two reasons

First, Servlet portability is not mandatory, i.e. servlets have to work only on server machines
that we are using for development and deployment

Second, servlets avoid the most error-prone and inconstancy implemented portions of the
Java languages.

Power:

Servlets can harness the full power of the core Java. API’s: such as Networking and Url access,
multithreading, image manipulation, data compression, database connectivity,
internationalization, remote method invocation (RMI) CORBA connectivity, and object
serialization, among others.

Efficiency and Endurance:

Servlet invocation is highly efficient, Once a servlet is loaded it generally remains in the server’s
memory as a single object instance, Thereafter the server invokes the servlet to handle a request
using a simple, light weighted method [Link] the CGI, there’s no process to spawn or
interpreter to invoke, so the servlet can begin handling the request almost immediately, Multiple,
concurrent requests is handled the request almost immediately. Multiple, concurrent requests are
handled by separate threads, so servlets are highly scalable.

Servlets in general are enduring objects. Because a servlet stays in the server’s memory as
a single object instance. It automatically maintains its state and can hold onto external resources,
such as database connections.

Safety:

Servlets support safe programming practices on a number of [Link] they are written in Java,
servlets inherit stronger type safety of the Java language. In addition the servlet API is
implemented to be type safe. Java’s automatic garbage collection and lack of pointers mean that
servlets are generally safe from memory management problems like dangling pointers invalid
pointer references and memory leaks.

Servlets can handle errors safely, due to Java exception – handling mechanism. If a servlet
divides by zero or performs some illegal operations, it throws an exception that can be safely
caught and handled by the server.

A server can further protect itself from servlets through the use of Java security manager. A
server can execute its servlets under the watch of a strict security manager.

Elegance:

The elegance of the servlet code is [Link] code is clean, object oriented modular and
amazingly simple one reason for this simplicity is the served API itself. This includes methods
and classes to handle many of the routine chores of servlet [Link] advanced to
operations like cookie handling and session tracking are abstracted into convenient classes.

Integration:

Servlets are tightly integrated with the server. This integration allows a servlet to cooperate with
the server in two ways. For e.g.: a servlet can use the server to translate file paths, perform
logging, check authorization, perform MIME type mapping and in some cases even add users to
the server’s user database.

Extensibility and Flexibility:

The servlet API is designed to be easily extensible. As it stands today the API includes classes
that are optimized for HTTP servlets. But later it can be extended and optimized for another type
of [Link] is also possible that its support for HTTP servlets could be further enhanced.

Servlets are also quite flexible; Sun also introduced Java server pages. Which offer a way to
write snippets of servlet code directly within a static HTML page using syntax similar to
Microsoft’s Active server pages (ASP

5.3 JDBC
What is JDBC?

Any relational database. One can write a single program using the JDBC API,and the JDBC is a
Java Api for executing SQL,Statements(As a point of interest JDBC are trademarks names and is
not an acronym; nevertheless, Jdbc is often thought of as standing for Java Database
Connectivity. It consists of a set of classes and interfaces written in the Java Programming
[Link] provides a standard API for tool/database developers and makes it possible to
write database applications using a pure Java API

Using JDBC, it is easy to send SQL statements to virtually program will be able to send
SQL Statements to the appropriate database. The Combination of Java and JDBC lets a
programmer writes it once and run it anywhere.

What Does JDBC Do?

Simply put, JDBC makes it possible to do three things

• Establish a connection with a database

• Send SQL statements

• Process the results

• JDBC Driver Types

• The JDBC drivers that we are aware of this time fit into one of four categories

• JDBC-ODBC Bridge plus ODBC driver

• Native-API party-Java driver

• JDBC-Net pure Java driver

• Native-protocol pure Java driver

An individual database system is accessed via a specific JDBC driver that implements the
[Link] interface. Drivers exist for nearly all-popular RDBMS systems, through few are
available for free. Sun bundles a free JDBC-ODBC bridge driver with the JDK to allow access to
a standard ODBC, data sources, such as a Microsoft Access database, Sun advises against using
the bridge driver for anything other than development and very limited development.

JDBC drivers are available for most database platforms, from a number of vendors and in a
number of different flavors. There are four driver categories

Type 01-JDBC-ODBC Bridge Driver

Type 01 drivers use a bridge technology to connect a Java client to an ODBC database service.
Sun’s JDBC-ODBC bridge is the most common type 01 driver. These drivers implemented using
native code.

Type 02-Native-API party-Java Driver

Type 02 drivers wrap a thin layer of Java around a database-specific native code libraries for
Oracle databases, the native code libraries might be based on the OCI(Oracle call Interface)
libraries, which were originally designed for c/c++ programmers, Because type-02 drivers are

implemented using native code. In some cases, they have better performance than their all-Java
counterparts. They add an element of risk, however, because a defect in a driver’s native code
section can crash the entire server

Type 03-Net-Protocol All-Java Driver

Type 03 drivers communicate via a generic network protocol to a piece of custom middleware.
The middleware component might use any type of driver to provide the actual database access.
These drivers are all Java, which makes them useful for applet deployment and safe for servlet
deployment

Type-04-native-protocol All-Java Driver

Type o4 drivers are the most direct of the lot. Written entirely in Java, Type 04 drivers
understand database-specific networking. Protocols and can access the database directly without
any additional software

JDBC-ODBC Bridge

If possible use a Pure Java JDBC driver instead of the Bridge and an ODBC driver. This
completely eliminates the client configuration required by [Link] also eliminates the potential
that the Java VM could be corrupted by an error in the native code brought in by the Bridge (that
is, the Bridge native library, the ODBC driver manager library, library, the ODBC driver library,
and the database client library).

WHAT IS The JDBC-ODBE Bridge?

The JDBC-ODBC Bridge is a Jdbc driver, which implements JDBC operations by translating
them into ODBC operations. To ODBC it appears as a normal application program. The Bridge
is implemented as the [Link] Java package and contains a native library used to access
[Link] Bridge is a joint development of Intersolv and Java Soft.

5.4 HTML, JAVASCRIPT

Hypertext Markup Language(HTML), the languages of the World Wide Web (WWW), allows
users to produce web pages that included text, graphics and pointer to other web pages
(Hyperlinks).
 HTML is not a programming language, but it is an application of ISO Standard 8879,
SGML (Standard Generalized Markup Language), but Specialized to hypertext and adapted to
the Web. The idea behind Hypertext one point to another point. We can navigate through the
information based on out interest and preference. A markup language is simply a series of items
enclosed within the elements should be [Link] are underlined or emphasized
works that load to other documents or some portions of the same document.

HTML can be used to display any type of document on the host computer, which can be
geographically at a different location. It is a versatile language and can be used on any platform
or desktop

HTML provides tags (special codes) to make the document look attractive.

HTML provides are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can
enhance the presentation of the document. Anything that is not a tag is part of the document
itself.

Basic Html Tags:

<!-- --> Specific Comments.

<A>………</A> Creates Hypertext links.

<B>………</B> Creates hypertext links.

<Big>……..</Big> Formats text in large-font

<Body>……. </Body> contains all tags and text in the Html-document

<Center>……</Center> Creates Text

<DD>………..</DD> Definition of a term.

<TABLE>…… </TABLE> creates a table

<Td>………..</Td> indicates table data in a table.

 <Tr>………..</Tr> designates a table row

<Th>………. </Th> creates a heading in a table.

ADVANTAGE
• A HTML document is small and hence easy to send over the net. It is small
because it does not include formatted information.

• HTML is platform independent

• HTML tags are not case-sensitive.

5.5 JAVA SCRIPT

The Java Script Language

JavaScript is a compact, object-based scripting language for developing client and server internet
applications. Netscape Navigator 2.0 interprets JavaScript statements embedded directly in an
HTML page. And Livewire enables you to create server-based applications similar to common
gateway interface (CGI) programs.

In a client application for Navigator, JavaScript statements embedded in an HTML Page can
recognize and respond to user events such as mouse clicks form input, and page navigation.
For example, you can write a JavaScript function to verify that users enter valid information
into a form requesting a telephone number or zip code. Without any network transmission, an
Html page with embedded Java Script can interpret the entered text and alert the user with a
message dialog if the input is invalid or you can use JavaScript to perform an action (such as
play an audio file, execute an applet, or communicate with a plug-in) in response to the user
opening or exiting a page.
 CHAPTER-6

SYSTEM DESIGN
6.1 INTRODUCTION

The HR Management Web Application is a comprehensive and scalable solution designed to

address modern organizational challenges by integrating advanced technologies, secure data
handling mechanisms, and efficient workflows. This application operates through five core
modules: Admin, Client, Employee, Secure Management, and Management. Each module plays
a critical role in ensuring seamless collaboration among stakeholders and enhancing overall
productivity. The Admin Module serves as the system's backbone, managing user data,
dynamically assigning tasks using an algorithm that considers employee expertise and workload,
and acting as the central point for access requests and project review. The Client Module allows
clients to make project modifications, including algorithm enhancements, which are reviewed
and validated by the admin, fostering direct collaboration. The Employee Module facilitates
project updates, access requests, and final deliverables, ensuring alignment with organizational
[Link] application’s Secure Management Module employs SHA-256 blockchain encryption
to provide a robust key management system for access control. This ensures data integrity,
immutability, and security while maintaining a detailed, tamper-proof audit trail of all system
interactions. The Management Module oversees project updates, reviews employee
enhancements, and provides feedback, ensuring alignment with client expectations. An
integrated task allocation algorithm optimizes resource utilization by considering employee
skills, workload, and project deadlines. Additionally, real-time collaboration features and
comprehensive reporting capabilities enhance transparency and informed [Link]
application’s reliance on blockchain technology ensures a secure and transparent record of all
modifications, fostering trust among stakeholders. Its modular design supports scalability and
adaptability, making it suitable for businesses of all sizes. By combining advanced algorithms,
secure data management, and dynamic workflows, this application addresses diverse
organizational needs while maintaining robust security and operational efficiency.

MODULES:

• Admin
 • Management

• Task mangement

• Employee

• client

1. Admin Module

The Admin Module serves as the central control hub, responsible for managing user access,
initiating workflows, and ensuring secure data handling. Administrators upload and maintain
user data across all modules, validate client modifications, and assign approved changes to
employees based on workload and expertise. They also manage employee access requests for
secure project components, forwarding them to the Secure Management Module for verification.
Additionally, the admin oversees project progress, ensuring compliance with security protocols
and efficiency standards. To maintain transparency and accountability, the module generates
detailed reports on project updates, workflow performance, and stakeholder collaboration.

2. Client Module

The Client Module allows clients to actively participate in project management while ensuring
administrative oversight. Clients can submit project modifications, including algorithm updates
and technical enhancements, which are then forwarded to the Admin Module for validation.
They can track the status of approvals and implementation progress while also accessing reports
to ensure project alignment with business objectives. The module fosters seamless collaboration
with employees and administrators, enabling clients to refine project goals and maintain
visibility into project development.

3. Secure Management Module

The Secure Management Module is the core of the system’s security framework, ensuring strict
access control through a blockchain-powered key management system. It verifies employee
access requests forwarded by the Admin Module and employs SHA-256 blockchain encryption
to secure data, transactions, and access logs. This module ensures data integrity, immutability,
and traceability within the project workflow, granting or denying access to sensitive project
components based on authorization levels. Additionally, it maintains a tamper-proof record of all
access permissions and security-related actions, reinforcing system transparency and trust.

4. Management Module

The Management Module plays a supervisory role, overseeing employee contributions and
project execution to ensure quality and efficiency. Managers review project updates, provide
feedback to employees, and verify that modifications align with company standards. They
monitor project milestones and task completion, collaborating with the Secure Management
Module to validate access permissions when needed. Additionally, the module evaluates reports
and performance metrics, enabling informed decision-making and optimized resource allocation
for project success.

5. Employee Module

The Employee Module facilitates seamless task execution, project enhancements, and secure
data requests. Employees receive dynamically assigned tasks based on expertise and workload,
allowing for efficient resource utilization. They update project requirements, implement
approved enhancements, and request secure access to specific project components via the Admin
Module. Employees incorporate feedback from the Management Module to refine project
deliverables, ensuring consistency and quality. Furthermore, they maintain communication with
clients, admins, and managers, ultimately submitting finalized project updates for review and
approval.
Database Screen Short:
6.3 System Architecture:
6.4 E – R DIAGRAMS

• The relation upon the system is structured through a conceptual ER-Diagram, which not
only specifics the existing entities, but also the standard relations through which the
system exists and the cardinalities that are necessary for the system state to continue.

• The Entity Relationship Diagram (ERD) depicts the relationship between the data objects.
The ERD is the notation that is used to conduct, the date modeling activity the attributes
of each data object noted, is the ERD can be described resign a data object description.

• The set of primary components that are identified by the ERD are

• Data object

• Relationships

• Attributes

• Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

6.5 FLOW DIAGRAMS

A data flow diagram is a graphical tool used to describe and analyze the movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output through processing, may be
described logically and independently of physical components associated with the system. These
are known as the logical data flow diagrams. The physical data flow diagrams show the actual
implements and movement of data between people, departments and workstations. A full
description of a system actually consists of a set of data flow diagrams. Using two familiar
notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component
in a DFD is labeled with a descriptive name. The process is further identified with a number that
will be used for identification purpose. The development of DFD’S is done on several levels.
Each process in lower level diagrams can be broken down into a more detailed DFD in the next
level. The lop-level diagram is often called context diagram. It consist a single process bit,
which plays a vital role in studying the current system. The process in the context level diagram
is exploded into another process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at one level of
detail is exploded into greater detail at the next level. This is done until further explosion is
necessary and an adequate amount of detail is described for analysts to understand the process.

Larry Constantine first developed the DFD as a way of expressing system requirements in a
graphical form, this lead to the modular design.

A DFD is also known as a “bubble Chart” has the purpose of clarifying system requirements and
identifying major transformations that will become programmed in system design. So it is the
starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles
joined by data flows in the system.
6.6 DFD SYMBOLS

In the DFD, there are four symbols

• A square defines a source (originating) or destination of system data

• An arrow identifies data flow. It is the pipeline through which the information flows
• A circle or a bubble represents a process that transforms the incoming data flow into
outgoing data flows.
• An open rectangle is a data store, data at rest or a temporary repository of data

A process that transforms the data flow

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:

Several rules of thumb are used in drawing DFD’S:

• Process should be named and numbered for an easy reference. Each name should be
representative of the process.
• The direction of flow is from top to bottom and from left to right. Data traditionally flow
from source to the destination although they may flow back to the source. One way to
 indicate this is to draw the long flow line back to a source. An alternative way is to repeat
the source symbol as a destination. Since it is used more than once in the DFD it is marked
with a short diagonal.
• When a process is exploded into lower level details, they are numbered.
• The names of data stores and destinations are written in capital letters. Process and dataflow
names have the first letter of each work capitalized
A DFD typically shows the minimum contents of data store. Each data store should
contain all the data elements that flow in and out.

Questionnaires should contain all the data elements that flow in and out. Missing
interfaces redundancies and like is then accounted for often through interviews.

SAILENT FEATURES OF DFD’S

• The DFD shows the flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
• The DFD does not indicate the time factor involved in any process, whether the dataflow take
place daily, weekly, monthly or yearly.
• The sequence of events is not brought out on the DFD.
TYPES OF DATA FLOW DIAGRAMS

• Current Physical

• Current Logical

• New Logical

• New Physical

CURRENT PHYSICAL

In Current Physical DFD process label includes the name of the people or their positions or the
names of computer systems that might provide some of the overall system-processing label
includes an identification of the technology used to process the data. Similarly, data flows and
data stores are often labelled with the names of the actual physical media on which data are
stored such as file folders, computer files, business forms or computer tapes.

CURRENT LOGICAL:

The physical aspects in the system are removed as much as possible so that the current system is
reduced to its essence to the data and the processes that transform them regardless of actual
physical form.

NEW LOGICAL:

This is exactly like a current logical model if the user were completely happy with the user were
completely happy with the functionality of the current system, but had problems with how it was
implemented typically through the new logical model will differ from the current logical model
while having additional functions, absolute function removal and inefficient flows recognized.

NEW PHYSICAL:

The new physical represents only the physical implementation of the new system.

RULES GOVERNING THE DFD’S

PROCESS

• No process can have only outputs.

• No process can have only inputs. If an object has only inputs than it must be a sink.
• A process has a verb phrase label.

DATA STORE

• Data cannot move directly from one data store to another data store, a process must move
data.
• Data cannot move directly from an outside source to a data store, a process, which receives,
must move data from the source and place the data into the data store
• A data store has a noun phrase label.
SOURCE OR SINK

The origin and /or destination of data

• Data cannot move direly from a source to sink it must be moved from a process
• A source and /or sink have a noun phrase land

DATA FLOW

• A Data Flow has only one direction of flow between symbols. It may flow in both directions
between a process and a data store to show a read before an update. The latter is usually
indicated, however by two separate arrows since these happen at different type.
• A join in DFD means that exactly the same data comes from any of two or more different
processes data store or sink to a common location.
• A data flow cannot go directly back to the same process it leads. There must be at least one
other process that handles the data flow produce some other data flow returns the original
data in the beginning process.
• A Data flow to a data store means update (delete or change).
• A data Flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can appear on a single
arrow as long as all of the flows on the same arrow move together as one package.
DATA FLOW DIAGRAM
6.8 USE CASE DIAGRAM
CHAPTER-7
OUTPUT SCREENS
CHAPTER-8
 CODINGS
HOME PAGE: [Link]
<!DOCTYPE html>
<html>
<head>
<title></title>
<!-- for-mobile-apps -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta property="og:title" content="Vide" />
<meta name="keywords" content="Eduma Responsive web template, Bootstrap Web Templates,
Flat Web Templates, Android Compatible web template,
Smartphone Compatible web template, free webdesigns for Nokia, Samsung, LG, SonyEricsson,
Motorola web design" />
<script type="application/x-javascript"> addEventListener("load", function()
{ setTimeout(hideURLbar, 0); }, false);
function hideURLbar(){ [Link](0,1); } </script>
<!-- //for-mobile-apps -->
<link href="index_css/css/[Link]" rel='stylesheet' type='text/css' />
<!-- Custom Theme files -->
<link href="index_css/css/[Link]" rel="stylesheet" type="text/css" media="all"/>
<link href="index_css/css/[Link]" rel='stylesheet' type='text/css' />
<link href="index_css/css/[Link]" rel='stylesheet' type='text/css' />
<!-- js -->
<script src="index_css/js/[Link]"></script>
<!-- //js -->
<!-- dropdown -->
<script src="index_css/js/[Link]"></script>
<!-- //dropdown -->
<!--webfont-->
<link href='//[Link]/css?family=Nunito:400,300,700' rel='stylesheet'
type='text/css'>
<link href='//[Link]/css?
family=Open+Sans:400,300,300italic,400italic,600,600italic,700,700italic,800,800italic'
rel='stylesheet' type='text/css'>
<!-- start-smoth-scrolling -->
<script type="text/javascript" src="index_css/js/[Link]"></script>
<script type="text/javascript" src="index_css/js/[Link]"></script>
<script type="text/javascript">
jQuery(document).ready(function($) {
$(".scroll").click(function(event){
[Link]();
$('html,body').animate({scrollTop:$([Link]).offset().top},1000);
});
});
</script>
<!-- start-smoth-scrolling -->
<!-- accordian -->
<link rel="stylesheet" href="index_css/css/[Link]">
<script src="index_css/js/[Link]"></script>
<script>
$(function() {
$( "#accordion" ).accordion();
});
</script>
<!-- //accordian -->
<!-- tabs -->
<script src="index_css/js/[Link]" type="text/javascript"></script>
<script type="text/javascript">
$(document).ready(function () {
$('#horizontalTab').easyResponsiveTabs({
type: 'default', //Types: default, vertical, accordion
width: 'auto', //auto or any width like 600px
fit: true // 100% fit in a container
});
});
</script>
<!-- //tabs -->
<!--animate-->
<link href="index_css/css/[Link]" rel="stylesheet" type="text/css" media="all">
<script src="index_css/js/[Link]"></script>
<script>
new WOW().init();
</script>
<!--//end-animate-->

</head>
<body>

<div data-vide-bg="index_css/video/training">
<div class="center-container">
<div class="ban-shade">
 <div class="header-nav">
<div class="logo wow fadeInUp animated" data-wow-
delay=".5s">
<h1>
<a class="link link--kumya"
href="[Link]"><i></i><span data-letters="Organization MERCH">Organization
MERCH</span></a>
</h1>
</div>
<div class="top-nav wow fadeInUp animated" data-wow-
delay=".5s">
<label class="mobile_menu" for="mobile_menu">
<span>Menu</span>
</label>
<input id="mobile_menu" type="checkbox">
<ul class="nav">
<li><a class="active"
href="[Link]">HOME</a></li>
<li><a href="Client_Log.jsp?
var=client">CLIENT</a></li>
<li><a href="ad_log.jsp?var=admin">ADMIN</a>

</li>
<li><a href="[Link]?
var=employee">Employee</a></li>
<li><a href="[Link]?
var=secure">Secure Management</a>

</li>
<li><a href="[Link]?
var=taskmanager">Management</a></li>
 </ul>
</div>
<div class="clearfix"></div>

</div>
<div class="socials">
<script type="text/javascript"
src="//[Link]/js/300/addthis_widget.js#pubid=ra-4dd797b06396480a"></script>
</div>
<div class="box_1-top">
<div class="banner-info wow fadeInLeft animated" data-wow-
delay=".5s">
<h3>Decent Education, Successful career</h3>
<h2>Pursue your goals with our expert faculty</h2>

<a class="scroll" href="#faculty" class="hvr-shutter-in-

vertical button">Meet our faculty</a>
</div>
</div>
</div>
</div>
</div>

<script>[Link] || [Link]('<script src="index_css/js/vendor/jquery-

[Link]"><\/script>')</script>
<script src="index_css/js/[Link]"></script>
<!-- smooth scrolling -->
<script type="text/javascript">
$(document).ready(function() {
/*
var defaults = {
containerID: 'toTop', // fading element id
containerHoverID: 'toTopHover', // fading element hover id
scrollSpeed: 1200,
easingType: 'linear'
};
*/
$().UItoTop({ easingType: 'easeOutQuart' });
});
</script>
<a href="#" id="toTop" style="display: block;"> <span id="toTopHover" style="opacity:
1;"> </span></a>
<!-- //smooth scrolling -->
<!-- for bootstrap working -->
<script src="index_css/js/[Link]"></script>
<!-- //for bootstrap working -->
</body>
</html>
SYSTEM TESTING AND IMPLEMENTATION

9.1. INTRODUCTION
 Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive.

9.2. STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering defines
the role of software and leads to software requirement analysis where the information domain, functions,
behavior, performance, constraints and validation criteria for software are established. Moving inward
along the spiral, we come to design and finally to coding. To develop computer software we spiral in
along streamlines that decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins
at the vertex of the spiral and concentrates on each unit of the software as implemented in source code.
Testing progress is done by moving outward along the spiral to integration testing, where the focus is on
the design and the construction of the software architecture. Talking another turn on outward on the spiral
we encounter validation testing where requirements established as part of software requirements analysis
are validated against the software that has been constructed. Finally, we arrive at system testing, where
the software and other system elements are tested as a whole.

9.3. TESTING PROCEDURES

Unit testing focuses verification effort on the smallest unit of software design, the module. The
unit testing we have is white box oriented and some modules the steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that

• All independent paths have been exercised at least once

• All logical decisions have been exercised on their true and false sides
• All loops are executed at their boundaries and within their operational bounds
• All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .We have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.

2. BLACK BOX TESTING

The established technique of flow graph with Cyclamate complexity was used to derive test
cases for all the functions. The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graphs.

Determine the Cyclamate complexity of the resultant flow graph, using formula:

V (G) =E-N+2 or

V (G) =P+1 or

V (G) =Number of Regions

Where V (G) is Cyclomatic complexity,

E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

3. MODULE TESTING

In this part of the testing each of the conditions were tested to both true and false aspects. And all
the resulting paths were tested. So that each path that may be generated on particular condition is
traced to uncover any possible errors.

4. SUB SYSTEM TESTING

This type of testing selects the path of the program, according to the location of the definition
and use of variables. This kind of testing was used only when some local variable were declared.
The definition-use chain method was used in this type of testing. These were particularly useful
in nested statements.

5. UNIT TESTING

In this type of testing all the loops are tested to all the limits possible. The following exercise
was adopted for all loops:

• All the loops were tested at their limits, just above them and just below them.
• All the loops were skipped at least once.
• For nested loop test the innermost loop first and then work outwards.
• For concatenated loops the values of dependent loops were set with the help of a connected
loop.
CHAPTER-10
 SYSTEM SECURITY

10.1 INTRODUCTION
Security system can be divided into four related issues: The protection of computer based
resources that includes hardware, software, data, procedures and people against unauthorized use
or natural

Disaster is known as System Security.

• Security
• Integrity
 • Privacy
• Confidentiality
SYSTEM SECURITY refers to the technical innovations and procedures applied to the
hardware and operation systems to protect against deliberate or accidental damage from a
defined threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.

SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate
physical security and safety against external threats such as eavesdropping and wiretapping.

PRIVACY defines the rights of the user or organizations to determine what information they are
willing to share with or accept from others and how the organization can be protected against
unwelcome, unfair or excessive dissemination of information about it.

CONFIDENTIALITY is a special status given to sensitive information in a database to

minimize the possible invasion of privacy. It is an attribute of information that characterizes its
need for protection.

10.2 SECURITY IN SOFTWARE

System security refers to various validations on data in the form of checks and controls to avoid
the system from failing. It is always important to ensure that only valid data is entered and only
valid operations are performed on the system. The system employs two types of checks and
controls:

CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that only valid data is entered.
Client side validation saves server time and load to handle invalid data. Some checks are
imposed:
 • JavaScript in used to ensure those required fields are filled with suitable data only.
Maximum lengths of the fields of the forms are appropriately defined.
• Forms cannot be submitted without filling up the mandatory data so that manual mistakes
of submitting empty fields that are mandatory can be sorted out at the client side to save
the server time and load.
• Tab-indexes are set according to the need and taking into account the ease of use while
working with the system.

SERVER SIDE VALIDATION

Some checks cannot be applied on the client side. Server side checks are necessary to save the
system from failing and intimating the user that some invalid operation has been performed or
the performed operation is restricted. Some of the server side checks imposed is:
• A server side constraint has been imposed to check for the validity of primary key and
foreign key. A primary key value cannot be duplicated. Any attempt to duplicate the primary
value results in a message intimating the user about those values through the forms using
foreign key can be updated only of the existing foreign key values.
• The user is intimated through appropriate messages about the successful operations or
exceptions occurring at server side.
• Various Access Control Mechanisms have been built so that one user may not agitate upon
another. Access permissions to various types of users are controlled according to the
organizational structure. Only permitted users can log on to the system and can have access
according to their category. User- name, passwords and permissions are controlled the server
side.
• Using server side validation, constraints on several restricted operations are imposed.
CHAPTER-11

CONCLUSION
CONCLUSION:

The proposed HR Management Web Application offers a modern, efficient, and secure solution
to streamline project management and collaboration across organizations. By integrating
advanced algorithms for task allocation, blockchain technology for secure data management, and
a modular, scalable design, it enhances operational efficiency, reduces delays, and improves
transparency. This system ensures that organizations can manage projects with optimal resource
allocation, robust data security, and seamless collaboration, providing a reliable platform for
modern HR management needs.