21BIT044_DOCUMENTATION (1).docx

Mobile Application for Daily Sales Management
MINOR PROJECT REPORT
Submitted by
Syed Aneesh S
21BIT044
Under the Guidance of
Mrs R Sathya MCA MPhil NET (PhD)
Assistant Professor
Department of Information Technology
In partial fulfillment of the requirements for the award of the degree of
BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY
of Bharathiar University
DEPARTMENT OF INFORMATION TECHNOLOGY
PSG COLLEGE OF ARTS & SCIENCE
An Autonomous College-Affiliated to Bharathiar University
Accredited with ‘A++
’ grade by NAAC (4th
Cycle)
College with Potential for Excellence
(Status Awarded by the UGC)
Star College Status Awarded by DBT - MST
An ISO 9001:2015 Certified Institution
Coimbatore -641 014
DECEMBER 2023

i
DEPARTMENT OF INFORMATION TECHNOLOGY
Accredited with A++
grade by NAAC (4th
Cycle)
Civil Aerodrome Post
Coimbatore -641 014
CERTIFICATE
This is to certify that this Project work entitled “Mobile Application for Daily Sales
Management” is a bonafide record of work done by Syed Aneesh S (21BIT044) in partial
fulfillment of the requirements for the award of Degree of Bachelor of Science in
Information Technology of Bharathiar University.
Faculty Guide Head of the Department
Submitted for Viva-Voce Examination held on ____________________
Internal Examiner External Examiner

ii
DECLARATION
I Syed Aneesh S 21BIT044 hereby declare that this Project work entitled “Mobile
Application for Daily Sales Management” is submitted to PSG College of Arts & Science
(Autonomous), Coimbatore in partial fulfillment for the award of Bachelor of Science in
Information Technology, is a record of original work done by me under the supervision and
guidance of Mrs R Sathya Assistant Professor, Department of Information Technology,
PSG College of Arts & Science, Coimbatore.
This Project work has not been submitted by me for the award of any other Degree/
Diploma/ Associate ship/ Fellowship or any other similar degree to any other university.
PLACE : Coimbatore Syed Aneesh S
DATE : 21BIT044

iii
ACKNOWLEDGEMENT
My venture stands imperfect without dedicating my gratitude to a few people
who have contributed a lot towards the victorious completion for my project work.
I would like to thank Mr Gopalakrishnan L Managing Trustee PSG & Sons
Charities for providing me with a prospect and surroundings that made the work possible.
I take this opportunity to express my deep sense of gratitude to
Dr Kannaian T Secretary of PSG College of Arts & Science, Coimbatore for permitting
and doing the needful towards the successful completion of this project.
I express my deep sense of gratitude and sincere thanks to our Principal
Dr Brindha D MSc MPhil PhD MA (Yoga) for her valuable advice and concern on
students.
I am very thankful to Dr Anguraj A MSc MPhil PhD Vice Principal,
Dr Umarani M MCom MPhil Vice Principal (Student Affairs) for their support.
I kindly and sincerely thank Dr Rajdeepa B MCA MPhil PhD Associate Professor
and Head of the Department of Information Technology for her whole hearted help to
complete this project successfully by giving valuable suggestions.
I convey my heartiest and passionate sense of thankfulness to my project guide
Mrs R Sathya, MCA, MPhil, NET (PhD) Assistant Professor, Department of Information
Technology for her timely suggestion which has enabled me to complete the project
successfully.
This note of acknowledgement will be incomplete without paying my heartfelt
devotion to my parents, my friends and other people, for their blessings, encouragement,
financial support and the patience, without which it would have been impossible for me to
complete the job.

