INDEX

1. ABSTRACT
2. SYSTEM REQUIREMENT SPECIFICATION
2.1 Introduction
2.1.1 Purpose of the system
2.1.2 Scope of the system
2.1.3 Objectives

2.2 Existing system

2.3 Proposed system
2.3.1 Overview
2.3.2 Non-functional Requirements

2.4 Feasibility study

3. REQUIRMENT ANALYSIS DOCUMENT(RAD)
3.1 System model
3.1.1 Identifying Actors
3.1.2 Identifying Scenarios

3.2 Use Case Model

3.2.1 Identifying Use Case

3.3 Object Model

3.3.1 Class Diagram

3.4 Dynamic Model

3.4.1 Sequence Diagrams
3.4.2 Collaboration Diagrams
3.4.3 State Chart Diagrams
3.4.4 Activity Diagrams
[Link] DESIGN DOCUMENT
4.1 Sub System Decomposition
4.2 Design Goals
4.3 Data Dictionary

[Link] ENVIRONMENT
5.1 Hardware Configuration
5.26. PROPOSED SCREENS

[Link] SCREENS
7. TESTING
7.1 Testing Strategy
7.3 Testing Case Specification & Execution
7.3 Testing Case login
7.4 Test Case Report

[Link]
9. FUTURE ENHANCEMENT OF THE PROJECT
10. BIBLOGRAPHY
ABSTRACT
 ABSTRACT
The Payroll Processing System (PPS) is a comprehensive and integrated software
solution designed to streamline and automate the intricate tasks associated with managing
employee compensation within an organization. PPS offers a robust platform that facilitates
the efficient calculation, distribution, and record-keeping of employee salaries, taxes,
benefits, and deductions.

PS ensures precision in computing payroll by automating complex calculations, adhering to

tax regulations, and accounting for variable compensation components such as overtime and
bonuses. The system remains up-to-date with evolving tax laws, labour regulations, and
statutory requirements, ensuring adherence to legal obligations and reducing the risk of
compliance errors. PPS significantly reduces the time and effort required to process payroll,
minimizing manual intervention, and thereby allowing HR personnel to focus on more
strategic tasks. Robust data encryption and access controls safeguard sensitive employee
information, ensuring confidentiality and integrity throughout the payroll process.

Error Reduction: Minimize payroll errors and discrepancies by automating calculations and
adhering to standardized processes.

BENEFITS:

➤ Expedite payroll processing, reducing the time spent on manual computations and
administrative tasks.

➤ Streamline payroll operations, leading to cost savings through reduced labour and
operational overheads.

➤ Enhanced Employee Satisfaction: Ensure timely and accurate compensation, fostering

employee trust and satisfaction within the organization.

➤In conclusion, the Payroll Processing System stands as a pivotal tool for organizations

offering accuracy, compliance, efficiency, and security in managing the intricate landscape of
employee compensation.
➤ This abstract summarizes the essential aspects of a payroll processing system, emphasiz
➤Health Insurance: Details about the health insurance plans offered by the company,
including coverage options, premiums, deductibles, co-payments, and the extent of coverage
for medical services, prescriptions, and other healthcare needs.

➤ Retirement Plans: Information about retirement savings plans like 401(k), pension
schemes, or other investment opportunities provided by the employer, including contribution
matching, vesting schedules, and eligibility criteria

➤ Bonuses and Incentives: Details about bonuses, performance-based incentives,

profitsharing, or other monetary rewards that employees might receive based on their
individual performance or the company’s performance.

➤Flexible Spending Accounts (FSAs) or Health Savings Accounts (HSAs): Information

about accounts that allow employees to set aside pre-tax funds for healthcare expenses or
other eligible expenses.

➤ Other Benefits: This section may include additional benefits such as tuition
reimbursement, wellness programs, commuter benefits, life insurance, disability coverage,

