LATE BHAUSAHEB HIRAY SMARNIKA SAMITI TRUST

HIRAY GROUP OF INSTITUTES

ISO 9001-2008 CERTIFIED

A PROJECT REPORT ON

INCRENCY® In-Process Check System

FOR

TantraSoft Solutions (I) Pvt. Ltd.

SUBMITTED BY
ANKITA SINGH

MASTER OF COMPUTER APPLICATION

SEMESTER lV
2023-2024
UNIVERSITY OF MUMBAI
 ACKNOWLEDGEMENT

I have completed the Internship at Tata Consultancy Services on iTalent-HR

management System (Regex and Menu management) successfully. Though I
have taken efforts for this project, it was not possible to complete this project
without help of many individuals and the organizations. I would like to thank
them all for their support.

First I would like to thank Mr. Rahul Lad(Project Manager) for his constant
guidance and supervision he provided, and helped me a lot in completion of
project. I would like to show my greatest appreciation to my internal project
guide Prof. Diwakar Jha for their support and guidance.

I am also grateful to the head of M.C.A. department Prof. Dr. Vikram

Patalbansi for giving us an opportunity to undertake the project work.

It would be my pleasure to mention the name of my company- Infosys

Limited where I completed overall project, also I would like to thank all of
my colleagues who provided me constant support and helped me with their
abilities for the successful completion of project.

Finally, I wish to thank the faculty of Late Bhausaheb Hiray S.S Trust’s for the
guidance,inspiration and constructive suggestions that proved helpful to us
throughout the completionof this project.
 Table of Contents

Chapter Contents Page No.

1. Introduction

1.1 Synopsis of the Project

1.1.1 About the Organization

1.1.2 About the Project

1.2 Objective & Scope of the Project

1.3 Problem Definition

1.4 Theoretical Background

1.4.1 Overview of Front End

1.4.2 Overview of Back End

1.4.3 Overview of Reporting Tool

2. System Analysis

2.1 Feasibility Study

2.1.1 Technical

2.1.2 Operational

2.2 System Planning and Schedule

2.2.1 GANTT Chart

2.2.2 PERT Table

2.2.3 PERT Chart

2.2.4 Mind Map

2.2.5 Time Line

2.2.6 Work Break down Structure

3. System Design

3.1 Software Requirement Specification

 3.1.1 Introduction

3.1.2 Selection of Technology/Specific Requirements

3.1.2.1 Hardware to be used

3.1.2.2 Software to be used

3.1.2.3 Tools to be used

3.2 Methodologies Adapted

3.3 Detailed life Cycle of the Project

3.3.1 Object Oriented Analysis & Design Diagrams

3.3.1.1 Use Case Diagram

3.3.1.2 Activity Diagram

3.3.1.3 Sequence Diagram

3.3.2 Flow Chart

3.3.3 Database

3.3.3.1 ER Diagram

3.3.4 I/0 Screen Layout

3.3.5 Processes Involved

3.3.6 Design Testing

4. Testing

4.1 Methodologies used for testing

4.2 Types of Testing

4.2.1 White Box Testing

4.2.2 Black Box Testing

4.3 Test Report

4.3.1 Testing & Result

4.4 Check List

5. System Implementation
 5.1 Hardware required at Client Side

5.2 Software required at Client Side

5.3 Testing Done as End User

6. System Maintenance & Evaluation

6.1 Maintenance

6.2 Evaluation

7. User/Operational Manual

7.1 Security Aspects, Access Rights

8. Future Enhancements

9. Limitations

10. Conclusion

12. Bibliography
 1.Introduction

1.1 Synopsis of the Project

1.1.1 About the Organization
TantraSoft Solutions (I) Pvt. Ltd.

We specialize in electronic data management systems. Multiple instruments/equipment

with electronic (RS232) or electrical (4-20 mA, 0-4 volts, etc.) outputs can be connected to a
single computer via LAN/Wi-Fi for electronic data transfer. Our electronic data management
system can accept inputs from equipment such as weighing scales, vernier calipers,
temperature and humidity sensors, hardness testers, barcode scanners, dissolution
apparatus, etc. Our success stories with the top pharmaceutical companies indicate that our
solutions are well accepted for quality assurance in pharmaceutical industry. This, coupled
with the fact that our system is adaptable equally for Life Science and Non-Life Science
industries, sets the tone for successful adaptation of our systems in Non-Life Science
industries as well. Our solution can be customized for the following industries:
Pharmaceutical Food and Beverage (Bottling units) Biotechnology Laboratories FMCG
Chemical Diamond Animal Houses The system supports 21 CFR part 11 compliance for life
sciences industries. For the past 18 years, Tantrasoft Solutions has been at the forefront of
pharmaceutical manufacturing innovation, collaborating with top industry leaders to
enhance operational efficiencies and accuracy. Our long-standing partnerships with the
biggest names in the pharmaceutical sector reflect our commitment to excellence and our
deep expertise in streamlining complex processes. Embrace the future of pharmaceutical
manufacturing with a leader that is trusted industry-wide.” Trusted By Top Pharma
Companies like Cipla, Sun Pharma, Zydus, Lupin, IPCA, Alembic, Glenmark, Micro Labs,
Ajanta Pharma etc.

Industry - Automation Machinery Manufacturing

Company size - 51-200 employees

Headquarters - Mumbai

Founder - 2006

Specialties - Electronic Data Transfer, Electronic data management system, Supports 21 CFR
part 11 compliance, and Data Integrity in Pharmaceutical industry

1.1.2 About the Project

TantraSoft Solutions (I) Pvt. Ltd. Is a company specialized in interfacing multiple instruments
to single PC for electronic data transfer over LAN network. Electronic Data Transfer -To
collect data from multiple equipment’s from electronic /electrical port and transfer to
application software over LAN network.
Products / Projects
Application Software- (Incrency Inprocess Check System) – is a web application for Data
collection from multiple equipment’s placed in operation area through electronic hardware
over LAN network . It helps in taking data from instruments and passing it to software
through LAN via IDS .
Electronic hardware (IDS) – IDS stands for Intelligent Data Station Installed at remote area of
operation next to equipment.
1.2 Objectives & Scope of the Project
1. PURPOSE
The purpose of this document is to provide design and parameterization of Incrency
Inprocess Check System proposed to be installed at CIPLA UNIT – III GOA plant.
2. SCOPE
In-Scope (TantraSoft): The scope of this design document is for Incrency Inprocess Check
System to be installed at CIPLA UNIT – III GOA. In-Scope (Cipla): The design for Power, LAN
point and IDS enclosure is in scope. Also, Infrastructure Qualification is covered under
installation qualification checks- infrastructure.
3. SYSTEM OVERVIEW
Features of INCRENCY® In-Process Check System:
INCRENCY® In-Process Check System is a data integrity system, consist of software and
hardware. Software is installed on a server and shall be accessible with respected clients.
Software consists of master database and generates reports Hardware – Intelligent Data
Station – is installed close to the Instrument and is used for converting the output from
Instrument into software in computer via LAN. The test Instrument transfers the values to
the system via IDS. The measured values are compared with pre-defined tolerance limits fed
in master data. Master data can be maintained for multiple parameters for all stages of
product. Visual display indicators of the sample being out of tolerance limit, helps the user
to take corrective action. The reports are generated digitally. Benefits of this system:
INCRENCY® In Process Check System can be used via local server by all users in the same
network. Thus, eliminates human error. Reports / records are authenticated, customized
and Date and time stamped of the server. All the data are permanently stored. All the
reports shall be electronically generated and printed reports can be verified manually by
signing the documents. Supports features of 21 CFR part 11 compliance and system is
developed as per GAMP 5 guidelines.