iv
Accredited with A++
grade by NAAC (4th
Cycle)
Civil Aerodrome Post
Coimbatore -641 014
CERTIFICATE
This is to certify that this project work entitled “Mobile Application for Daily Sales
Management ” is submitted to PSG College of Arts & Science (Autonomous) ,Coimbatore,
Affiliated to Bharathiar University in partial fulfillment for the award of Bachelor of Science
in Information Technology, is record of original work done by Syed Aneesh S (21BIT044)
during June 2023 to December 2023 of his study in the Department of Information
Technology, PSG College of Arts & Science affiliated to Bharathiar University under my
supervision and guidance. This project work has not formed the basis for the award of any
other Degree / Diploma / Associate ship / Fellowship or any other similar degree to any other
University.
Signature of the Guide Signature of the HOD
Mrs R Sathya Dr Rajdeepa B
Assistant Professor Associate Professor and Head
Department of Information Technology Department of Information Technology
PSG College of Arts & Science PSG College of Arts & Science
Coimbatore Coimbatore

v
SYNOPSIS
The Main motive of this project is to create portable and easy application for sales.
This application will enable us to sale products and manage inventory from anywhere. In
general, mobile apps are far more user friendly than desktop, as the interface has been
specifically designed with mobile users in mind. Mobile apps offer a simple layout, clear
visuals and even tutorials for first-time user. All of which make using them that much easier.
So, 84% of people prefer mobile apps over desktop management.
In this application Sales, Purchase, Payment, Stock, Receipt, Employee can be
maintained in a single platform. Thus it helps the Manager or Owner to manage all the
essential details easily with a minimum amount of knowledge about the application. The man
power is reduced so it is a profit to the company and the profit can be indulged in company
growth. Application was developed using Android Studio and SQLite Data Base.

vi
TABLE OF CONTENTS
CONTENTS PAGE NO.
1. INTRODUCTION
1.1. Project Overview 1
1.2 Module Description 2
2. SYSTEM SPECIFICATIONS
2.1. Hardware Configurations 4
2.2. Software Specifications 4
2.3. Software Description 5
3. SYSTEM ANALYSIS
3.1 Existing System 11
3.2 Proposed System 11
4. SYSTEM DESIGN
4.1. ER Diagram 12
4.2. Data Flow Diagram 14
4.3. Database Diagram 17
4.4. Input Design 20
4.5. Output Design 21
5. SYSTEM TESTING & IMPLEMENTATION 22
6. CONCLUSION 24
7. SCOPE FOR FUTURE ENHANCEMENTS 25
8. BIBLIOGRAPHY 26
9. APPENDICES
A. Sample Coding 27
B. Screenshots 33

21BIT044 Daily Sales Management
Page 1 of 35
1. INTRODUCTION
Organizations today are realizing how mobile apps can help amplify reach and multiply their
customer base in the digital era. With almost everyone using a smartphone to access a variety of applications
– it has most certainly given a huge boost to the eCommerce business.
Android OS today commands a sizable share of the mobile app development market. With over 2.5 billion
active users spread across the world – the number is constantly growing. What makes it significant as the
preferred platform for companies are compelling advantages like massive customer reach, seamless
customization, faster deployment, improved scalability & much more.
However, there’s a lot to consider when giving your brand a digital boost in the mobile world. Through this
blog, we will explore the benefits of developing apps using Android and help you discover ways in which
you can stay competitive and relevant in the current times.
1.1 PROJECT OVERVIEW
The Main motive of this project is to create portable and easy application for sales. This
application will enable us to sale products and manage inventory from anywhere. In general, mobile apps
are far more user friendly than desktop, as the interface has been specifically designed with mobile users in
mind. Mobile apps offer a simple layout, clear visuals and even tutorials for first-time user. All of which
make using them that much easier. So, 84% of people prefer mobile apps over desktop management.
In this application Sales, Purchase, Payment, Stock, Receipt, Employee can be maintained in a single
platform. Thus it helps the Manager or Owner to manage all the essential details easily with a minimum
amount of knowledge about the application. The man power is reduced so it is a profit to the company and
the profit can be indulged in company growth. Application was developed using Android Studio and SQLite
Data Base.

Page 2 of 35
1.2 MODULE DESCRIPTION
Purchase
This module helps us to add the purchased product to the stock. The payment can be added and payment
balance can be added if any.
• Purchased product, Quantity, Payment amount, Payment Balance.
Sales
This module helps us to deduced the product from the stock and add the receipt.
• Sale product, Quantity, Payment Mode, Amount
Receipt
This module displays all the sales details with Date, Amount and Mode of Payment.
Stock
This module displays the current stock of the Products with Product Name and Quantity.
Payment
In this module, can view all the balance payment and clear if payment is done. Once payment is done it’s
stored in ledger.
• Product ID, Pay Amount.
Ledger
In this module, can view all the sales and purchase details of products with Product ID, Product Name,
Payment Mode, and Amount.

Page 3 of 35
Employee Details
In this module, employees are registered.
• Employee ID, Employee Name, Phone.
Employee Attendance
In this module, Employee are marked attendance based on their Employee ID. An Employee can also be
deleted in this module using the Employee ID.
 Employee ID

Page 4 of 35
2. SYSTEM SPECIFICATION
2.1 HARDWARE CONFIGURATION
 RAM : 2.00 GB
 PROCESSOR : Intel Pentium dual core,1.3GHz
 OPERATING SYSTEM :Windows 8.1 & Above
2.2 SOFTWARE SPECIFICATION
 FRONTEND : JAVA,XML(ANDROID STUDIO)
 BACKEND : SQLite

Page 5 of 35
2.3 SOFTWARE DESCRIPTION
2.3.1 FRONTEND
Android Studio is the official Integrated Development Environment (IDE) for android application
development. Android Studio provides more features that enhance our productivity while building Android
apps.
Android Studio was announced on 16th May 2013 at the Google I/O conference as an official IDE for
Android app development. It started its early access preview from version 0.1 in May 2013. The first stable
built version was released in December 2014, starts from version 1.0.
Since 7th May 2019, Kotlin is Google's preferred language for Android application development. Besides
this, other programming languages are supported by Android Studio.

Page 6 of 35
Features of Android Studio
o It has a flexible Gradle-based build system.
o It has a fast and feature-rich emulator for app testing.
o Android Studio has a consolidated environment where we can develop for all Android devices.
o Apply changes to the resource code of our running app without restarting the app.
o Android Studio provides extensive testing tools and frameworks.
o It supports C++ and NDK.
o It provides build-in supports for Google Cloud Platform. It makes it easy to integrate Google Cloud
Messaging and App Engine.
Android Studio Project Structure
The Android Studio project contains one or more modules with resource files and source code files. These
include different types of modules-
o Android app modules
o Library modules
o Google App Engine modules

Page 7 of 35
By default, Android Studio displays our project files in the Android project view, as shown in the above
image. This view is formed by modules to provide quick access to our project's key source files.
These build files are visible to the top-level under Gradle Scripts. And the app module contains the following
folders:
o manifests: It contains the AndroidManifest.xml file.
o java: It contains the source code of Java files, including the JUnit test code.
o res: It contains all non-code resources, UI strings, XML layouts, and bitmap images.
We will see the actual file structure of the project by selecting the Project from the Project dropdown.
Android Studio User Interface
The Android Studio main window contains the several logical areas which are shown in the below figure:

Page 8 of 35
1. The toolbar provides us a wide range of actions, which includes running apps and launching Android
tools.
2. The navigation bar helps in navigating our project and open files for editing. It gives a compact
view of structure visible in the Project window.
3. The editor window is a space where we can create and modify our code. On the basis of the current
file type, the editor can change. While viewing a layout file, the editor displays the Layout Editor.
4. The tool window bar runs around the outside the IDE window and contains buttons that allow as to
expand and collapse individual tool windows.
5. The tool windows provide us access specific tasks like search, project management, version control,
and more. We can able expand and collapse them.
6. The status bar displays the status of our project and IDE itself, as well as any messages or warnings.
We are willing to organize the main window to give ourselves more screen space by moving or hiding
toolbars and tool windows. We can also use keyboard shortcuts to access most of the IDE features.
Gradle build system
Gradle build used as the foundation of the build system in Android Studio. It uses more Android-specific
capabilities provided by the Android plugin for Gradle. This build system runs independently from the
command line and integrated tool from the Android Studio menu. We can use build features for the following
purpose:
o Configure, customize, and extend the build process.
o We can create multiple APKs from our app, with different features using the same project and
modules.
o Reuse resource and code across source sets.

Page 9 of 35
2.3.2 BACKEND
SQLiteDatabase
SQLite is a freely available open source database provided in Android. SQLite is a lightweight and compact
database that does not require any kind of server to run. It is easily integrated into any kind of mobile
application. There are many libraries and classes available on Android to perform any kind of database queue
on SQLite. It provides so many commands like add new data, update, read, and delete data.
SQLITEOPENHELPER CLASS:
We can use this class for creating a database and also we can use it for version management. This class
provides the onCreate() and onUpgrade() methods for performing any database operation.
Constructors of SQLiteOpenHelper Class:-
SQLiteOpenHelper class has two constructors.
1. SQLiteOpenHelper(Context context, String name, SQLiteDatabase.CursorFactory factory, int
version): This constructor creates an object for creating, opening, and managing the database.
2. SQLiteOpenHelper(Context context, String name,SQLiteDatabase.CursorFactory factory, int
version,DatabaseErrorHandler errorHandler): This constructor creates an object for creating, opening, and
managing the database. It specifies the error handler.

Page 10 of 35
Methods of SQLiteOpenHelper class:
SQLiteOpenHelper class has many methods. Some of them are as follows:
1. public abstract void onCreate(SQLiteDatabase db): This method is called only when you create a database
for the first time.
2. public abstract void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion): This method is
called when the database needs to be upgraded.
3. public synchronized void close(): This method closes the database object.
SQLITE DATABASE CLASS:
We have different methods in this class which are used to perform some commands on SQLite databases
such as create, update, delete, select, etc.
Methods of SQLiteDatabase class:
SQLite database class has many methods. Some of them are as follows:
1. void execSQL(String sql): This method executes a SQL query that is NOT a SELECT query.
2. long insert(String table, String nullColumnHack, ContentValues values): This method inserts a record on
the database.
3. int update(String table,ContentValues values,String whereClause, String[]whereArgs): This method is
used for updating a row.

Page 11 of 35
3. SYSTEM ANALYSIS
3.1 EXISTING SYSTEM – DISADVANTAGES
 Not easily portable must setup a particular place.
 Accessibility of data cannot be from remote locations.
 Data protection and availability is not effective during disasters.
3.2 PROPOSED SYSTEM – ADVANTAGES
 Easily portable
 Can manage data from remote locations
 Easy to maintain data and data protection is very high.

Page 12 of 35
4.SYSTEM DESIGN
4.1ER DIAGRAM
ER model stands for an Entity-Relationship model. It is a high-level data model. This model is
used to define the data elements and relationship for a specified system. It develops a conceptual
design for the database. It also develops a very simple and easy to design view of data. In ER
modeling, the database structure is portrayed as a diagram called an entity-relationship diagram.
Entity relationship diagrams provide a visual starting point for database design that can also be
used to help determine information system requirements throughout an organization. After
a relational database is rolled out, an ERD can still serve as a reference point, should any
debugging or business process re-engineeringbe needed later.
However, while an ERD can be useful for organizing data that can be represented by a relational
structure, it can't sufficiently represent semi-structured or unstructured data. It's also unlikely to
be helpful on its own in integrating data into a pre-existing information system.

Page 13 of 35
Fig: ER Diagram for Daily Sales Management

Page 14 of 35
4.2 DATA FLOW DIAGRAM
A data-flow diagram is a way of representing a flow of data through a process or a system
(usually an information system). The DFD also provides information about the outputs and
inputs of each entity and the process itself. A data-flow diagram has no control flow — there are
no decision rules and no loops. Specific operations based on the data can be represented by
a flowchart.
There are several notations for displaying data-flow diagrams. The notation presented above was
described in 1979 by Tom DeMarco as part of structured analysis.
For each data flow, at least one of the endpoints (source and / or destination) must exist in a
process. The refined representation of a process can be done in another data-flow diagram, which
subdivides this process into sub-processes.
The data-flow diagram is a tool that is part of structured analysis and data modeling. When using
UML, the activity diagram typically takes over the role of the data-flow diagram. A special form
of data-flow plan is a site-orienteddata-flowplan.
Data-flow diagrams can be regarded as inverted Petri nets, because places in such networks
correspond to the semantics of data memories. Analogously, the semantics of transitions from
Petri nets and data flows and functions from data-flow diagrams should be considered
equivalent.

Page 15 of 35
Level 0
Fig: Level 0 Data flow diagram for Daily Sales Management

Page 16 of 35
Level 1
Fig : Level 1 Data flow diagram for Daily Sales Management

Page 17 of 35
4.3 DATABASE DESIGN
4.3.1 PURCHASE
TABLE NAME : Purchase
TABLE DESCRIPTION : Table to store purchase details.
PRIMARY KEY : Product_ID
4.3.2 RECEIPT DETAILS
TABLE NAME : Receipt_Details
TABLE DESCRIPTION : Table to store sales details.
PRIMARY KEY : Sale_ID

Page 18 of 35
4.3.3 PAYMENT
TABLE NAME : Payment
TABLE DESCRIPTION : Table to store payment details and payment balance to the vendor.
FOREIGN KEY : Product_ID
4.3.4 STOCK
TABLE NAME : Stock
TABLE DESCRIPTION : Table to store purchase products and reduce the sale product , gives
report
FOREIGN KEY : Product_ID

Page 19 of 35
4.3.5 EMPLOYEE DETAILS
TABLE NAME : Employee_Details
TABLE DESCRIPTION : Table to store employee details .
PRIMARY KEY : Employee_ID
4.3.6 EMPLOYEE ATTENDANCE
TABLE NAME : Employee_Attendance
TABLE DESCRIPTION : Table to store attendance.
FOREIGN KEY : Employee_ID

Page 20 of 35
4.4 INPUT DESIGN
This design is input form design of Daily Sales Management.
Fig : Purchase Details are Entered
Fig: Sales Details are Entered

Page 21 of 35
4.5OUTPUT DESIGN
This design is output form design of Hotel Waste and Donation Management.
Fig : Stock Details are shown
Fig : Receipt Details are shown

Page 22 of 35
5.SYSTEM TESTING AND IMPLEMENTATION
5.1 Functionality Testing
Functionality testing is a process that includes several testing parameters like user interface,
APIs, database testing, security testing, client and server testing and basic website
functionalities. Functional testing is very convenient and it allows users to perform both
manual and automated testing. It is performed to test the functionalities of each feature on
the website.
Test Forms are working as expected. This will include-
 Forms are optimally formatted for better readability.
 Scripting checks on the form are working as expected.
 Check default values are being populated
 Once submitted, the data in the forms is submitted to a live database or is linked to a
working email address.
5.2 Usability Testing
Unit Testing has now become a vital part of any project. It can be carried out bytesters like you
or a small focus group similar to the target audience of the application.
Test the site Navigation
Menus, buttons or Links to different pages on your site should be easily visible and
consistenton all webpages. Content should be legible with no spelling or grammatical errors.
5.3 Interface Testing
Three areas to be tested here are – Application, Mobile and Database
 Application: Test requests are sent correctly to the Database and output at the client side
is displayed correctly. Errors if any must be caught by the application and must be only
shown to the administrator and not the end user.

Page 23 of 35
 Server: Test server is handling all application requests without any service denial.
 Database: Make sure queries sent to the database give expected results.
5.4 Database Testing
Database is one critical component of application and stress must be laid to test itthoroughly. Testing
activities will include-
 Test if any errors are shown while executing queries
 Data Integrity is maintained while creating, updating or deleting data in database.
 Check response time of queries and fine tune them if necessary.
 Test data retrieved from your database is shown accurately in your web application.
5.5 Security Testing
Security Testing is vital for e-commerce website that store sensitive customer information likecredit
cards. Test unauthorized access to secure pages should not be permitted
Fig: Authenticating User

Page 24 of 35
6.CONCLUSION
The Implementation of this project in Real world could provide immense help to the company.
It reduces labor cost that provides profit to company. Every data are stored in a centralized
database so retrieval of data is easy and maintain doesn’t conflict. If any changes in Business
logic the data can be added to the existing database rather than using exactly different
application. Data are protected and can be backup anytime by the company if database is
overloaded. Android Studio provides a feature of downloading Data as excel, therefore backup
will be effective.

Page 25 of 35
7.SCOPE FOR FUTURE ENHANCEMENTS
In the future this project of application can be developed as an Android application that
incorporate Artificial Intelligence with it. It can be used to take attendance with their face
recognition. AI can also be used to add stock by just scanning the products using Machine
Learning and grouping it.

Page 26 of 35
8.BIBLIOGRAPHY
BOOKS REFERRED
1. Author Michael Burton – “Android App Development For Dummies”, Third Edition
– John Wiley, March 2015.
2. Author Pradeep Kothari– “Android Application Development Black book”, Second
Edition – John Wiley, 11 June 2014.
3. Author Adam Stroud – “Android Database best practices” , First Edition – Addison
Wesley, 20 June 2019.
WEBSITE REFERRED
 https://www.topcoder.com/thrive/articles/sqlite-database-in-android
 https://www.javatpoint.com/android-studio
 https://www.tutorialspoint.com/software_testing_dictionary/web_application_
testing.htm

Page 27 of 35
9. APPENDICES
A.SAMPLE CODING
Database Coding
package com.example.myapplication;
import android.content.Context;
import android.database.sqlite.SQLiteDatabase;
import android.database.sqlite.SQLiteOpenHelper;
public class DatabaseHelper extends SQLiteOpenHelper {
private static final String DATABASE_NAME = "inventory.db";
private static final int DATABASE_VERSION = 1;
public DatabaseHelper(Context context) {
super(context, DATABASE_NAME, null, DATABASE_VERSION);
}
@Override
public void onCreate(SQLiteDatabase db) {
// Create Purchase table
db.execSQL("CREATE TABLE Purchase (Product_ID INTEGER PRIMARY KEY
AUTOINCREMENT, Product_Name TEXT, Quantjty INTEGER, Payment_Mode TEXT, Amount REAL,
Date TEXT)");
// Create Payment table
db.execSQL("CREATE TABLE Payment (Payment_ID INTEGER PRIMARY KEY
AUTOINCREMENT, Balance REAL, Date TEXT, Purchase_ID INTEGER, FOREIGN KEY
(Purchase_ID) REFERENCES Purchase (Product_ID))");
// Create Stock table
db.execSQL("CREATE TABLE Stock (Stock_ID INTEGER PRIMARY KEY
AUTOINCREMENT, Product_Name TEXT, Quantity INTEGER)");
// Create Sale table
db.execSQL("CREATE TABLE Receipt_Details (Sales_ID INTEGER PRIMARY KEY
AUTOINCREMENT, Product_Name TEXT, Quantity INTEGER,Payment_Mode TEXT,Amount
REAL,DATE TEXT)");
db.execSQL("CREATE TABLE Employee_details (Employee_ID INTEGER PRIMARY KEY
AUTOINCREMENT, Employee_Name TEXT,Employee_Phone TEXT)");
db.execSQL("CREATE TABLE Employee_Attendance (Employee_ID INTEGER PRIMARY KEY
AUTOINCREMENT,Employee_Name TEXT, Attendance TEXT,Date TEXT)");
}

Page 28 of 35
@Override
public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
// Handle database upgrades if needed
}
}
Android Manifests Coding
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools">
<application
android:allowBackup="true"
android:dataExtractionRules="@xml/data_extraction_rules"
android:fullBackupContent="@xml/backup_rules"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:roundIcon="@mipmap/ic_launcher_madhani_foreground"
android:supportsRtl="true"
android:theme="@style/Theme.MyApplication"
tools:targetApi="31">
<activity
android:name=".attendanceview"
android:exported="false" />
<activity
android:name=".attendance"
android:exported="true">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
</intent-filter>
</activity>
<activity
android:name=".employee"
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".receipt"
<intent-filter>
</intent-filter>

Page 29 of 35
</activity>
<activity
android:name=".payment"
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".stock"
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".ledger"
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".sales"
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".purchase"
android:exported="true"
android:label="purchase">
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".firstpage"
android:label="firstpage">
<intent-filter>
</intent-filter>
</activity>
<activity
android:name=".MainActivity"
android:exported="false" />

Page 30 of 35
<activity
android:name=".loginmain"
android:label="Madhani Mobiles"
android:theme="@style/Theme.MyApplication">
<intent-filter>
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
Redirect Coding
package com.example.myapplication;
import androidx.appcompat.app.AppCompatActivity;
import android.content.Intent;
import android.os.Bundle;
import android.view.View;
import android.widget.Button;
import android.widget.ImageButton;
public class firstpage extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_firstpage);
ImageButton purchaseButton = findViewById(R.id.purchaseButton);
purchaseButton.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
Intent intent = new Intent(firstpage.this, purchase.class);
startActivity(intent);
}
});
ImageButton salesButton = findViewById(R.id.salesButton);
salesButton.setOnClickListener(new View.OnClickListener() {

Page 31 of 35
@Override
Intent intent = new Intent(firstpage.this, sales.class);
}
});
ImageButton ledgerButton = findViewById(R.id.ledgerButton);
ledgerButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, ledger.class);
}
});
ImageButton paymentButton = findViewById(R.id.paymentButton);
paymentButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, payment.class);
}
});
ImageButton employeeRegistrationButton = findViewById(R.id.employeeRegistrationButton);
employeeRegistrationButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, employee.class);
}
});
ImageButton receiptButton = findViewById(R.id.receiptButton);
receiptButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, receipt.class);
}
});
ImageButton stockButton = findViewById(R.id.stockButton);
stockButton.setOnClickListener(new View.OnClickListener() {

Page 32 of 35
@Override
Intent intent = new Intent(firstpage.this, stock.class);
}
});
ImageButton attendanceButton = findViewById(R.id.attendanceButton);
attendanceButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, attendance.class);
}
});
ImageButton attendancButton = findViewById(R.id.imageButton2);
attendancButton.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(firstpage.this, attendanceview.class);
}
});
}
}

Page 33 of 35
B. SCREENSHOTS
Fig: Login Page
Fig : Purchase Details are Entered

Page 34 of 35
Fig: Sales Details are Entered
Fig : Stock Details are shown

Page 35 of 35
Fig : Receipt Details are shown
Fig : Ledger Details are Shown

21BIT044_DOCUMENTATION (1).docx

Recommended

Recommended

More Related Content

Similar to 21BIT044_DOCUMENTATION (1).docx

Similar to 21BIT044_DOCUMENTATION (1).docx (20)

Recently uploaded

Recently uploaded (20)

21BIT044_DOCUMENTATION (1).docx