Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Project Paint Store

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 26

PAINT STORE MANAGEMENT SYSTEM

A Project Report Submitted to the Madurai Kamaraj University in

Partial Fulfillment for the Award of the Degree


BACHELOR OF COMPUTER APPLICATIONS

(2021 - 2024)

Submitted by STUDENT NAME


21BCAXX
Under the Guidance of
Guide Name, Degree.,

THE AMERICAN COLLEGE


An Autonomous Institution affiliated to Madurai Kamaraj University

(Re-accredited (3rd cycle) by NAAC with Grade “A+” CGPA-3.47 on a 4-points scale)

Madurai – 625002.
THE AMERICAN COLLEGE
DEPARTMENT OF COMPUTER APPLICATIONS
An Autonomous Institution affiliated to Madurai Kamaraj University

(Re-accredited (3rd cycle) by NAAC with Grade “A+” CGPA-3.47 on a 4-points scale)

Madurai – 625002

CERTIFICATE
This is to certify that this Project titled “PAINT STORE MANAGEMENT SYSTEM” is a
bonafide work done by Student Name (Roll.no) in Partial Fulfillment for the award of the
degree of Bachelor of Computer Applications of The American College, Madurai for the
year 2021-2024.

Guide name, Degree., Mrs. T. Suganya, M.Sc., M.Phil., SLET, (Ph.D)

Internal Guide Head of the Department

Submitted for the Viva-Voice examination held on

Internal Examiner External Examiner


DECLARATION

I hereby declare that this project was carried out by me under the guidance of
Guide name, Degree., Department of Computer Applications, The American College, Madurai.

I also declare that this project report is the result of my own effort and that it has not
been copied from any one and has not been submitted by anybody in anywhere.

Place: Madurai STUDENT NAME

Date: (ROLL.NO)
ACKNOWLEDGEMENT

I am pleased to convey my sincere thanks to our Principal Dr. M. Davamani Christober,


M.Sc., M.Phil., M.Ed., PGDCA, Ph.D.(Inter Disciplinary), Ph.D.(Math).

I am Grateful to the Head of our department Mrs. T. Suganya, M.Sc., M.Phil., SLET,
(Ph.D) for her energetic encouragement and support.

I express my deep sense of gratitude and indebtedness to Guide Name, Degree., his/her
inspiring guidance and continuous encouragement which has enabled me to complete this
project.

Also I would like to thank my Teachers, Friends and my well-wishers who have helped
me during the course of completion of this project.
Contents
S. NO. DESCRIPTION PAGE NO.
Abstract
System Analysis
1.1 Existing System
1
1.2 Proposed System
1.3 Feasibility Study
System Requirements Specification
2.1 Software Requirements
2
2.2 Hardware Requirements
2.3 About Software
System Design
3.1 Modules Description
3.2 Functional Requirements
3.2.1 System Diagram
3 3.2.2 Data Flow Diagrams
3.2.3 E-R Diagram
3.2.4 UML Diagrams
3.3 Database Design
3.4 User Interface Design
4 System Implementation
5 System Testing
6 System Maintenance
7 Conclusion
8 Future Enhancement
9 Bibliography
Appendix
10 10.1 Sample Screens
10.2 Source Code
INTRODUCTION
ABSTRACT

The Paint Management System is an advanced software solution designed to


streamline and enhance the management processes of paint stores. This system addresses the
complexities associated with inventory control, sales transactions and customer interactions
within the paint retail industry. By integrating automation and modern technology, the Paint
Management System aims to optimize operational efficiency, provide a seamless customer
experience, and empower paint store owners with valuable insights for strategic decision-
making. It also focuses on delivering a smooth and hassle-free experience for customers while
providing paint store owners with crucial insights. These enhancements would not only
improve operational efficiency but also elevate the overall customer experience, positioning
the paint store as owner in innovation within the industry.
SYSTEM
ANALYSIS
1. SYSTEM ANALYSIS

1.1 EXISTING SYSTEM

The existing Paint Store Billing System relies on traditional manual


methods, which often result in inefficiencies, errors, and delays.
In this system, store operations such as inventory management, sales
transactions, and billing are predominantly paper-based.
The manual nature of the process makes it challenging to maintain accurate
stock levels, track sales trends, and provide timely services to customers.
Additionally, the lack of integration leads to difficulties in managing
customer relationships and analyzing business performance.
The absence of a systematic approach hampers the overall efficiency and
growth potential of the paint store.
1.2 PROPOSED SYSTEM

The proposed Paint Store Billing System is a comprehensive software


solution designed to address the limitations of the existing system and
elevate the efficiency of store operations.
This system introduces automation and integration to streamline various
processes, ensuring a more accurate, transparent, and customer-centric
approach.
1.3 FEASIBILITY STUDY
The feasibility study for paint store management aims to assess the practicality and
viability of implementing a management system tailored to the needs of paint stores.
This study evaluates various factors such as technical feasibility, economic viability,
and operational feasibility to determine whether investing in such a system is justified

1.Technical Feasibility
2. Financial Feasibility
3. Operating Feasibility

Technical Feasibility:

Hardware Requirements: Evaluate the hardware infrastructure required to support the


management system, including servers, computers, and networking equipment.
Software Requirements: Assess the software components needed for the management system,
including operating systems, databases, and application software.
Compatibility: Ensure compatibility with existing hardware and software systems used in the
paint store.

Financial Feasibility:

Cost-Benefit Analysis: Conduct a cost-benefit analysis to compare the costs associated with
implementing the management system against the expected benefits, such as increased
efficiency, reduced errors, and improved customer service.
Return on Investment (ROI): Calculate the projected ROI over a specified period to determine
the financial viability of the project.
Budget Constraints: Consider budget constraints and explore cost-effective solutions to
minimize implementation costs.

Operational Feasibility:

User Requirements: Gather input from paint store staff to identify their requirements
and preferences for the management system.
Training Needs: Assess the training needs of employees to ensure they can effectively
use the management system.
Change Management: Evaluate the impact of implementing the management system on
existing processes and workflows, and develop strategies to manage resistance to change.

Based on the findings of the feasibility study, it is determined that implementing a


paint store management system is feasible. The technical requirements can be met with
existing hardware and software infrastructure, while the economic analysis indicates a positive
ROI within a reasonable timeframe. Additionally, the operational feasibility assessment
suggests that the system can be successfully integrated into the paint store's operations with
proper training and change management strategies in place. Therefore, it is recommended to
proceed with the implementation of the paint store management system to improve efficiency
and enhance customer satisfaction.
SYSTEM
REQUIREMENTS
SPECIFICATION
2. SYSTEM REQUIREMENTS SPECIFICATION

2.1 SOFTWARE REQUIREMENTS

Operating System : Windows 11


Language used : VB.NET
Data Base : MySQL
Web Server : XAMMP
Browser : Google Chrome

2.2 HARDWARE SPECIFICATION


FUTURE
ENHANCEMENT
7. FUTURE ENHANCEMENT

SYSTEM TESTING
Testing Process:
Software testing is a crucial element of software quality assurance and represents the
meticulous review of the specification, design, and coding. The user evaluates the developed
system, and adjustments are made according to their requirements. The testing phase involves
comprehensive testing of the developed system using various types of data.
System testing is the implementation stage aimed at ensuring that the system operates
accurately and efficiently before live operation commences. Testing is vital to the success of
the system. System testing operates on the logical assumption that if all parts of the system are
correct, the goal will be successfully achieved.
Testing Strategies:
• Unit Testing
• Integration Testing
• Validation Testing
• Output Testing
• User Acceptance Testing

Unit Testing:
Unit testing focuses verification efforts on the smallest unit of software design or module.
This is also known as module testing. The modules of the system are tested independently.
This testing is conducted during the programming stage itself. Validation of each text box and
button is included in this type of testing.
For example, we have tested whether the text box accepts only numbers or not. We checked
whether the home button works properly and navigates to the first page or not, etc.

Integration Testing:
Data loss can occur across an interface, a module can adversely affect another, and sub-
functions when combined may not produce the desired major function.
Integration testing is a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfaces. Proper integration ensures
correct functioning when several modules work together. Changes in one module should be
reflected in others and should not lead to errors when the different modules work together as a
whole.

Validation Testing:
At the culmination of integration testing, the software is considered as a package. Interface
errors have been uncovered and corrected, and the final series of software tests, i.e., validation
tests, begins.
Validation testing can be defined in many ways, but a simple definition is that validation
succeeds when the software functions in a manner reasonably expected by the customer.
We checked whether the entire system works correctly by combining all modules in the
system.
For example:
• We checked whether it navigates to the first, next, or a particular page correctly.
• We tested whether data are correctly stored in corresponding tables or not, etc.

Output Testing:
After performing validation testing, the next step is output testing of the proposed system, as
no system could be useful if it does not provide the required output in the specified format.
Here, the output format is considered in two ways: on-screen and printed format. The output
format is adjusted according to user needs.
For example, we checked whether the particulars, date, images, and text are printed in the
correct location or not by taking a hard copy. We tested whether the displayed page fits on one
page or not using the print preview command on the screen.

User Acceptance Testing:


User acceptance of a system is a key factor for the success of any system. The system is tested
for user acceptance by engaging with prospective system users during development and
making changes whenever necessary. The following are designed according to user needs:
• Menu-driven pages
• Alerts and confirmation boxes on input screens
• Output screens
BIBLIOGRAPHY

9. BIBLIOGRAPHY

Books:

1. "Pro ASP.NET Core MVC" by Adam Freeman


2. "ASP.NET Core in Action" by Andrew Lock
3. "Programming ASP.NET Core" by Dino Esposito
4. "ASP.NET Core Application Development: Building an application in four sprints" by James
Chambers, David Paquette, and Simon Timms
5. "Professional ASP.NET MVC 5" by Jon Galloway, Brad Wilson, K. Scott Allen, and David
Matson.

Websites and Online Resources:

1. Stack Overflow - stackoverflow.com (for community-driven problem solving and discussion)


2. ASP.NET Community - forums.asp.net (for discussions, Q&A, and support)
3. Pluralsight - pluralsight.com (for online courses and tutorials on ASP.NET development)
4. GitHub - github.com (for accessing open-source projects, samples, and contributions related
to ASP.NET development)
10. APPENDIX

10.1 SAMPLE USER INTERFACE SCREENS

Dashboard
Product Management Module

Product Entry Module


Receipt Module

Report Module
10.2 SOURCE CODE

Imports System.Data.SqlClient
Imports System.Data
Imports System.Net
Imports System.Windows.Forms.VisualStyles.VisualStyleElement

Public Class Login

Dim Conn As New SqlConnection("Your MySQL Connection String Here")


Dim dr As SqlDataReader

Private Sub Login_Load(sender As Object, e As EventArgs) Handles MyBase.Load


Panel_Login.BringToFront()
Panel_LoginBar.BackColor = Color.Yellow
TextBox5.UseSystemPasswordChar = True
TextBox5.UseSystemPasswordChar = True
TextBox6.UseSystemPasswordChar = True
TextBox1.Focus()
TextBox1.Select()
End Sub

Private Sub Clear()


TextBox4.Text = ""
TextBox3.Text = ""
TextBox6.Text = ""
TextBox5.Text = ""
End Sub

Private Sub Button_Register_Click(sender As Object, e As EventArgs) Handles


Button_Register.Click
If TextBox4.Text = "" Then
MessageBox.Show("Please enter username")
ElseIf TextBox3.Text = "" Then
MessageBox.Show("Please enter Email")
ElseIf TextBox6.Text = "" Then
MessageBox.Show("Please enter Password")
ElseIf TextBox5.Text = "" Then
MessageBox.Show("Please enter Confirm_password")
Else
If Conn.State = ConnectionState.Closed Then
Conn.Open()
End If
Dim cmd As New SqlCommand("insert into Register Values ('" & TextBox4.Text &
"','" & TextBox5.Text & "','" & TextBox3.Text & "' )", Conn)
Try
cmd.ExecuteNonQuery()
Conn.Close()
MsgBox("Register Successfully")
Clear()
Catch ex As Exception
MsgBox(ex.Message)
End Try
End If

End Sub

Private Sub TextBox5_ChangeUICues(sender As Object, e As UICuesEventArgs) Handles


TextBox5.ChangeUICues
If TextBox5.Text.Equals(TextBox6.Text) Then
Else
' Values are different
MessageBox.Show("Values are different")
End If
End Sub

Private Sub PictureBox_Close_Click(sender As Object, e As EventArgs) Handles


PictureBox_Close.Click
Me.Close()
End Sub

Private Sub ButtonGoToRegister_Click(sender As Object, e As EventArgs) Handles


ButtonGoToRegister.Click
Panel_Login.Hide()
Panel_Register.Show()
Panel_Register.BringToFront()
ButtonGoToRegister.BackColor = Color.FromArgb(34, 167, 240)
ButtonGoToRegister.Font = New Font("Microsoft Sans Serif", 28)
ButtonGoToRegister.ForeColor = Color.White
Panel_RegisterBar.BackColor = Color.Yellow

ButtonGoToLogin.BackColor = Color.White
ButtonGoToLogin.ForeColor = Color.Black
ButtonGoToLogin.Font = New Font("Microsoft Sans Serif", 20)
Panel_LoginBar.BackColor = Color.FromArgb(34, 167, 240)
End Sub

Private Sub ButtonGoToLogin_Click(sender As Object, e As EventArgs) Handles


ButtonGoToLogin.Click
Panel_Login.Show()
Panel_Login.BringToFront()
ButtonGoToLogin.BackColor = Color.FromArgb(34, 167, 240)
ButtonGoToLogin.Font = New Font("Microsoft Sans Serif", 28)
ButtonGoToLogin.ForeColor = Color.White
Panel_LoginBar.BackColor = Color.Yellow

ButtonGoToRegister.BackColor = Color.White
ButtonGoToRegister.ForeColor = Color.Black
ButtonGoToRegister.Font = New Font("Microsoft Sans Serif", 20)
Panel_RegisterBar.BackColor = Color.FromArgb(34, 167, 240)
End Sub

Private Sub Login_button_Click_1(sender As Object, e As EventArgs) Handles


Login_button.Click
If TextBox1.Text = "" Then
MessageBox.Show("Please enter username")
TextBox1.Focus()
Exit Sub
ElseIf TextBox2.Text = "" Then
MessageBox.Show("Please enter password")
TextBox2.Focus()
Exit Sub
Else
' If TextBox1.Text = "admin" And TextBox2.Text = "admin" Then
'MsgBox("Log in Successfully!", MsgBoxStyle.OkOnly, "Log in Form")
' Form1.Show()
' Me.Hide()
'Else
' MsgBox("Sorry Incorrect Username and Password", MsgBoxStyle.OkOnly,
"Invalid")
' End If

If Conn.State = ConnectionState.Closed Then


Conn.Open()
End If
Dim cmd As New SqlCommand("select Count(*) From Register where username=?
and password=?", Conn)
cmd.Parameters.AddWithValue("@1", SqlDbType.VarChar).Value = TextBox1.Text
cmd.Parameters.AddWithValue("@2", SqlDbType.VarChar).Value = TextBox2.Text
Dim Count = Convert.ToInt32(cmd.ExecuteScalar)
If (Count > 0) Then
' MsgBox("Login Success")
Brand.Show()
Me.Hide()
Else
MsgBox("Sorry Incorrect Username and Password", MsgBoxStyle.OkOnly,
"Invalid")
End If
'ElseIf
'MsgBox("Sorry Incorrect Username and Password", MsgBoxStyle.OkOnly,
"Invalid")
'End If

End If
End Sub
Private Sub TextBox2_KeyDown(sender As Object, e As KeyEventArgs) Handles
TextBox2.KeyDown
If e.KeyCode = Keys.Enter Then
Login_button_Click_1(Nothing, Nothing)
Else
Exit Sub
End If
e.SuppressKeyPress = True
End Sub
End Class

If DataGridView1.Rows.Count = 0 Then
MsgBox("Please load Items to Print.", MsgBoxStyle.Exclamation, "Report")
Exit Sub
End If
private void btnSearch_Click(object sender, EventArgs e)
{
string searchTerm = txtSearch.Text.Trim();

if (!string.IsNullOrEmpty(searchTerm))
{
SearchItems(searchTerm);
}
}

private void SearchItems(string searchTerm)


{
try
{
connection.Open();

string query = "SELECT ItemName FROM YourTableName WHERE ItemName LIKE


@searchTerm";
OleDbCommand command = new OleDbCommand(query, connection);
command.Parameters.AddWithValue("@searchTerm", "%" + searchTerm + "%");

OleDbDataReader reader = command.ExecuteReader();

listBoxResults.Items.Clear();

while (reader.Read())
{
listBoxResults.Items.Add(reader["ItemName"].ToString());
}
}
catch (Exception ex)
{
MessageBox.Show("Error: " + ex.Message);
}
finally
{
connection.Close();
}
}

Private Sub ComboBox2_SelectedIndexChanged(sender As Object, e As EventArgs) Handles


ComboBox2.SelectedIndexChanged
Try
Using connection As New SqlConnection("Your_Connection_String_Here")
connection.Open()

Dim query As String = "SELECT * FROM product_price WHERE product =


@Product"
Using command As New SqlCommand(query, connection)
command.Parameters.AddWithValue("@Product", Trim(ComboBox2.Text))

Dim reader As SqlDataReader = command.ExecuteReader()

If reader.HasRows Then
reader.Read()
Me.ComboBox1.Text = reader("Code").ToString()
Me.TextBox4.Text = reader(Me.Client_type.Text).ToString()
End If

reader.Close()
End Using
End Using
Catch ex As Exception
MsgBox(ex.Message)
End Try
End Sub

private void Print()

' Create a PrintDocument instance


Dim printDocument As New PrintDocument()

' Show PrintDialog to select printer and basic print settings


Dim printDialog As New PrintDialog()
printDialog.Document = printDocument
If printDialog.ShowDialog() = DialogResult.OK Then
' Configure page settings using PageSetupDialog
Dim pageSetupDialog As New PageSetupDialog()
pageSetupDialog.Document = printDocument
If pageSetupDialog.ShowDialog() = DialogResult.OK Then
' Print the document
printDocument.Print()
End If
End If
End Sub

You might also like