1.1.2 About proposed system:

Architectural Description:

• Programming Language – Incrency system is developed in Angular & Node.js, since it is a

browser-based application.

• Frontend of application is Angular 6 & 7 whereas backend of application is Node.js 10.15

• Node.js is also being used for data abstraction and interfacing multiple devices with
software.

• As an asynchronous event driven JavaScript runtime, Node is designed to build scalable

network applications.
• LDAP (Windows authentication) – is to validate user with windows active directory •
Database – MySQL 5.7 is to store information. Root pages: (../~)

• Style.css Type: Cascading Style Sheet Purpose: To maintain the same style throughout the
application.

• Sidebar Type: component (.ts/.html/.scss) Purpose: To maintain the sidebar and menu
throughout the application.

• Header-navigation Type: component (.ts/.html/.scss) Purpose: To maintain the header

throughout the application.

• authentication/login Type: component (.ts/.html/.scss) Purpose: This is an entry point for

the system.

1.4 Theoretical Background

1.4.1 Overview of Front End
The main motive while developing this project was to develop user friendly screens with
good interface. Hence, Angular was used to develop frontend of proposed system.
Frontend – Angular
Angular is a popular and powerful JavaScript framework for building web applications. It is
developed and maintained by Google and is the successor to the original AngularJS
framework. Angular provides a comprehensive set of tools, libraries, and features that
facilitate the development of scalable, modular, and high-performance applications.
Key features of Angular:

• TypeScript: Angular is built using TypeScript, a statically typed superset of JavaScript.

TypeScript adds features like static typing, classes, interfaces, and advanced tooling
support, which enhance code organization, maintainability, and developer
productivity.
• Component-based architecture: Angular follows a component-based architecture
where the application is divided into reusable and independent components.
Components encapsulate the HTML, CSS, and TypeScript logic related to a specific
part of the user interface, making it easier to manage and maintain the application.
• Templates and Data Binding: Angular uses declarative templates to define the user
interface. Angular’s data binding capabilities allow for automatic synchronization
between the data in the component and the view, enabling a responsive and
interactive user interface.
• Dependency Injection (DI): Angular has a built-in dependency injection mechanism
that helps manage the dependencies between different components and services. DI
 promotes modularity, reusability, and testability by allowing components to consume
services without directly creating instances of them.
• Routing: Angular provides a powerful routing module that allows developers to
define and navigate between different views or pages within an application.
• Reactive Programming: RxJS (Reactive Extensions for JavaScript) enables developers
to handle asynchronous operations, such as HTTP requests, user interactions, and
event streams, using observable streams and operators.

Languages: Typescript, html, CSS

Angular Material as a UI component library that follows the Material Design principles. It
offers a wide range of pre-built and customizable UI components that can be easily
integrated into Angular applications. Angular Material helps in creating visually appealing
and consistent user interfaces.
1.4.2 Overview of Back End
Backend – NodeJs
Node.js is a runtime environment that allows you to run JavaScript code outside of a web
browser. It is built on Chrome's V8 JavaScript engine and uses an event-driven, non-blocking
I/O model, making it lightweight and efficient for building scalable network applications.

Key features of Node.js include:

1. Asynchronous and Event-Driven

Node.js operates on a non-blocking, event-driven architecture. Here's what this means:

• Non-blocking I/O: Node.js uses asynchronous I/O operations, meaning it can handle
multiple requests concurrently without waiting for each operation to finish before
moving on to the next one. This is crucial for performance in applications that need
to handle many simultaneous connections or I/O-bound tasks (like reading from a file
or making network requests).
• Event-driven: Node.js uses an event loop to handle events and execute callbacks
when an event occurs. This event-driven architecture allows Node.js to efficiently
manage I/O operations and respond to events such as incoming requests or data
streams.

2. Single-Threaded and Event Loop

Node.js is single-threaded but uses an event loop to handle multiple concurrent requests
efficiently:

• Single-threaded: Node.js uses a single-threaded event loop to handle all I/O

operations asynchronously. This means it can serve many requests in parallel without
creating new threads for each request, which is more memory efficient compared to
traditional thread-based models.
 • Event loop: The event loop is a mechanism that allows Node.js to perform non-
blocking I/O operations by offloading operations to the system kernel whenever
possible and then notifying the event loop when those operations are complete. This
enables Node.js to handle multiple requests concurrently with minimal overhead.

3. Node Package Manager (npm)

Node.js has a robust ecosystem of libraries and packages available through npm:

• npm (Node Package Manager): npm is the default package manager for Node.js and
hosts over a million packages of reusable code. It allows developers to easily install,
manage, and share packages and dependencies needed for their applications.
• Modules: Node.js uses a module system based on CommonJS, where each file is
treated as a module with its own scope. Modules can export functionalities using
module.exports and exports, making it easy to structure applications and reuse code.

4. Cross-Platform Compatibility

Node.js is designed to run on various operating systems:

• Supported Platforms: Node.js supports major operating systems like Windows,

macOS, and various Unix-like systems (Linux, FreeBSD, etc.), making it versatile for
different development environments.

5. Server-Side Development

Node.js is well-suited for building server-side applications and APIs:

• Web Servers: Node.js can serve HTTP requests and handle routing, middleware, and
database interactions, making it a popular choice for building web servers and APIs.
• Real-Time Applications: Its event-driven architecture makes Node.js particularly
suitable for real-time applications such as chat applications, online gaming, and
collaborative tools where responsiveness and scalability are critical.

6. Scalability and Performance

Node.js offers scalability and performance advantages:

• Scalability: Node.js applications can handle a large number of concurrent

connections efficiently due to its non-blocking, event-driven architecture and
lightweight nature.
• Performance: By leveraging asynchronous I/O operations and the event loop, Node.js
can handle I/O-bound tasks and respond to events quickly, making it well-suited for
high-performance applications.

Getting Started with Node.js

To start using Node.js:

 • Installation: Download and install Node.js from the official website (nodejs.org) or
use a package manager like npm or yarn to install it on your system.
• Creating Applications: Write JavaScript code using Node.js APIs and modules. You can
create server-side applications, APIs, command-line tools, and more.
• Using npm: Explore and install packages from npm to extend the functionality of your
applications.

Node.js has become a popular choice for modern web development due to its efficiency,
scalability, and vibrant ecosystem, making it suitable for a wide range of applications from
small utilities to large-scale enterprise systems.

Database : MySql

MySQL is a popular open-source relational database management system (RDBMS) known

for its reliability, performance, and ease of use. It is widely used in web development for
storing and managing structured data.

Key Features of MySQL:

1. Relational Database Management System (RDBMS):

o MySQL is a relational database, meaning it organizes data into tables with
predefined relationships between them. This structure allows for efficient
querying and retrieval of data.
2. SQL (Structured Query Language):
o MySQL uses SQL as its query language for interacting with databases. SQL
allows developers to perform operations such as inserting, updating, deleting,
and retrieving data from tables.
3. Client-Server Architecture:
o MySQL follows a client-server architecture where clients (applications or
users) communicate with the MySQL server to perform database operations.
The server manages data storage, retrieval, and access control.
4. Scalability and Performance:
o MySQL is designed for scalability, allowing it to handle large volumes of data
and high concurrent user connections efficiently. It supports various storage
engines (like InnoDB, MyISAM) that offer different performance
characteristics and features.
5. High Availability and Replication:
o MySQL supports features like replication and clustering to ensure high
availability and fault tolerance. Replication allows data to be replicated across
multiple servers for redundancy and load balancing.
6. Security Features:
o MySQL provides robust security features including user authentication, access
control, encryption for data in transit and at rest, and auditing capabilities.
These features help protect sensitive data from unauthorized access and
ensure compliance with security standards.
7. Cross-Platform Support:
 o MySQL is available on various operating systems including Linux, Windows,
macOS, and others, making it versatile for different development and
deployment environments.

Common Use Cases for MySQL:

• Web Applications: MySQL is widely used as the backend database for web
applications, powering content management systems (CMS), e-commerce platforms,
forums, and more.
• Data Warehousing: It is used for storing and analyzing large volumes of data in data
warehousing scenarios, often in conjunction with analytics and reporting tools.
• Content Management: Many content management systems (CMS) like WordPress,
Joomla, and Drupal use MySQL as their database backend.
• Business Applications: MySQL is suitable for developing and maintaining business
applications that require reliable data storage and retrieval capabilities.

Getting Started with MySQL:

To use MySQL effectively:

• Installation: Download and install MySQL from the official website (mysql.com) or
use package managers available for your operating system.
• Configuration: Configure MySQL server settings such as database storage locations,
authentication methods, and security settings based on your requirements.
• Connecting and Managing Databases: Use MySQL client tools like MySQL
Workbench, phpMyAdmin, or command-line tools to connect to MySQL servers,
create databases, define tables, and manage data.
• Programming with MySQL: Integrate MySQL into your applications using MySQL's
native connectors for various programming languages (e.g., MySQL
Connector/Python, MySQL Connector/J for Java).

MySQL's popularity stems from its reliability, performance, and extensive community
support. Whether you're building a small-scale application or a large-scale enterprise
solution, MySQL provides the tools and capabilities necessary to manage your data
effectively.
 2. System Analysis

2.1 Feasibility Study

A feasibility study is to determine the practicality and viability of the project before
committing significant resources to its development. It involves evaluating various aspects of
the project, including technical, economic, operational, legal, and scheduling considerations.
The primary goal of a feasibility study is to determine if the project is feasible and if it should
proceed to the next phase of development.
2.1.1 Technical Feasibility
Technical Feasibility focuses on evaluating the technological requirements, constraints, and
capabilities associated with the project. The purpose of assessing technical feasibility is to
ensure that the necessary technology and infrastructure are available to support the project
development, implementation, and ongoing operation.

Technologies involved in development of this system include:

Angular - Angular is a robust and feature-rich framework that provides a comprehensive set
of tools and capabilities for building complex web applications. It offers built-in support for
essential features such as data binding, component-based architecture, dependency
injection, routing, and form handling. These features help developers build scalable and
maintainable applications more efficiently.

• By offering a comprehensive framework, component-based architecture, powerful

tooling, and a supportive community, Angular fulfills the technical feasibility
requirements of projects It enables developers to build scalable, maintainable, and
high-performance web applications while providing a rich ecosystem of tools and
resources to support development efforts.

NodeJs - Node.js is a runtime environment that allows you to run JavaScript code outside of
a web browser. It is built on Chrome's V8 JavaScript engine and uses an event-driven, non-
blocking I/O model, making it lightweight and efficient for building scalable network
applications. Key features include Asynchronous and Event-Driven, Single-Threaded, Non-
Blocking, Package Ecosystem (npm), Cross-Platform, Server-Side Development, Scalability

MySql - MySQL is a popular open-source relational database management system (RDBMS)

known for its reliability, performance, and ease of use. It is widely used in web development
for storing and managing structured data. By offering scalability, performance, reliability,
security, extensibility, integration capabilities, developer tools, and continuous support,
Oracle Database fulfils the technical feasibility requirements of project. It provides a robust
and feature-rich database solution for managing and storing data, making it suitable for
enterprise- level applications and projects with demanding data management needs.
2.1.2 Operational Feasibility
Due to developed system, all HR related functions can be carried out from single platform.
By considering operational feasibility factors, organizations can assess the viability and
potential success of proposed project.
2.1.3 Resource Feasibility
Resource feasibility assesses whether an organization has the necessary resources to
successfully execute the proposed system.
Overview of the resource feasibility evaluation process:
1. Identify Resource Requirement
2. Assess Financial Resources
3. Evaluate Human Resources
4. Review Technology and Infrastructure
5. Examine Data and Information Resources
6. Consider External Resources
7. Evaluate Timeframe and Dependencies
8. Mitigate Risks
Resource feasibility study for proposed system was carried out. Adequate members from
different teams helped in achieving the same. It helped in making informed choices
regarding the projects future, enabling stakeholders to understand the feasibility assessment
and the path forward.
2.2 Cost Benefit Analysis
A cost-benefit analysis is a financial evaluation method used to determine whether the
benefits of a project outweigh its costs. In the context of an HR management project, a cost-
benefit analysis helps assess the financial impact and potential return on investment (ROI)
associated with implementing new HR systems, processes, or initiatives.

Following factors can be considered to understand cost factors of the project:

- Strategic Alignment
- Stakeholder Engagement
- Technology Infrastructure
- Data Management and Analytics
- Compliance and Legal Requirements
- Employee Experience and Engagement
- Change Management and Training
- Performance Measurement and Evaluation
- Continuous Improvement

Benefit factors are considered as:

Application is flexible and can be aligned with geography-based requirements
Developed system will be connected to all peripheral applications like
GRS/NCP/GESS/SAP etc through EAI for employee data feed to downstream
applications
Essential service functionality will be created and multiple functions can be
implemented from through single application.
2.3 System Planning and Schedule

GANTT Chart

Time Line
 3. System Design

3.1. Software Requirement Specification

3.1.1 Introduction
Software Requirements Specification (SRS) is a comprehensive document that outlines the
functional and non-functional requirements of an IT project. The SRS serves as a blueprint
for the development team, helping them understand the projects scope, goals, and specific
requirements. SRS composed of clearly mentioned requirements to achieve the end
objective and core functionality of the project.

Requirements are as follows:

▪ Functional Requirements
1. ® In Process Check System can be used via local server by all users in the
same network. Thus, eliminates human error. Reports / records are
authenticated, customized and Date and time stamped of the server. All the
data are permanently stored. All the reports shall be electronically
generated and printed reports can be verified manually by signing the
documents.

▪ Non-Functional Requirements
1. Non-Functional Requirements often focus on aspects such as
performance,
2. security, usability, reliability, scalability, and maintainability.
3. The system should be available and accessible to users during
scheduled
4. hours, with minimal downtime for maintenance or upgrades.
5. System must have user-friendly interface that is easy to navigate and
understand.
6. The system should support secure login mechanisms to ensure
authorized access to sensitive data.
7. The system should enforce appropriate access controls, ensuring that
users can
8. only access the data they are authorized to view or modify.
9. The system should be designed in a modular manner, allowing for
easier
10. maintenance and future enhancements.
3.1.2 Selection of Technology / specific requirements

Following Hardware and Software environment is used in the project:

1. Hardware to be used

Server Name Quantity Hardware Configuration

Transaction Database 1 Inter® core i5

Server 4 GB RAM

160 GB HDD

Websever and Application 1 1 Inter® core i5

server 4 GB RAM

160 GB HDD

Work station 42 Inter® core i5

4 GB RAM

160 GB HDD

-
2. Software to be used

Software Product Vendor

Operating System Windows NT / Unix Microsoft / HP

Database MySql Sun Microsystems

Browser (client) Internet Explorer. Microsoft,

Chrome, Safari, Google,Apple
Firefox
etc.

3. Tools to be used

Following tools are required for the development of project:

▪ IDE : Eclipse, Visual Studio Code

▪ Database : PL/SQL Developer
▪ Github for code integration

4 . DEVELOPMENT TOOLS AND STANDARDS

Sr. No Development Module Development Tools

1 Software Designing & Development Visual Studio Code, Visual Studio, Android
studio, Keil uvision, Simplicity Studio

2 Database Development & Design MySql, SqlYog Community Edition, SQL Server,
Sql Server Management Studio

3 Report Designing JaspersoftIreport designer, TibcoJaspersoft

Studio. Crystal Reports

4 Version Controlling Github

3.2 SYSTEM DEVELOPMENT MODEL
Developers have determined criteria for selection of suitable System Development Model
considering our Company Policy, Goals and Objectives.

CRITERIA FOR SELECTION OF SDLC MODEL

• Systems shall be developed within given time and estimated cost.

• Development shall focus on verification and validation activities at each stage of life cycle

• Development shall enhance probability of building an error free, good quality systems

• Highly disciplined development model that shall guide testing at each stage of
development.

• Development shall be based on three specification phases - User Requirements, Functional

Specifications and Design Specifications. Above all criteria determined by our developers will
be met using V Model for system development, hence we have V model for system
development, where ‘V’ stands for verification and validation.

3.3 RISK BASED APPROACH

Bugs observed during development / testing / documentation / installation or in systems
that are already installed and validated or in validated documents, risk assessment shall be
done considering its severity, probability of occurrence (chance of risk event to occur) and
probability of detection (likely to get detected). Any process changes recommended in the
installed systems shall also under go risk assessment before undergoing the change and
implementing the same. Recommended corrective action to mitigate the observed issue /
change, also shall be assessed before implementation as a measure of risk control.

3.4 RISK ASSESSMENT AND RISK CONTROL PROCESS

3.3 Methodologies adapted

Project management methodology is a framework that helps you to manage your

project in the best way possible. Project management is so important to organizations and
teams, but in order for it to be really effective, it needs to be correctly mapped to team type,
project, organization, and goals. There are several methodologies that can be adapted for IT
projects. Also, the choice of methodology depends on various factors such as project size,
complexity, team size, organizational culture.

Agile methodology is characterized by several unique features that set it apart from

traditional project management approaches. Hence, Agile methodology was adopted for

development for this project.

Agile methodology:

Agile methodology is an iterative and incremental approach to project management

that is widely used in software development and other industries. It emphasizes flexibility,

collaboration, customer satisfaction, and continuous improvement.

Values and Principles: Agile methodology is based on the Agile Manifesto, which

outlines four key values:

• Individuals and interactions over processes and tools

• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Agile methodology follows a set of 12 principles that guide project execution,

including customer involvement, delivering working software frequently, embracing change,

and empowering self-organizing teams.

• Iterative and Incremental Approach: Agile projects are divided into short iterations
or sprints, typically lasting 1-4 weeks. Each iteration delivers a working increment of
the product, which can be reviewed and evaluated by stakeholders. The product is
developed incrementally, with new features and improvements added in each
iteration.

• Scrum Framework: Scrum is a popular Agile framework that provides a structure for
managing projects. It includes specific roles, artifacts, and ceremonies:

• Roles: The Scrum Master, Product Owner, and Development Team collaborate to
deliver the product.

• Artifacts: The Product Backlog, Sprint Backlog, and Increment capture the
requirements, tasks, and progress of the project.

• Ceremonies: Daily Stand-ups, Sprint Planning, Sprint Review, and Sprint

Retrospective facilitate communication, planning, review, and improvement.
 • Continuous Collaboration and Customer Involvement: Agile methodology promotes
active collaboration and involvement of the customer or product owner throughout
the project. Customers provide feedback, clarify requirements, and validate
deliverables ensuring that the product meets their needs and expectations. Regular
communication and collaboration within the team and with stakeholders are key
components of Agile.

• Embracing Change: Agile recognizes that requirements and priorities can change
throughout the project. It encourages flexibility and embraces change as a natural
part of the development process. Changes are incorporated through ongoing
collaboration, regular feedback, and prioritization, allowing the project to adapt and
deliver the most valuable product.

• Continuous Improvement and Adaptation: Agile methodology fosters a culture of

continuous improvement. Retrospectives are held at the end of each iteration to
reflect in the teams processes, identify areas for improvement, and make
adjustments. Lessons learned are applied in subsequent iterations, leading to
increased efficiency,quality, and team effectiveness.

• Empowered and Self-Organizing Teams: Agile teams are self-organizing and cross-
functional. They have the autonomy to make decisions, collaborate closely, and
collectively take ownership of the projects success. This empowerment fosters
creativity, engagement, and a sense of collective responsibility.

• Delivering Value Early and Frequently: Agile focuses on delivering working software
or increments of the product at the end of each iteration. This allows stakeholders to
see tangible progress, provide feedback, and validate the direction of the project. By
delivering value early and frequently, Agile projects can adapt to changing
requirements and achieve customer satisfaction.

Agile methodology provides a flexible and collaborative approach to project

management, enabling teams to deliver high-quality products that meet customer needs. It
promotes customer satisfaction, continuous improvement, and adaptability in a rapidly
changing environment.
Application of methodology in project:
Agile training - Agile training was given to team and key stakeholders involved in the
project to make them understand Agile principles, values, and practices. Also, team member
were trained to use TCS provided tools ( Prime work / jile ) to manage agile workflow.

Identification of Project Scope - Clearly defined the scope of the project. Identified the
specific goals, objectives, and deliverables want to achieve using Agile.

Creation of product backlog - Product backlog was created as per the deliverables of the
project and required functionalities. Also, prioritization of backlog items based on their
importance and value was done.

Formation of Cross-Functional Teams - Cross-functional teams consisting of HR

professionals, managers, IT specialists, and other relevant stakeholders were created. Each
team was created considering it should have a mix of skills and expertise required to execute
the project effectively.

Creation of Sprints - Sprints are short iterations, typically ranging from one to four weeks.
Sprints were planned by selecting set of items or functionality to be developed from the
product backlog in each sprint. Developers, scrum master, stakeholders were the part of
sprints developed for every module.

Defining user stories - Break down the backlog items from sprint into user stories. User
stories are concise, customer-centric descriptions of specific features or functionalities.
Define user stories collaboratively with the team and ensure they are clear, actionable, and
testable. Afterwards development is carried out based on the user stories provided.

Sprint Execution - It was decided to execute the sprint by working on the user stories
selected during sprint planning. Encourage close collaboration, regular communication, and
knowledge sharing within the team. Monitor progress through daily stand-up meetings and
track tasks on a visual board or Agile project management tool.

Conduct Daily Stand-up Meetings (Scrum meeting) - Daily Scrum where team members
share their progress, discuss any challenges or roadblocks, and plan their tasks for the day
were scheduled to be conducted. These short meetings help keep the team aligned and
facilitate quick issue resolution.

Embrace Iterative Development: Embrace the iterative development approach by

delivering small increments of work within each sprint. This allows for frequent feedback,
adjustments, and the ability to adapt to changing requirements.

Conduct Sprint Review and Retrospective - At the end of each sprint, sprint review to
showcase the completed work to stakeholders and gather their feedback was decided to be
conducted. Also, sprint retrospective meeting to reflect on the team's performance,
identify
areas for improvement, and make adjustments to the process.

Continuously Adapt and Improve - Use the feedback received during sprint reviews and
retrospectives to refine the product backlog, reprioritize user stories, and make necessary
adjustments to the project plan. Continuously learn and improve the project based on
feedback and evolving business needs.
3.3 Detailed lifecycle of the project

3.3.1. Modules
Main modules involved in this project are as follows:

Login screen
Dashboard

Add user
Add Tablet
Area setting to add instruments on particular IDS
Cubicle Setting
Batches active in particular area

Batch in cubicle setting with Product information

Report view
Hardware Screen

Login
Menu Screen
Test Screen
Database
 • Authorization Tagging

Description This use case describes the tagging of authorization

Trigger The tagging should be done to a valid employee ID
Actors User
Preconditions The authorization must be created properly and should be visible under the
authorization names
Post The tagging of authorization should be properly processed at User

Step No Actor Action Notes and references

1 User The authorization is to be created
2 User Tagging of authorization is done under
the Tagging Authorization and Data
Boundary tab against the Authorization
name created.
3 User Tagging is done with a valid employee Proper employee ID should
ID against the authorization name. be tagged against the
authorization.
4 User The tagging details are visible against
the corresponding authorization name

• Authorization Access

Description This use case describes the access of tagged authorization

Trigger The access is only given to the employee ID which is tagged against the
authorization name
Actors User
Preconditions The tagging of authorization should be done in proper manner
Post The access should be properly processed at iTalent

Step No Actor Action Notes and references

1 User User should login into the system and
access the authorization like ‘person’.
2 User Once person infocard is opened, user
can edit and modify details.
3 User Details will get processed and will be
reflected on iTalent.
 • Infocard Management

Description This use case describes how to modify the configuration of an Infocard
Trigger Infocards cannot have same infocard ID
Actors User
Preconditions Infocard should exist in database in iTalent
Post The fields of the infocard should be properly processed in iTalent

Step No Actor Action Notes and references

1 User In the infocard management page, all
the infocards are displayed along with
their fields.
2 User Any changes can be made in these fields
according to the requirements.
3 User The changes once made should be There are two options, one
saved and then the changes will be is Save and the other is
visible in the respective infocard. Apply to all BGs. Apply to
all BGs will change the data
in all the infocards and
Save will change the data
only in the infocard in
which you have made the
changes.

• Dataset Management

Description This use case describes the dataset configuration

Trigger User should have the access for this
Actors User
Preconditions NA
Post The configuration of the dataset should be properly processed in User

Step No Actor Action Notes and references

1 User A dataset is to be created under the Dataset Name, Effective
dataset management. Start date, Set Type and Set
Category are mandatory
fields.
2 User Search for the dataset and check The dataset can be edited.
whether it has been created and
mapped correctly.

3 User Dataset tagging is done against the

infocard field through infocard
management.
FLOW CHART FOR INDIVIDUAL TEST
 5. Testing

5.1 Methodologies used for testing:

In Agile methodology, testing is an integral part of the development process and is
carried out continuously throughout the project lifecycle. Here's an overview of how testing
is typically conducted in Agile:

• Test Planning: Agile teams collaborate to define the testing strategy, scope, and
objectives for each iteration or sprint. This includes identifying the features or user
stories to be tested, prioritizing them, and estimating the effort required.

• Test Design: Testers work closely with developers, product owners, and other
stakeholders to create test scenarios and test cases based on the acceptance criteria
defined for each user story. These test cases focus on validating the functionality and
behaviour of the software.

• Test Execution: Testing is performed iteratively during each sprint. Testers execute
the test cases designed in the previous step, aiming to uncover defects and ensure
that the software meets the desired quality standards. Automated testing tools are
often employed to improve efficiency and reliability.

• Defect Reporting: When issues or defects are identified during testing, testers report
them to the development team. Defects are typically tracked in a bug tracking system
or issue management tool, allowing for better collaboration between developers and
testers to resolve the issues.

• Continuous Integration and Testing: In Agile, the development and testing processes
are closely integrated. Continuous integration practices ensure that code changes
made by developers are frequently merged and tested. Automated test suites are
executed regularly to catch any regression issues.

• Test Automation: Agile teams prioritize test automation to accelerate testing efforts.
Automated tests help ensure faster feedback, reduce manual effort, and enable
 frequent regression testing. Test automation frameworks and tools are used to create
and maintain automated test scripts.

• User Acceptance Testing (UAT): UAT is performed to obtain user feedback and
validate that the software meets the end-users' requirements. This typically involves
engaging stakeholders or actual users to perform real-world scenarios and provide
feedback on the functionality.

• Retrospectives and Continuous Improvement: At the end of each sprint, Agile teams
conduct retrospectives to reflect on the testing process and identify areas for
improvement. These insights help refine the testing practices, adapt strategies, and
enhance the overall development process.

It's worth noting that Agile testing follows the principle of "Test Early, Test Often," promoting
collaboration, adaptability, and continuous feedback loops to ensure high-quality software is
delivered incrementally throughout the project.

5.2 Types of Testing

White box testing

Also known as clear box testing, structural testing, or glass box testing, is a software
testing technique that focuses on examining the internal structure, design, and
implementation of the software being tested. The primary goal of white box testing is to
ensure that the internal logic and code of the software function correctly, as well as validate
the completeness and accuracy of the implemented features.
White box testing is typically performed by testers who have access to the source code,
architectural diagrams, and other internal details of the software. They use this knowledge
to design and execute test cases that specifically target different paths, conditions, and
branches within the code.
Our developers with access to code, carried out this testing. It involves checks to
determine
• Test coverage: It includes techniques such as statement coverage, branch coverage,
path coverage, and condition coverage to analyze and measure the extent to which
the code has been tested.
 • Code-level testing: Testers focused on individual units or components of the
software, such as functions, methods, or classes, to verify their behaviour and
interactions.
• Code analysis: Testers analyzed the code structure, algorithms, and data flow to
identify potential defects, bottlenecks, or security vulnerabilities.
• Data Flow Testing: Testers examined how data is transferred and manipulated within
the code, focusing on variables, assignments, and data dependencies.
Basically, development was tested at code level at the time of white box testing to
determine proper functionality as per code developed.

Black box testing

Black box testing is a software testing technique that focuses on assessing the
functionality and behavior of a software system without considering its internal structure or
implementation details. It is performed from an external perspective, treating the software
as a "black box" where only inputs and outputs are visible and accessible.

In black box testing, the tester does not have access to the internal code,
architecture, or design of the software. The objective is to verify if the software meets the
specified requirements, behaves as expected, and handles different inputs correctly,
regardless of how it is implemented.

The black box testing of proposed system was carried out by users through which
requirement was received. They tested the flow as per the requirement given for
development in sprint and expected outcome of the sprint.

Following steps were involved in black box testing:

• Test Scenario Design

• Input Validation
• Functional Testing
• Specification Compliance
• Usability Testing
• Error Handling and Recovery
5.3 TOOLS REQUIRED FOR TEST ENVIRONMENT
➢ Incrency In-Process Check System setup
➢ Node JS 10.13 / Node JS 16.14 or above
➢ MySQL 5.7 / MS-SQL 2019 or above
➢ SqlYog Community Edition 13.01
➢ Google Chrome browser
➢ Foxit Reader 6.1.4 or above
➢ Java 1.7 or above
➢ Apache 2.4 service or above
➢ Remote access software
➢ Mosquito MQTT broker 1.6 or above
➢ MQTT.FX 1.7.0 or above

5.3.1 Test Cases

Module/
Area/ Test Case Actual
Sl No. Process Description Expected Result Test Data Result

Person Basic
information
like name,
Person Open forms and Person Infocard will be group hire
1 Infocard click on Person loaded date etc. OK
Person Basic
information like
Person Click on create blank person form will name, group hire
2 Infocard new open date etc.
Person Basic
fill up all required different options for information like
Person fields and click creating person will name, group hire
3 Infocard on action come in pop up date etc.
Person Basic
choose any message shown that information like
Person option and click employee craeted name, group hire
4 Infocard on confirm successfully date etc.
Person Basic
information
like name,
Person Click on search Pop up will be opened group hire
5 Infocard button to search employee date etc. OK
 Search employee
by giving Person Basic
employee information
number and click like name,
Person on the search Employee person group hire
6 Infocard data details will be loaded date etc. OK
I.User will get option for
correct or update data
if the employee is
created before system Person Basic
date. information
Change some II.User will get correct like name,
Person field value and option if person is group hire
6 Infocard click on save created on system date. date etc. OK

Negative
Testing
While creating a Error meassage displayed as
person give BG “Company Joining date Person
joining date less should be equal or greater BG
Person than group joining then the group joining joining
Infocard date date” date OK

Module/
Area/ Test Case Actual
Sl No. Process Description Expected Result Test Data Result

Use search field in Employee

the pop up and Number
Assignment Click on search choose one option
1 Infocard button OK
Delete the
Click Untag data in information that was
Organization field tagged in the field Employee Number
Assignment
2 Infocard
See the options in
the scroll down
Click Assignment menu and choose
reason button one Employee Number
Assignment
3 Infocard
 Use search field in
Click Location and the pop up and
search button choose one option Employee Number
Assignment
4 Infocard
Delete the
Click Untag data in information that was Employee
Location field tagged in the field Number
Assignment
5 Infocard . OK
Use search field in
the pop up and Employee
Click
choose one option Number
Assignment Role/Responsibility
6 Infocard and search button OK

Negative
Testing
Required to fill
up all necessary Basic details are filled up
fields and also miss to enter data of
need to check all Base details. Assignment
the associated details does not get Employee
tabs. saved. Number
Assignment
Infocard OK
 Module/
Area/ Test Case Actual
Sl No. Process Description Expected Result Test Data Result

Only an HR User is able Hierarchy

Log in as HR user to see the screen. Name
Employee
1 movement OK
Click on the Search pop up opens
search data icon with all Organization
from the Tool bar Hierarchy Name. Hierarchy Name
Employee
2 movement
The corresponding
Click on any Organization Hierarchy
Organization details is being
Hierarchy Name displayed. Hierarchy Name
Employee
3 movement
Enter any
organization
name and click Desired organization
search button name is displayed. Hierarchy Name
Employee
4 movement
Enter hierarchy
name and tick
enabled button,
position control
and display fields
and after that The organization
click on save hierarchy details is Hierarchy
button in toolbar saved successfully. Name
Employee
5 movement OK
Click on History
button to view
the history
record and click
on the history
from the list to history details is Hierarchy
display it displayed Name
Employee
6 movement OK
click on date details from that date is Hierarchy
updated successfully Name
Employee track to update
6 movement the details from OK
 that date and