➤The payroll abstract for benefits serves as a concise summary for employees to understand
and appreciate the value of the benefits package offered by the company. It is essential for
employees to be informed about the benefits available to them, including the terms,
conditions, and any changes to the benefits package over time. This information helps in
attracting and retaining talent while contributing to employee satisfaction and well-being

Time-saving process:

t takes a very long time to process payroll. If you invest in a payroll service provider, the staff
members will be able to concentrate on other crucial areas of the organisation, such as
creating financial plans that boost the firm's competitive edge by freeing up the payroll
department from these time-consuming payroll duties.

Reduces errors:

Helps employees improve their job performance, reduce errors, and increase productivity.
SYSTEM REQUIREMENT SPECIFICATION
 [Link] Requirements Specification (SRS):
System requirement specification is a comprehensive document that outlines the
functional and non-functional requirements of a software system or a product. It serves as a
blueprint for the development team and stakeholders to understand what the system should
accomplish. Here's an outline of what an SRS typically includes.

2.1 Introduction:

The introduction section of a System Requirements Specification (SRS) serves as a

starting point for the document, providing an overview of its purpose, scope, and intended
audience. Here's an example of how an introduction for an SRS might be structured.

2.1.1 Purpose of the system:

The creation of a System Requirements Specification (SRS) document is a critical

step that creates a clear understanding and alignment on what the software should achieve.
This document serves as a comprehensive guide, detailing the software's intended function,
performance, and interactions.

2.1.2 Scope of the system:

The scope of this SRS encompasses the definition of [System/Product/Project],

detailing its intended functionalities, performance expectations, constraints, and interfaces
with external entities. It delineates the boundaries within which the system will operate and
defines the features and capabilities that will be included in its development.

2.1.3 Objectives:

The System Requirements Specification (SRS) plays a crucial role in the software or
product development lifecycle, serving several key objectives.

[Link] Stakeholder Expectations:

An SRS aims to clearly and comprehensively document the requirements of the

system, ensuring that all stakeholders have a shared understanding of what the system is
expected to accomplish.
2. Define Functionalities:

It outlines the functional requirements of the system, specifying what the system should
do from a user's perspective. This includes specific features, operations, and interactions the
system should support.

[Link] Non-Functional Attributes:

Beyond functionalities, the SRS defines non-functional requirements such as performance,

security, usability, reliability, scalability, and maintainability. These aspects contribute to the
overall quality and effectiveness of the system

4. Serve as a Blueprint for Development:

The document acts as a blueprint or guideline for the development team, providing a
clear roadmap on how the system should be designed, developed, and implemented.

5. Facilitate Communication:

It serves as a communication bridge between stakeholders, developers, designers, and

testers, ensuring everyone is on the same page regarding the system's goals, functionalities,
and constraints.

2.2 Existing system:

1. Functional Limitations

 [List specific functional limitations or shortcomings of the existing system

 [Describe any inefficiencies or lack of functionalities affecting operation

2. Technical Constraints

 [Highlight technical limitations, such as outdated technology, hardware, or software]

 [Note any compatibility issues or integration challenges]

1. User Experience Issues

 [Describe any user interface or usability issues experienced by stakeholders

 [Note any difficulties in system navigation or user interaction]
2.3 Proposed system:

A Payroll Management System is crucial for businesses to efficiently handle employee

salaries, deductions, taxes, and other financial aspects related to employee compensation.
Here's an outline for a proposed Payroll Management System. Of course! To help you
develop a proposed system, I'll need more specific information about what kind of system
you're referring to.

Is it a software system, a management system, a technological system, or something else?

Additionally, details about the objectives, functionalities, target users, and any specific
requirements or features you want in this proposed system would be beneficial. Please
provide more details so that I can assist you better in creating a proposed system

2.3.1 Advantages of proposed system:

The proposed Payroll Management System offers several advantages for b

[Link] and Time Savings:

automating payroll processes can reduce manual effort, streamline calculations, and minimize
errors, which can save time for HR and payroll administrators. Here are some other benefits
of payroll automation:

[Link] in Payroll Processing:

Automation reduces the chances of human error in calculating salaries, taxes, and
deductions, ensuring accurate payments to employees. This accuracy helps in maintaining
trust and satisfaction among employees.

Overview:

Payroll software is an on-premises or cloud-based solution that manages, maintains,

and automates payments to employees. Robust, integrated, and properly configured payroll
software can help organizations of all sizes maintain compliance with tax laws and other
financial regulations, and reduce costs.
2.3.2 Functional Requirements:

These are the requirements that the end user specifically demands as basic facilities that the
system should offer. All these functionalities need to be necessarily incorporated into the
system as a part of the contract.

These are represented or stated in the form of input to be given to the system, the operation
performed and the output expected. They are the requirements stated by the user which one
can see directly in the final product, unlike the non-functional requirements.

Non-functional requirements:

These are the quality constraints that the system must satisfy according to the project
contract. The priority or extent to which these factors are implemented varies from one
project to another. They are also called non-behavioral requirements. They deal with issues
like:

 Portability
 Security
 Maintainability
 Reliability
 Scalability
 Performance
 Reusability
 Flexibility

1. Usability:

➤ Provide an intuitive and user-friendly interface for all types of users (administrators, HR
staff, employees).

➤ Ensure easy navigation and minimal training required for users to operate the system

[Link]:

➤ Aim for high availability (minimal downtime) to ensure access to payroll data when
needed.

➤ Implement measures to handle system failures or ensure quick recovery in case of

disruptions.
➤ Ensure data accuracy and integrity throughout the system, preventing errors or data loss
during payroll processing.

[Link]:

➤ Maintain acceptable response times for system actions (calculations, generating reports) to
ensure smooth user experience.

[Link]:

➤ Design the system to handle increased data volumes or user loads as the organization
grows without significant performance degradation.

5. Maintainability:

➤ Design the system with modularity and proper documentation to facilitate easy updates
and maintenance without disrupting ongoing operations.

➤ Ensure clean and well-documented code to simplify troubleshooting, bug fixing, and future
enhancements.

6. Compatibility:

➤ Ensure compatibility and interoperability with other software systems and databases
commonly used within the organization.

7. Legal Requirements:

➤ Meet legal requirements related to payroll processing, tax calculations, and data retention
in different jurisdictions where the business operates.

2.4 Feasibility Study:

Feasibility Study in is a study to evaluate feasibility of proposed project or system.

Feasibility study is one of stage among important four stages of system feasible. The
feasibility study mainly concentrates on below five mentioned areas. Among these Economic
Feasibility Study is most important part of the feasibility analysis and Legal Feasibility Study
is less considered feasibility analysis.

1. Technical Feasibility:

In Technical Feasibility current resources both hardware software along with required
technology are analysed/assessed to develop project. This technical feasibility study gives
report whether there exists correct required resources and technologies which will be used for
project development. Along with this, feasibility study also analyses technical skills and
capabilities of technical team, existing technology can be used or not, maintenance and
upgradation is easy or not for chosen technology etc.

2. Operational Feasibility:

In Operational Feasibility degree of providing service to requirements is analysed

along with how much easy product will be to operate and maintenance after deployment.
Along with other operational scopes are determining usability of product Determining to
suggested solution by software development team is acceptable or not etc.

3. Economic Feasibility:

In Economic Feasibility study cost and benefit of the project is analysed. Means under
this feasibility study a detail analysis is carried out what will be cost of the project for
development which includes all required cost for final development like hardware and
software resource required, design and development cost and operational cost and so on.
After that it is analysed whether project will be beneficial in terms of finance for organization
or not.

4. Legal Feasibility:

In Legal Feasibility study project is analysed in legality point of view. This includes
analysing barriers of legal implementation of project, data protection acts or social media
laws, project certificate, license, copyright etc. Over all it can be said that Legal Feasibility
Study is study to know if proposed project legal and ethical requirements.

5. Schedule Feasibility:
 In Schedule Feasibility Study mainly timelines/deadlines is to be analysed for
proposed project which includes how many times teams will take to complete final project
which has a great impact on the organization as purpose of project may fail if it can't

6. Legal and Regulatory Compliance-

Ensure that the project complies with all relevant laws, regulations, and industry
standards. Identify potential legal issues or constraints that may affect the project.

7. Risk Analysis-

Identify and assess potential risks and uncertainties associated with the project.
Develop strategies to mitigate these risks and ensure project success.

8. Resource Assessment-

Evaluate the human, technological, and other resources required for the project's
implementation. Determine if these resources are available or can be acquired within the
project timeline

9. Recommendations and Conclusion-

Based on the analysis conducted, provide recommendations on whether to proceed

with the project. Summarize the key findings and conclusions of the feasibility study. Ensure
that the project complies with all relevant laws, regulations, and industry standards. Identify
potential legal issues or constraints that may affect the Identify and assess potential risks and
uncertainties associated with the project. Develop strategies to mitigate these risks and ensure
project success. Evaluate the human, technological, and other resources required for the
project's implementation. Determine if these resources are available or can be acquired within
the project timeline. Based on the analysis conducted, provide recommendations on whether
to proceed with the project. Summarize the key findings and conclusions of the feasibility
study.

Remember, the feasibility study serves as a foundation for decision-making. It helps

stakeholders understand the potential challenges, opportunities, and outcomes associated with
the project, allowing them to make informed decisions about its feasibility and
implementation.
REQUIREMENT ANALYSIS DOCUMENT
 3. REQUIREMENT ANALYSIS DOCUMENT

3.1 SYSTEM MODEL:

3.1.1 Identifying Actors:

By identifying actors early in the requirement analysis phase, you gain a clearer
understandingof who will be using the system, their needs, and how they interact with it. This
information iscrucial in designing a system that meets the requirements and expectations of
its users.

➤Stakeholder Analysis

➤ User Interviews and Surveys

➤ Use Case Analysis

➤ Role Identification

➤ External Systems or Interfaces

➤ Persona Creation

➤ Feedback and Validation

➤ Documentation

Types of System Models:

1. Functional Model: Focuses on the functions or operations performed by the system. It

outlines what the system does without detailing how it accomplishes these functions.

2. Structural Model: Describes the structure of the system, including its components, their
relationships, and how they are organized. This could be represented through diagrams like
UML (Unified Modelling Language) class diagrams or entity relationship diagrams.

3. Behavioural Model: Illustrates the behaviour of the system under various conditions. It
shows how the system responds to inputs and stimuli, detailing processes, states, events, and
transitions. State diagrams, sequence diagrams, and activity diagrams in UML are commonly
used for this purpose.
4. Data Model: Focuses on the representation of data within the system, including data
structures, entities, attributes, and their relationships. Entity-relationship diagrams and data
flow diagrams are examples of data models.

5. Process Model: Details the processes or workflows within the system. It shows the
sequence of activities, decision points, and their interactions Flowcharts and BPMN
(Business Process Model and Notation) diagrams are often used for process modelling.

Components of a System Model:

Components/Elements: Represent the parts of the system, such as modules, subsystems, or

entities.

1. Relationships: Show how the components interact or relate to each other.

2. Attributes/Properties: Describe the characteristics or properties of system components.

3. Behaviours/Processes: Explain the functions or operations performed by the system

components.

Importance of System Models:

➤ Understanding Complexity: Helps in breaking down complex systems into manageable

components for analysis and design.

➤ Communication: Provides a common language and visual representation for stakeholders

to discuss and understand the system.

➤ Design and Analysis: Aids in designing, analysing, and validating the system's architecture
and functionalities.

➤ Documentation: Serves as documentation that can be referenced throughout the system

development lifecycle.

➤ Creating a system model involves choosing the appropriate modelling techniques and tools
based on the system's nature and requirements. It's crucial to continually refine and update the
system model to accurately reflect the evolving system architecture and functionalities

➤ The topic of a system model encompasses various aspects related to conceptualizing.

designing, analysing, and understanding complex systems.

3.1.1 Identifying Actors

 Sure, I can help identify actors! Please provide me with the names of the actors you're
curious about or the context in which you want to identify them (such as movies, TV shows,
or any specific details).

Table of Contents

1. Introduction

➤Background of the Project

➤Purpose of the Requirements Analysis Document

➤Scope and Objectives

2. Stakeholder Identification

➤List of Stakeholders

➤ Roles and Responsibilities of Each Stakeholder

➤ Stakeholder Requirements

3. Business Requirements

➤ Overview of Business Goals and Objectives

➤ Business Process Analysis

➤ Business Rules and Constraints.

4. Functional Requirements

➤ Use Cases or User Stories

➤ Functional Specifications

➤ System Interfaces

➤ Data Requirements

➤ Non-functional Requirements (Performance, Security, etc.)

5. User Requirements

➤ User Profiles and Personas

➤ User Experience (UX) Requirements

➤ User Interface (UI) Design Guidelines

6. System Requirements

➤Hardware Requirements

➤Software Requirements

➤Network Requirements

➤ Security Requirements

7. Assumptions and Constraints

➤ Assumptions Made During Requirement Gathering

➤ Constraints that May Impact the Project

8. Requirements Traceability Matrix

➤Link requirements to their sources (e.g., stakeholder needs, business goals)

➤Show how requirements align with project objectives

9. Glossary

➤ Definitions of Terms and Acronyms Used

10. Appendix

➤ Supporting Documents (if any)

➤ Additional Information or Diagrams

11. Revision History

➤ Record of Changes Made to the Document

Notes for Creating a Strong Requirements Analysis Document:

➤Be Clear and Specifie: Use precise language and avoid ambiguity in requirements.

➤ Use Visual Aids: Diagrams, flowcharts, and tables can make complex information easier
to understand.

➤ Involve Stakeholders: Ensure that stakeholders review and approve the document to
validate the requirements.
➤ Keep It Updated: As the project progresses, update the document to reflect any change in
requirements.

Tailor this outline according to the specific needs and complexity of your project. Regularly
revisiting and updating the requirements analysis document throughout the project lifecycle
helps ensure that everyone involved is on the same page regarding project expectations and
day

system model is a visual or conceptual representation that describes the components,

interactions, behaviours, and relationships within a system. It provides a structured way to
understand and analyse how different parts of a system work together to achieve specific
objectives. Here's an overview of different types of system models.

Creating a system model involves choosing the appropriate modelling techniques and tools
based on the system's nature and requirements. It's crucial to continually refine and update the
system model to accurately reflect the evolving system architecture and functionalities.

The topic of a system model encompasses various aspects related to conceptualizing.

designing, analysing, and understanding complex systems. It involves creating
representations or abstractions that help comprehend the workings, components, interactions,
and behaviours within a system. Here are key aspects and considerations within the topic of
system modelling.

ADMINISTRATOR:

In the context of requirement analysis or system design, an Administrator is a role or actor

responsible for managing and overseeing the functioning, maintenance, and configurations of
a system or application. Administrators have elevated privileges and are typically tasked with
performing various administrative functions to ensure the smooth operation of the system.
Their responsibilities may include. It seems like you're asking about administrative and
employment-related topics. These are broad areas that encompass various aspects in both
business management and human resources. Here are some key points within each:

A. Office Administration:

➤ Documentation: Managing records, files, and information.

➤ Scheduling: Organizing meetings, appointments, and events.

➤ Office Management: Supervising office operations and ensuring efficiency.

B. Financial Administration:

➤ Budgeting: Creating and managing budgets for different departments.

➤ Expense Management: Handling expenditures, reimbursements, and financial reports.

➤ Bookkeeping: Maintaining financial records and transactions.

C. Project Management:

➤Planning and Coordination: Organizing tasks, timelines, and resources.

➤Team Collaboration: Facilitating teamwork and communication among project members.

➤Risk Management: Identifying and mitigating potential project risks.

D. Policies and Procedures:

➤ Development: Creating and updating organizational policies and procedures.

➤ Implementation: Ensuring compliance and adherence to established policies.

EMPLOYEE:

In the context of requirement analysis or system design, an "Employee" is a role or

actor within a system who interacts with or utilizes the system as part of their job or
responsibilities.

The term "Employee" can encompass various individuals within an organization, each
with specific roles, access levels, and functionalities within the system. Creating a
requirements analysis document is crucial for any project as it helps outline and define the
needs and expectations of stakeholders. Here's an outline you can follow to create a
comprehensive requirements analysis document.

Employment (Human Resources):

Recruitment and Selection:

➤Job Postings: Advertising positions and attracting suitable candidates .

➤ Screening and Interviewing: Assessing candidate qualifications and conducting

interviews.

➤ Hiring: Selecting and onboarding new employees.

Employee Relations:

➤ Conflict Resolution: Mediating disputes between employees or between employees and

management.

➤ Employee Engagement: Improving morale, motivation, and satisfaction within the

workplace.

➤ Performance Management: Evaluating and providing feedback on employee

performance.

Training and Development:

➤ Training Programs: Organizing sessions to enhance employee skills and knowledge.

➤ career Development: Providing opportunities for professional growth and advancement.

Compliance and Legal Issues:

➤Labor Laws: Ensuring compliance with labour regulations and employment laws.

➤Policy Enforcement: Addressing issues related to discrimination, harassment, and

Workplace safety.

Benefits Administration:

➤Healthcare and Insurance: Managing employee benefit packages.

➤Leave and Time Off: Administering vacation days, sick leave, and other time-off policies.

Both administrative and employment functions are crucial for the smooth operation of an
organization.

They involve managing resources, people, and processes effectively to ensure

productivity, compliance, and a positive work environment. The intersection of these areas
often involves HR administration, where administrative functions are tailored to address
employment-related matters within a company. Identifying scenarios involves recognizing
potential situations, events, or challenges that could arise within a specific context, and it's
essential for effective planning and preparedness across various fields.
 Identifying scenarios involves recognizing potential situations, events, or challenges that
could arise within a specific context, and it's essential for effective planning and preparedness
across various fields.

3.1.2 IDENTIFYING SCENARIOS:

Certainly! Identifying scenarios involves recognizing and defining situations or

contexts that might occur within a specific context, system, or environment. These scenarios
can help in planning, analysis, problem-solving, and decision-making. Here are scenarios
across various domains:

Business/Corporate Scenarios:

Market Expansion Scenario:

➤ Scenario: A company plans to enter a new market segment or expand globally.

➤Considerations: Market research, feasibility studies, competition analysis, and regulatory

complianc

Financial Crisis Scenario:

➤ Scenario: Economic downturn impacting company revenues.

➤ Considerations: Contingency planning, cost-cutting measures, and diversification of

revenue streams.

Mergers and Acquisitions Scenario:

➤ Scenario: Company considers merging with or acquiring another business.

➤ Considerations: Due diligence, negotiations, cultural integration, and postmerger

strategies.

Information Technology Scenarios:

Cybersecurity Breach Scenario:

➤Scenario: Unauthorized access compromises sensitive data.

➤Considerations: Incident response, data recovery, security enhancement, and legal

 implications.

Software Development Scenario:

➤ Scenario: Developing a new software product or system.

➤ Considerations: Requirement gathering, development methodologies, testing, and

deployment strategies.

System Downtime Scenario:

➤ Scenario: Critical system failure affecting operations.

➤ Considerations: Backup plans, disaster recovery, and system redundancy.

Healthcare Scenarios:

➤ Pandemic Scenario:

 Scenario: A widespread infectious disease outbreak affecting public health.

 Considerations: Preparedness, response plans, healthcare resource allocation,
and vaccination strategies.

➤Patient Care Scenario:

 Scenario: Emergency medical situations requiring immediate care.

 Considerations: Triage protocols, medical interventions, and patient
stabilization.

Educational Scenarios:

➤Remote Learning Scenario:

 Scenario: Shift from traditional classroom teaching to remote or hybrid learning.

 Considerations: Technology integration, student engagement, and teacher training.

➤Curriculum Development Scenario:

 Scenario: Designing a new curriculum or course.

  Considerations: Learning objectives, instructional methods, assessment strategies, and
alignment with standards.

Environmental Scenarios:

➤Natural Disaster Scenario:

 Scenario: Impact of a hurricane, earthquake, or flood on a community.

 Considerations: Evacuation plans, emergency shelters, relief efforts, and rebuilding

strategies.

➤Climate Change Scenario:

 Scenario: Long-term effects of climate change on ecosystems and societies.

 Considerations: Mitigation strategies, adaptation plans, and sustainable practices.

Personal/Everyday Scenarios:

➤Family Budgeting Scenario:

 Scenario: Managing finances to meet household expenses and savings goals.

 Considerations: Budget planning, expense tracking, and financial priorities.

➤Time Management Scenario:

 Scenario: Juggling multiple responsibilities within a limited timeframe.

 Considerations: Prioritization, scheduling, and delegation of tasks.

SCENARIO FOR LOGIN USER:

Scenario Name Login

Use case Name Login User

Participating Actors Administrator/Employer/Employee
Flow of Events [Link] the ID and password.

[Link] the ID and password were accepted

the would-be user will become as user of
the system.

3. If the ID and password were not

accepted, he will be intimated to try again
for a limited number of trails.

SCENARIO FOR ADD EMPLOYEE:

Scenario Name Registration

Use case Name Add Employee

Participating Actors Employer, Employee

Flow of events [Link] should fill the registration From

with appropriate details.

2. Employer should submit it to

administrator.

3. Administrator will be basic pay, login ID

and password to authorized employee
SCENARIO FOR PAY GENERATION:

Scenario Name Pay generation

Use case Name Pay roll mechanism

Participating Actors administrator

Flow of events [Link] reads basic pay of an

employee.
 2. Calculate [Link], HRA, GLIC and PF.

3. provide pay slip with above data and

across salary and transfers salary of that
employee to his bank account.

SCENARIO FOR SEARCH:

Scenario Name Search details

Use case Name Searching

Participating Actors Administrator/Employer/Employee

Flow of events I user must be authenticated.

2. select his search category and view the

results.

SEARCH FOR UPDATES ASSETS:

Scenario Name Update Assets

Use case Name Update

Participating Actors Administrator

Flow of Events [Link] must be Authenticate himself.

[Link] the assets information from

database.

[Link] making changes save them

IDENTIFYING USSECASE SCENARIOS:

Use case scenario for payroll:

use case Name
Payroll

Participating Actors Administrator

Entry condition End of the month

Flow of events 1. Authentication of Administrator

[Link] an employee
3. Read basic pay.
4. Calculate adding's (HRA, DA, ΤΑ,
ALLOWANCES OTHERS).
5. Calculated deductions. (PT, IT,
INSURENCES, LOAN)
6. Calculate gross salary.
7. pay salary to employee account and pay
tax on his name to authorized bank.
[Link] pay slip and form-16.
Exit condition Transformation completed successfully

Use case for authentication:

Use case Name Authentication

Scenario Name User entry

Participating Actros inherited from authenticate use case.

(Administrator/Employee/Employee)

Entry condition Should be an employee of the organization

Exit condition Iheritedf from authenticate use case.

1. Use case for search assets Information:

Use case Name Search for assets

Scenario Name Resource search

Participating Actors Administrator/Employer/Employee

Should be an employee of the organization

Entry condition

Flow of events [Link] in to the system.

2. invole the search function.
[Link] the search for asserts.

Exit condition
Close the Application
3.1 Use case Model:

Identifying use case overview:

USE CASE EXTENSIBILITY FOR PAYROLL MECHANISM: