AN

INTERNSHIP REPORT
ON
COSMETIC SHOP MANAGEMENT SYSTEM
PROJECT
BY
KAMAL ACHARYA
(Tribhuvan University)
Date: 2022/02/25

1|Page
 COSMETIC SHOP MANAGEMENT SYSTEM

INTRODUCTION

Buying new cosmetic products is difficult. It can even be scary for those who have
sensitive skin and are prone to skin trouble. The information needed to alleviate this problem is
on the back of each product, but it's thought to interpret those ingredient lists unless you have a
background in chemistry.

Instead of buying and hoping for the best, we can use data science to help us predict which
products may be good fits for us. It includes various function programs to do the above mentioned
tasks.

Data file handling has been effectively used in the program.

The automated cosmetic shop management system should deal with the automation of
general workflow and administration process of the shop. The main processes of the system focus
on customer's request where the system is able to search the most appropriate products and
deliver it to the customers. It should help the employees to quickly identify the list of cosmetic
product that have reached the minimum quantity and also keep a track of expired date for each
cosmetic product. It should help the employees to find the rack number in which the product is
placed.It is also Faster and more efficient way

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the programming knowledge into

a real- world situation/problem and exposed the students how programming skills helps in

developing a good software.

• Write programs utilizing modern software tools.

• Apply object oriented programming principles effectively when developing small to

medium sized projects.

2|Page
 • Write effective procedural code to solve small to medium sized problems.

• Students will demonstrate a breadth of knowledge in computer science, as exemplified

in the areas of systems, theory and software development.

• Students will demonstrate ability to conduct a research or applied Computer Science

project, requiring writing and presentation skills which exemplify scholarly style in

computer science.

PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be really wants to stand

against today’s merciless competition where not to wise saying “to err is human” no longer

valid, it’s outdated to rationalize your mistake. So, to keep pace with time, to bring about the

best result without malfunctioning and greater efficiency so to replace the unending heaps of

flies with a much sophisticated hard disk of the computer.

One has to use the data management software. Software has been an ascent in

atomization various organisations. Many software products working are now in markets, which

have helped in making the organizations work easier and efficiently. Data management initially

had to maintain a lot of ledgers and a lot of paper work has to be done but now software product

on this organization has made their work faster and easier. Now only this software has to be

loaded on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully automated and any

information regarding the organization can be obtained by clicking the button. Moreover, now

it’s an age of computers of and automating such an organization gives the better look.

3|Page
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management technique that divides
complex projects into smaller, more easily managed segments or phases. Segmenting projects
allows managers to verify the successful completion of project phases before allocating resources
to subsequent phases.
Software development projects typically include initiation, planning, design,
development, testing, implementation, and maintenance phases. However, the phases may be
divided differently depending on the organization involved.
For example, initial project activities might be designated as request, requirements-
definition, and planning phases, or initiation, concept-development, and planning phases. End
users of the system under development should be involved in reviewing the output of each phase
to ensure the system is being built to deliver the needed functionality.

4|Page
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE

The Initiation Phase begins when a business sponsor identifies a need or an opportunity.

The purpose of the Initiation Phase is to:

• Identify and validate an opportunity to improve business accomplishments of the

organization or a deficiency related to a business need.
• Identify significant assumptions and constraints on solutions to that need.
• Recommend the exploration of alternative concepts and methods to satisfy the need
including questioning the need for technology, i.e., will a change in the business process
offer a solution?
• Assure executive business and executive technical sponsorship. The Sponsor designates
a Project Manager and the business need is documented in a Concept Proposal. The
Concept Proposal includes information about the business process andthe relationship to
the Agency/Organization.
• Infrastructure and the Strategic Plan. A successful Concept Proposal results in a Project
Management Charter which outlines the authority of the project manager to begin
the project.

Careful oversight is required to ensure projects support strategic business objectives and
resources are effectively implemented into an organization's enterprise architecture. The
initiation phase begins when an opportunity to add, improve, or correct a system is identified and
formally requested through the presentation of a business case. The business case should, at a
minimum, describe a proposal’s purpose, identify expected benefits, and explain how the
proposed system supports one of the organization’s business strategies. The business case should
also identify alternative solutions and detail as many informational, functional, and network
requirements as possible.

5|Page
SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need or opportunity is validated
by the Agency/Organization Program Leadership and the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

• Determine the feasibility and appropriateness of the alternatives.

• Identify system interfaces.
• Identify basic functional and data requirements to satisfy the business need.
• Establish system boundaries; identify goals, objectives, critical success factors, and
performance measures.
• Evaluate costs and benefits of alternative approaches to satisfy the basic functional
requirements
• Assess project risks
• Identify and initiate risk mitigation actions, andDevelop high-level technical architecture,
process models, data models, and a concept of operations. This phase explores potential
technical solutions within the context of the business need.
• It may include several trade-off decisions such as the decision to use COTS software
products as opposed to developing custom software or reusing software components, or
the decision to use an incremental delivery versus a complete, onetime deployment.
• Construction of executable prototypes is encouraged to evaluate technology to support
the business process. The System Boundary Document serves as an important reference
document to support the Information Technology Project Request (ITPR) process.
• The ITPR must be approved by the State CIO before the project can move forward.

6|Page
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development, acquisition, and
maintenance projects. Careful planning, particularly in the early stages of a project, is necessary
to coordinate activities and manage project risks effectively. The depth and formality of project
plans should be commensurate with the characteristics and risks of a given project. Project plans
refine the information gathered during the initiation phase by further identifying the specific
activities and resources required to complete a project.
A critical part of a project manager’ sjob is to coordinate discussions between user, audit,
security, design, development, and network personnel to identify and document as many
functional, security, and network requirements as possible. During this phase, a plan is developed
that documents the approach to be used and includes a discussion of methods, tools, tasks,
resources, project schedules, and user input. Personnel assignments, costs, project schedule, and
target dates are established.
A Project Management Plan is created with components related to acquisition planning,
configuration management planning, quality assurance planning, concept
of operations, system security, verification and validation, and systems engineering management
planning.

7|Page
REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements using high-level
requirements identified in the Initiation, System Concept, and Planning phases. It also delineates
the requirements in terms of data, system performance, security, and maintainability
requirements for the system. The requirements are defined in this phase to alevel of detail
sufficient for systems design to proceed. They need to be measurable, testable, and relate to the
business need or opportunity identified in the Initiation Phase. The requirements that will be used
to determine acceptance of the system are captured in the Test and Evaluation MasterPlan.

The purposes of this phase are to:

• Further define and refine the functional and data requirements and document them in
the Requirements Document,
• Complete business process reengineering of the functions to be supported (i.e., verify
what information drives the business process, what information is generated, who
generates it, where does the information go, and who processes it),
• Develop detailed data and process models (system inputs, outputs, and the process.
• Develop the test and evaluation requirements that will be used to determine
acceptable system performance.

8|Page
DESIGN PHASE

The design phase involves converting the informational, functional, and network
requirements identified during the initiation and planning phases into unified design
specifications that developers use to scriptprograms during the development phase. Program
designs are c onstructed in various ways. Using a top-down approach, designers first identify and
link majorprogram components and interfaces, then expand design layouts as they identify and
link smaller subsystems and connections. Using a bottom-up approach, designers first identify
and link minor program components and interfaces, then expand design layouts as they identify
and link larger systems and connections. Contemporary design techniques often use prototyping
tools that build mock-up designs of items such as application screens, database layouts, and
system architectures. End users, designers, developers, database managers, and network
administrators should review and refine the prototyped designs in an iterative process until they
agree on an acceptable design. Audit, security, and quality assurance personnel should be
involved in the review and approval process. During this phase, the system is designed to satisfy
the functional requirements identified in the previous phase. Since problems in the design phase
could be very expensive to solve in the later stage of the software development, a variety of
elements are considered in the design to mitigate risk. These include:

• Identifying potential risks and defining mitigating design features.

• Performing a security risk assessment.
• Developing a conversion plan to migrate current data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and outputs.
• Allocating processes to resources.
• Preparing detailed logic specifications for each software module. The result is a draft
System Design Document which captures the preliminary design for the system.
• Everything requiring user input or approval is documented and reviewed by the user.
Once these documents have been approved by the Agency CIO and Business Sponsor,
the final System Design Document is created to serve as the Critical/Detailed Design for
the system.

9|Page
 • This document receives a rigorous review byAgency technical and functional
representatives to ensure that it satisfies the business requirements. Concurrent with the
development of the system design, the Agency Project Manager begins development of
the Implementation Plan, Operations and Maintenance Manual, and the Training Plan.

DEVELOPMENT PHASE

The development phase involves converting design specifications into executable

programs. Effective development standards include requirements that programmers and other
project participants discuss design specifications before programming begins. The
procedures help ensure programmers clearly understand program designs and functional
requirements. Programmers use various techniques to develop computer programs. The large
transaction oriented programs associated with financial institutions have traditionally been
developed using procedural programming techniques. Procedural programming involves the
line-by-line scripting of logical instructions that are combined to form a program.Effective
completion of the previous stages is a key factor in the success of the Development phase.
The Development phase consists of:

• Translating the detailed requirements and design into system components.

• Testing individual elements (units) for usability.
• Preparing for integration and testing of the IT system.

10 | P a g e
INTEGRATION AND TEST PHASE

• Subsystem integration, system, security, and user acceptance testing is conducted during
the integration and test phase. The user, with those responsible for quality assurance,
validates that the functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. OIT Security staff assess
the system security and issue a security certification and accreditation prior to
installation/implementation.
Multiple levels of testing are performed, including:

• Testing at the development facility by the contractor and possibly supported by end users

• Testing as a deployed system with end users working together with contract
personnel

• Operational testing by the end user alone performing all functions. Requirements are
traced throughout testing,a final Independent Verification & Validation evaluation is
performed and all documentation is reviewedand accepted prior to acceptance of the
system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and accepted by the user. In this
phase, the system is installed to support the intended business functions. System performance is
compared to performance objectives established during the planning phase. Implementation
includes user notification, user training, installation of hardware, installation of software onto
production computers, and integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance with the defined
userrequirements.

11 | P a g e
OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for continued performance in
accordance with user requirements and needed system modifications are incorporated.
Operations continue as long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified, the system may reenter the
planning phase.
The purpose of this phase is to:

• Operate, maintain, and enhance the system.

• Certify that the system can process sensitive information.
• Conduct periodic assessments of the system to ensure the functional
requirements continue to be satisfied.
• Determine when the system needs to be modernized, replaced, or retired.

12 | P a g e
 SOURCE CODE

import os import

platform

import mysql.connector

import pandas as pd

mydb=mysql.connector.connect(host="localhost",user="root",

passwd="root",

database="cosmetics") mycursor=mydb.cursor()

def cosmeticsInsert(): l=[]

code=int(input("Enter the cosmetic ID number : ")) l.append(code)

name=input("Enter the Cosmetics Name: ")

l.append(name)

company=input("Enter company of Cosmetics : ")

l.append(company)

cost=int(input("Enter the Cost : ")) l.append(cost)

manudate=input("Enter the Date of Manufacture : ")

l.append(manudate)

expdate=input("Enter the Date of Expiry : ") l.append(expdate)

stud=(l)

13 | P a g e
 sql="insert into product(code,name,company,cost,manudate,expdate) values
(%s,%s,%s,%s,%s,%s)"

mycursor.execute(sql,stud)

mydb.commit()

def cosmeticsView():

print("Select the search criteria : ")

print("1. Roll")

print("2. Name")

print("3. All")

ch=int(input("Enter the choice : ")) if

ch==1:

s=int(input("Enter cosmetics ID : ")) rl=(s)

sql="select * from cosmetics where code=%s"

mycursor.execute(sql,rl)

elif ch==2:

s=input("Enter Cosmetics Name : ") rl=(s)

sql="select * from cosmetics where name=%s"

mycursor.execute(sql,rl)

elif ch==3:

sql="select * from cosmetics"

mycursor.execute(sql) res=mycursor.fetchall()

print("The Cosmetics Stock details are as follows : ")

print("(Cosmetics ID, Cosmetics Name, Cost, Date of Manufacture, Date of Expiry)")

14 | P a g e
 for x in res: print(x)

def viewCustomer():

print("Select the search criteria : ")

print("1. Customer ID")

print("2. Customer Name") print("3.

All")

ch=int(input("Enter the choice : ")) if

ch==1:

s=int(input("Enter customer ID : ")) rl=(s)

sql="select * from customer where cust_id=%s"

mycursor.execute(sql,rl)

elif ch==2:

s=input("Enter Cosmetics Name : ") rl=(s,)

sql="select * from customer where name=%s"

mycursor.execute(sql,rl)

elif ch==3:

sql="select * from customer"

mycursor.execute(sql) res=mycursor.fetchall()

print("The Cosmetics Stock details are as follows : ")

print("(Cosmetics ID, Cosmetics Name, Cost, Date of Manufacture, Date of Expiry)")

for x in res:

15 | P a g e
 print(x)

def CustomerPurchase():

print("Please enter the details to purchase cosmetics product :") sql="select * from

customer"

mycursor.execute(sql) res=mycursor.fetchall()

print("The Cosmetics Stock details are as follows : ")

print("(Cosmetics ID, Cosmetics Name, Cost, Date of Manufacture, Date of Expiry)")

for x in res:

print(x)

cost=0.0

LI=dict()

ch='y'

tsum=0.0

q1=0

cc=0.0

#while(ch=='y'):

c1=input("Enter the items to be purchased : ") r1=(c1,)

sql="Select cost from product where name=%s"

mycursor.execute(sql,r1) res=mycursor.fetchall()

for x in res:

cost=float(x[0]) print

(cost)

16 | P a g e
 q1=int(input("Enter the item quantity: "))

cc=q1*cost

print(cc)

tsum=tsum+cc

ch=input("Want to purchase more items:")

else:

L=[]

cid=int(input("Enter customer ID"))

L.append(cid)

cname=input("Enter customer name")

L.append(cname) phone_no=int(input("Enter

Phone no.")) L.append(phone_no)

add=input("Enter Address")

L.append(add) gender=input("Enter

your Gender") L.append(gender)

member=input("Enter membership")

L.append(member)

cosmme=(L)

sql="insert into customer

(cust_id,cname,c_phoneno,c_address,gender,membership)values (%s,%s,%s,%s,%s,%s)"

mycursor.execute(sql,cosmme) mydb.commit()

print("Record of customer saves...")

print("Total cost of item purchased is Rs.",tsum)

17 | P a g e
def removeCosmetics():

name=input("Enter the cosmetics name to be deleted : ") rl=(name)

sql="Delete from customer where name=%s"

mycursor.execute(sql,rl)

sql="Delete from customer where cname=%s"

mycursor.execute(sql,rl)

mydb.commit()

def MenuSet(): #Function For The Student Management System print("Enter 1 :

To Add cosmetics product")

print("Enter 2 : To View Complete Cosmetics Stock")

print("Enter 3 : To Purchase any cosmetics Product ")

print("Enter 4 : To Remove any Cosmetic product") print("Enter

5 : To View Customer Details")

try:

#Using Exceptions For Validation

userInput = int(input("Please Select An Above Option: ")) #Will Take Input From
User

except ValueError:

exit("\nHy! That's Not A Number") #Error Message

else:

print("\n") #Print New Line

if(userInput == 1):

cosmeticsInsert() elif

(userInput==2):

18 | P a g e
 cosmeticsView() elif

(userInput==3):

CustomerPurchase() elif

(userInput==4):

removeCosmetics() elif

(userInput==5):

viewCustomer() else:

print("Enter correct choice. . . ")

MenuSet()

def runAgain():

runAgn = input("\nwant To Run Again Y/n: ")

while(runAgn.lower() == 'y'):

if(platform.system() == "Windows"):

print(os.system('cls'))

else:

print(os.system('clear'))

MenuSet()

runAgn = input("\nwant To Run Again Y/n: ")

print("Good Bye")

runAgain()

19 | P a g e
DATABASE

20 | P a g e
OUTPUT SCREEN

21 | P a g e
22 | P a g e
 TESTING

Software Testing is an empirical investigation conducted to provide stakeholders with

information about the quality of the product or service under test[1] , with respect to the context
in which it is intended to operate. Software Testing also provides an objective, independent view
of the software to allow the business to appreciate and understand the risks at implementation of
the software. Test techniques include, but are not limited to, the process of executing a program
or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements that guided its
design and development, so that it works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method employed, can be
implemented at any time in the development process, however the most test effort is employed
after the requirements have been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing and white box
testing. These two approaches are used to describe the point of view that a test engineer takes
when designing test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary value
analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory
testing and specification-based testing.
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to the

applicable requirements.[16] Thus, the tester inputs data into, and only sees the output from, the
test object. This level of testing usually requires thorough test cases to be provided to the tester,
who then can simply verify that for a given input, the

23 | P a g e
output value (or behaviour), either "is" or "is not" the same as the expected value specified in the
test case. Specification-based testing is necessary, but it is insufficient to guard against certain
risks

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception is very simple:
a code must have bugs. Using the principle, "Ask and you shall receive," black box testers find
bugs where programmers don't. But, on the other hand, black box testing has been said to be
"like a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the
software being tested was actually constructed.
That's why there are situations when (1) a black box tester writes many test cases to check
something that can be tested by only one test case, and/or (2) some parts of the back end are not
tested at all. Therefore, black box testing has the advantage of "an unaffiliated opinion," on the
one hand, and the disadvantage of "blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has access to the
internal data structures and algorithms (and the code that implement these)

Types of white box testing:-

The following types of white box testing exist:
• api testing - Testing of the application using Public and Private APIs.
• Code coverage - creating tests to satisfy some criteria of code coverage.
For example, the test designer can create tests to cause all statements in the program to be
executed at least once.
• fault injection methods.
• mutation testing methods.
• static testing - White box testing includes all static testing.

24 | P a g e
 CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness of a test suite
that was created with black box testing methods. This allows the software team to examine parts
of a system that are rarely tested and ensures that the most important function points have been
tested.

Two common forms of code coverage are:

• Function Coverage: Which reports on functions executed and
• Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage

25 | P a g e
 HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS:

I. OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL CORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

• Windows OS
• Python
• mysql connector module

26 | P a g e
 BIBLIOGRAPHY

Acharya, Kamal. "STUDENT INFORMATION MANAGEMENT

SYSTEM." Authorea Preprints (2023).
Acharya, Kamal. "Library Management System." Available at SSRN4807104 (2019).
ACHARYA, KAMAL, et al. "LIBRARY MANAGEMENT SYSTEM." (2019).
Acharya, Kamal. "Online bus reservation system project report." Authorea
Preprints (2024).
Acharya, Kamal. "Online bus reservation system project report." (2024).
Acharya, Kamal. “Online Bus Reservation System.” SSRN ElectroNIC ASIA
Journal (2024): n. pag.
Acharya, Kamal. “Student Information Management System Project.” SSRN
ElectroNIC ASIA Journal (2024): n. pag.
Acharya, Kamal. “ATTENDANCE MANAGEMENT SYSTEM.” International
Research Journal of Modernization in Engineering Technology and
Science (2023): n. pag.

Acharya, Kamal. “College Information Management System.” SSRN ElectroNIC

ASIA Journal (2024): n. pag.
Acharya, Kamal, Attendance Management System Project (April 28, 2024).
Available at
SSRN: https://ssrn.com/abstract=4810251 or http://dx.doi.org/10.2139/ssrn.4810251
Acharya, Kamal, Online Food Order System (May 2, 2024). Available at
SSRN: https://ssrn.com/abstract=4814732 or http://dx.doi.org/10.2139/ssrn.4814732
Acharya, Kamal, University management system project. (May 1, 2024). Availableat
SSRN: https://ssrn.com/abstract=4814103 or http://dx.doi.org/10.2139/ssrn.4814103
Acharya, Kamal, Online banking management system. (May 1, 2024). Available at
SSRN: https://ssrn.com/abstract=4813597 or http://dx.doi.org/10.2139/ssrn.4813597
Acharya, Kamal, Online Job Portal Management System (May 5, 2024). Available at
SSRN: https://ssrn.com/abstract=4817534 or http://dx.doi.org/10.2139/ssrn.4817534
Acharya, Kamal, Employee leave management system. (May 7, 2024). Available
at SSRN: https://ssrn.com/abstract=4819626 or http://dx.doi.org/10.2139/ssrn.4819626
Acharya, Kamal, Online electricity billing project report. (May 7, 2024). Available at
SSRN: https://ssrn.com/abstract=4819630 or http://dx.doi.org/10.2139/ssrn.4819630
27 | P a g e
Acharya, Kamal, POLICY MANAGEMENT SYSTEM PROJECT REPORT. (December 10, 2023).
Available at SSRN: https://ssrn.com/abstract=4831694 or http://dx.doi.org/10.2139/ssrn.4831694
Acharya, Kamal, Online job placement system project report. (January 10, 2023). Available at
SSRN: https://ssrn.com/abstract=4831638 or http://dx.doi.org/10.2139/ssrn.4831638
Acharya, Kamal, Software testing for project report. (May 16, 2023). Available at
SSRN: https://ssrn.com/abstract=4831028 or http://dx.doi.org/10.2139/ssrn.4831028
Acharya, Kamal, ONLINE CRIME REPORTING SYSTEM PROJECT. (August 10, 2022). Available
at SSRN: https://ssrn.com/abstract=4831015 or http://dx.doi.org/10.2139/ssrn.4831015
Acharya, Kamal, Burber ordering system project report. (October 10, 2022). Available at
SSRN: https://ssrn.com/abstract=4832704 or http://dx.doi.org/10.2139/ssrn.4832704
Acharya, Kamal, Teachers Record Management System Project Report (December 10, 2023).
Available at SSRN: https://ssrn.com/abstract=4833821 or http://dx.doi.org/10.2139/ssrn.4833821
Acharya, Kamal, Dairy Management System Project Report (December 20, 2020). Available at
SSRN: https://ssrn.com/abstract=4835231 or http://dx.doi.org/10.2139/ssrn.4835231
Acharya, Kamal, Electrical Shop Management System Project (December 10, 2019). Available at
SSRN: https://ssrn.com/abstract=4835238 or http://dx.doi.org/10.2139/ssrn.4835238
Acharya, Kamal, Online book store management system project report. (Febuary 10, 2020). Available
at SSRN: https://ssrn.com/abstract=4835277 or http://dx.doi.org/10.2139/ssrn.4835277
Acharya, Kamal, Paint shop management system project report. (January 10, 2019). Available at
SSRN: https://ssrn.com/abstract=4835441 or http://dx.doi.org/10.2139/ssrn.4835441
Acharya, Kamal, Supermarket billing system project report. (August 10, 2021). Available at
SSRN: https://ssrn.com/abstract=4835474 or http://dx.doi.org/10.2139/ssrn.4835474
Acharya, Kamal, Online texi booking system project report. (March 10, 2022). Available at
SSRN: https://ssrn.com/abstract=4837729 or http://dx.doi.org/10.2139/ssrn.4837729
Acharya, Kamal, Online car servicing system project report. (March 10, 2023). Available at
SSRN: https://ssrn.com/abstract=4837832 or http://dx.doi.org/10.2139/ssrn.4837832
Acharya, Kamal, School management system project report. (July 10, 2021). Available at
SSRN: https://ssrn.com/abstract=4837837 or http://dx.doi.org/10.2139/ssrn.4837837
Acharya, Kamal, Furniture Showroom Management System Project Report (March 21, 2021).
Available at SSRN: https://ssrn.com/abstract=4839422 or http://dx.doi.org/10.2139/ssrn.4839422
Acharya, Kamal, Online Vehicle Rental System Project Report (March 21, 2019). Available at
SSRN: https://ssrn.com/abstract=4839429 or http://dx.doi.org/10.2139/ssrn.4839429
Acharya, Kamal, Fruit Shop Management System Project Report (August 10, 2023). Available at
SSRN: https://ssrn.com/abstract=4841048 or http://dx.doi.org/10.2139/ssrn.4841048
28 | P a g e
Acharya, Kamal, Hall Booking Management System Project Report (December 21, 2023). Available
at SSRN: https://ssrn.com/abstract=4841055 or http://dx.doi.org/10.2139/ssrn.4841055
Acharya, Kamal, Lundry Management System Project Report (October 21, 2023). Available at
SSRN: https://ssrn.com/abstract=4841059 or http://dx.doi.org/10.2139/ssrn.4841059
Acharya, Kamal, A CASE STUDY OF CINEMA MANAGEMENT SYSTEM PROJECT (September 25,
2023). Available at
SSRN: https://ssrn.com/abstract=4841209 or http://dx.doi.org/10.2139/ssrn.4841209
Acharya, Kamal, A CASE STUDY ON ONLINE TICKET BOOKING SYSTEM PROJECT (May 25,
2024). Available at
SSRN: https://ssrn.com/abstract=4841210 or http://dx.doi.org/10.2139/ssrn.4841210
Acharya, Kamal, ONLINE DATING MANAGEMENT SYSTEM PROJECT REPORT. (April 25, 2023).
Available at SSRN: https://ssrn.com/abstract=4842066 or http://dx.doi.org/10.2139/ssrn.4842066
Acharya, Kamal, ONLINE RESUME BUILDER MANAGEMENT SYSTEM PROJECT REPORT.
(April 25, 2021). Available at
SSRN: https://ssrn.com/abstract=4842071 or http://dx.doi.org/10.2139/ssrn.4842071
Acharya, Kamal, TOLL TEX MANAGEMENT SYSTEM PROJECT REPORT (August 21, 2023).
Available at SSRN: https://ssrn.com/abstract=4842082 or http://dx.doi.org/10.2139/ssrn.4842082
Acharya, Kamal, Chat Application Through Client Server Management System Project Report (June
25, 2023). Available at
SSRN: https://ssrn.com/abstract=4842761 or http://dx.doi.org/10.2139/ssrn.4842761
Acharya, Kamal, Web Chatting Application Management System Project Report (April 25, 2022).
Available at SSRN: https://ssrn.com/abstract=4842771 or http://dx.doi.org/10.2139/ssrn.4842771
Acharya, Kamal, Automobile management system project report (May 25, 2022). Available at
SSRN: https://ssrn.com/abstract=4846917 or http://dx.doi.org/10.2139/ssrn.4846917
Acharya, Kamal, College bus management system project report (April 25, 2023). Available at
SSRN: https://ssrn.com/abstract=4846920 or http://dx.doi.org/10.2139/ssrn.4846920
Acharya, Kamal, Courier management system project report (May 25, 2023). Available at
SSRN: https://ssrn.com/abstract=4846922 or http://dx.doi.org/10.2139/ssrn.4846922
Acharya, Kamal, Event management system project report (April 25, 2021). Available at
SSRN: https://ssrn.com/abstract=4846927 or http://dx.doi.org/10.2139/ssrn.4846927
Acharya, Kamal, Library management system project report II (May 25, 2020). Available at
SSRN: https://ssrn.com/abstract=4848857 or http://dx.doi.org/10.2139/ssrn.4848857

29 | P a g e