update it

6. System Implementation

6.1 Hardware required at Client Side

• Server Name Quantity Hardware Configuration

Transaction Database 1 Inter® core i5
Server 4 GB RAM
160 GB HDD
Websever and Application 1 Inter® core i5
server 4 GB RAM
160 GB HDD
Work station 42 Inter® core i5
4 GB RAM
160 GB HDD

With above minimum specifications, better performance of system can be achieved.

6.2 Software required at Client Side

Software Product Vendor

Operating System Windows NT / Unix Microsoft / HP
Webserver and EJB Server JBoss 7.0 JBoss
Database PostgreS 9.1 PostgreS
Browser (client) Internet Explorer. Chrome, Microsoft, Google,Apple
Safari, Firefox etc.

Tools to be used

Following tools are required for the development of project:

 • IDE : Eclipse, Visual Studio Code
• Database : PL/SQL Developer
• Github for code integration

6.3 Testing done as end user

User Acceptance testing:

User Acceptance Testing (UAT) is a phase of software testing where the software is
evaluated by end-users or representatives of the intended audience to determine whether it
meets their requirements and is ready for production release. UAT serves as the final
validation before the software is deployed to the users.

At the end of every iteration of sprint, developed artifact was given to end users for testing.
As per their feedback changes were implemented and final deliverable was achieved for
which UAT sign-off was received.

Beta testing:
Beta testing is a type of user acceptance testing that involves releasing a pre-release
version of software to a select group of external users, known as beta testers or beta users.
The purpose of beta testing is to gather real-world feedback and uncover any remaining
defects or usability issues before the software is officially launched to a wider audience.
Beta version of system was released to determine unfound issues if any, associated
with system. As, there were no complications found in beta testing final version of software
was deployed.
 7. System Maintenance & Evaluation

7.1 Maintenance
The maintenance of an system involves a range of activities aimed at ensuring the
system remains functional, secure, and up to date. Here are some key aspects followed for
system maintenance:

Regular Updates and Upgrades: Stay up to date with the latest versions. Apply patches, bug
fixes, and updates provided by the system vendor to address any known issues and improve
system performance.

System Monitoring: Continuously monitor the system to identify any performance issues,
errors, or anomalies. Utilize monitoring tools to track system health, server resources,
database performance, and user activity. Proactively address any issues that may arise to
minimize downtime and ensure optimal system performance.

Data Backup and Recovery: Regularly back up system data to protect against data loss or
corruption. Establish a backup strategy that includes both onsite and offsite backups. Test
the backup and recovery processes periodically to verify the integrity and availability of the
data.

Security Measures: Implement robust security measures to protect sensitive data. This may
include access controls, encryption, user authentication, and audit trails. Regularly review
and update security configurations, perform vulnerability assessments, and stay informed
about security best practices to mitigate the risk of data breaches.

User Support and Training: Provide ongoing user support to address any questions, issues, or
training needs of system users. Offer documentation, user guides, and training materials to
ensure users understand how to effectively use the system. Stay responsive to user feedback
and continuously improve the user experience.

Customization and Configuration: Assess the system's configuration and customization

options to align it with evolving DSA processes and requirements. Regularly review system
configurations to ensure they reflect current organizational needs. Consider leveraging
system integrations or add-ons to extend functionality and improve efficiency.
Compliance and Regulatory Updates: Keep legal and regulatory changes that may impact the
system's functionalities or data management. Stay updated on industry best practices, data
privacy laws, and compliance requirements. Adjust system configurations and workflows as
necessary to remain in compliance.

Performance Evaluation and Enhancement: Regularly evaluate the system's performance

and effectiveness in meeting objectives. Collect user feedback, conduct surveys, and analyze
system usage metrics. Identify areas for improvement and enhancements, and consider
future system upgrades or migration to better meet evolving needs.

By proactively maintaining system, organizations ensures that it remains reliable,

secure, and aligned with their processes. Regular updates, monitoring, data backups, user
support, security measures, and continuous improvement efforts are key to maintaining a
robust and efficient system.

7.2 Evaluation
Evaluating an system involves assessing its performance, effectiveness, and
alignment with the organization's objectives. Here are some steps which were carried out in
evaluation:

Define Evaluation Criteria: Determine the criteria against which you will evaluate the system.
These criteria can include system functionality, usability, data accuracy, performance,
security, scalability, compliance, integration capabilities, user satisfaction, and alignment
with goals.

Gather User Feedback: Collect feedback from system users, including HR professionals,
managers, and employees. Use surveys, interviews, or focus groups to understand their
experiences, challenges, and satisfaction levels with the system. Identify areas of
improvement or specific pain points they may be facing.

Analyze System Metrics: Utilize system metrics and usage data to assess its performance.
Look at key performance indicators (KPIs) such as system uptime, response time, user
adoption rates, transaction volumes, and data accuracy. Identify any patterns or trends that
indicate areas for improvement or potential issues.
Evaluate Functionality: Review the system's functionalities and features against the
organization's requirements. Assess whether the system adequately supports essential
processes such as employee onboarding, performance management, training and
development, compensation, benefits administration, and reporting. Identify any gaps or
limitations in functionality.

Assess User Experience: Evaluate the system's user interface, intuitiveness, and ease of use.
Consider factors such as navigation, search capabilities, data entry processes, and overall
user satisfaction. Identify any areas where the system may cause confusion, require
excessive manual effort, or hinder productivity.

Review Data Integrity and Reporting: Examine the accuracy, completeness, and consistency
of the HR data stored in the system. Verify that data inputs and outputs are reliable and that
reporting capabilities meet the organization's needs. Assess the system's ability to generate
standard reports, customize reports, and provide insights for analytics.

Consider Integration and Scalability: Assess the system's integration capabilities with other
HR and enterprise systems. Determine if it can effectively exchange data and synchronize
information with other applications. Evaluate its scalability to handle increasing data
volumes, user growth, or organizational changes.

Evaluate Security and Compliance: Review the system's security measures, access controls,
data encryption, and compliance with data privacy regulations. Assess if the system provides
adequate protection for sensitive data. Verify that the system aligns with relevant industry
standards and legal requirements.

Compare with Industry Standards and Best Practices: Benchmark the system against industry
standards and best practices. Stay informed about emerging technologies, trends, and
innovations in software. Identify areas where the system can be enhanced or aligned with
leading practices.

Prioritize Areas for Improvement: Based on the evaluation findings, prioritize areas for
improvement or enhancement. Create an action plan that addresses the identified gaps or
challenges. Consider system upgrades, customization, process optimizations, training
programs, or other initiatives to enhance the system's effectiveness.
 Regular evaluation of the system ensures that it continues to meet the organization's
evolving needs and remains a valuable tool for DSA operations. By considering user
feedback, system metrics, functionality, user experience, data integrity, security, and
compliance, organizations can identify areas for improvement and take proactive steps to
optimize system.
 8. User/Operational Manual

• Security aspects, Access rights

Maintaining the security aspect of a system is crucial to protect against potential threats
and vulnerabilities.

• Proper authentication and authorization mechanisms were applied on the system to

achieve security.
• Multiple layers of security controls were applied.
• Password complexity requirements were implemented and regular password
changes were enforced to users.
• Minimum level of privileges necessary to perform their tasks were granted to users.
• Regular security audits to identify potential vulnerabilities and weaknesses in system
were performed.

• Backups
Maintaining backups of system is crucial to ensure data integrity and facilitate recovery
in case of data loss or system failures.
• critical data, configuration files, databases, and any other important elements
that need to be included in backups were identified.
• Backups were scheduled as per data criticality
• Confidentiality of backed up data was maintained by applying proper encryption
algorithm.
 9.Future Enhancements

The systems is likely to see several enhancements as technology continues to evolve.

Also, we are working towards making system lightweight. Hence, we have used Angular JS
for the development of frontend as it enhances development of SPA (Single Page
Applications) which loads in faster manner, hence decreasing response time. Also, spring
boot is used to remove dependency between multiple modules by using microservices.

• AI and Machine Learning can be implemented in better manner to generate insights

from data developed through system.
• More modules can we integrated in employee self service functionality such as
chatbots to respond to employee concerns, benefits enrolment functionality, etc.
• As per the additional functionalities to be included, system can be evolved to meet
those requirements
 10. Limitations

While digital saving accounts offer numerous advantages, they also come
with certain limitations and challenges that need to be addressed. These
limitations can impact the adoption and effectiveness of digital saving solutions.

1. Security Risks:
Digital saving accounts are vulnerable to cyber-attacks, phishing scams, and data
breaches. Ensuring the security of customer data and transactions is a significant
challenge that requires continuous investment in advanced security measures.
2. Accessibility Issues:
Not all customers have access to the internet or possess the digital literacy
required to navigate online banking platforms. This digital divide can exclude a
portion of the population from benefiting from digital saving accounts.
3. Technical Problems:
Technical issues such as server downtime, software bugs, or connectivity
problems can hinder the accessibility and reliability of digital saving accounts.
Such issues can lead to customer dissatisfaction and loss of trust in digital
banking services.
4. Regulatory Compliance:
Digital saving accounts must comply with various regulatory requirements,
including KYC (Know Your Customer) and AML (Anti-Money Laundering)
regulations. Keeping up with changing regulations and ensuring compliance can
be complex and costly.
5. Limited Personal Interaction:
Some customers prefer face-to-face interactions for their banking needs. The lack
of personal interaction in digital saving accounts can be a drawback for those
who value in-person services and personal relationships with bank staff.
6. Privacy Concerns:
Customers may have concerns about the privacy of their financial data. Ensuring
that customer data is handled securely and transparently is crucial to building
trust in digital saving accounts.
7. Dependence on Technology:
Digital saving accounts are heavily reliant on technology. In the event of
technological failures or natural disasters that disrupt internet services, access to
digital accounts can be compromised.
8. Costs of Technology Adoption:
For banks and financial institutions, the initial setup and ongoing maintenance of
digital saving account systems can be expensive. Smaller institutions may struggle
with the financial burden of adopting and maintaining advanced digital
infrastructure.
9. Customer Support Challenges:
Providing effective customer support for digital saving accounts can be
challenging. Customers may require assistance with technical issues, account
management, and security concerns, necessitating a robust and responsive
support system.
10. Market Competition:
The rapid growth of fintech companies and the increasing competition in the
digital banking space can make it difficult for traditional banks to keep up with
innovations and offer competitive digital saving account services.
 11. Conclusion

The software used in pharmacies within plant settings serves a critical role by facilitating the
seamless integration of data from various instruments through Local Area Network (LAN)
connections. This integration is essential for pharmaceutical operations, where precision
and efficiency are paramount.

Upon receiving data from instruments, the software undertakes sophisticated processing
algorithms tailored to pharmaceutical standards. These algorithms analyze the data,
applying specific calculations and validations to ensure accuracy and reliability in the results
generated. This capability is crucial for maintaining quality control and compliance with
regulatory requirements governing pharmaceutical production.

Once processed, the software generates detailed reports that encapsulate key findings and
outcomes. These reports are not only essential for internal operations but also serve as
critical documentation for regulatory audits and inspections. By automating the generation
of reports, the software streamlines administrative tasks, freeing up valuable time for
pharmacy staff to focus on other essential duties.

Moreover, the software enhances communication and collaboration within the pharmacy
setting. It facilitates real-time access to data and results across different departments or
locations within the plant, fostering efficient decision-making and coordinated efforts.

In terms of security, the software employs robust measures to safeguard sensitive

pharmaceutical data. Encryption protocols, access controls, and audit trails are typically
implemented to ensure confidentiality and integrity throughout data transmission and
storage processes.

The integration of such software into pharmacy operations within plants not only improves
operational efficiency but also enhances overall productivity. By minimizing manual errors
and reducing the time required for data processing and reporting, the software contributes
to cost savings and operational effectiveness.

Furthermore, the software's ability to adapt and scale with evolving technological and
regulatory landscapes is crucial. Regular updates and enhancements ensure that the
software remains compliant with changing regulations and continues to meet the dynamic
needs of pharmaceutical manufacturing.

In conclusion, the software used in pharmacies within plants, which leverages LAN
connectivity to integrate instrument data, plays a pivotal role in ensuring the accuracy,
efficiency, and compliance of pharmaceutical operations. Its capabilities in data processing,
result generation, and report creation contribute significantly to operational excellence and
regulatory adherence in the pharmaceutical industry.
 12. Appendices

Abbreviation/ Acronym Expansion

CEP Continuous Education Program

FAQ Frequently Asked Questions

GL Group Leader

IPMS Integrated Project Management System

ISU Industry Solution Unit

ODC Offshore Development Centre

PL Project Leader

PM Project Manager

SDD Solution Design Document

SDD System Design document

SRS System Requirement Specification

STP System Test Plan

STS System Test Specification

TCS Tata Consultancy Services

TM Team Member

UTP Unit Test Plan

UTS Unit Test Specification

 13. Bibliography

• https://material.angular.io/
• https://nodejs.org/en
• https://training-course-material.com/training/Nodejs
• Hotokit documents (provided by organization)
• https://docs.oracle.com/cd/B10501_01/appdev.920/a96624/toc.htm