Student Fees Management System Android App

Abstract

Hello, to develop an Android program related to Student fees management system consisting of Homepage, login page and features of the app are students can check their fee details, due fees, and date etc., through app along with SQLite database (local server).

Our project Student Fees Management System tracks all the details of a student from the day one to the end of his course which can be useful for all reporting purpose, tracking enrolment, status and all these will be available for future references too. We are developing an Android App using which every aspect related to fees can be involved.

Today majority of mobile users are Android users. So, we choose Android as a platform to develop the App. Through this, parents need not approach college every time for fees. They can get entire information like pending fees, paid fees, due date etc., just on single click on their mobile. Also easy for the college to maintain all these aspects just by updating the database.

This App is entirely GUI based i.e., user-friendly since the users also include the parents it is easy to understand and operate. It also includes the attendance of the student apart from the fees details.

want this app as user-friendly because we want to provide this to our college so that parents can check the fees details of their children through this app. Our main aim is that all the fees details like total fees, due fees, due date and all categories like a bus, tuition, exam, university fees etc, of a student, can be checked through the app. Whenever a student pays some fees in the college his/her record should be updated and can get same info through the app.

Home screen should have Admin login(college staff) and normal login(for students and parents both can log in through student id)

Admin should have rights to add, delete, update a student record and normal users should be able to check the fees details only.

Also, they should get notified about due date ie., last date for fee payment.

The student should log in through his unique ID has username and password and can change his/her password.

Forgot password option should be worked through student mail.

SQLite database should be used. As part of an academic career, we want to show the working of this app through our phones with some 50 records. And we ask our college management to provide economic help in order to implement it in a full-pledge manner. So that all the students can utilize this facility.

Food Ordering System using Context Aware Computing Project

Abstract:

In this Food Ordering System project, pop-up messages will inform the user about the existence of this application in the mobile device once moving from one location to another. This Food Ordering System application provides more comfort for the users in ordering the food and to avoid the railway catering system.

Features:

  • Uses the GPS from Android mobile to match the current location.
  • Automatically sends a message for Order once it is placed.
  • Displays on the Screen a message.

Existing System:

  • The user needs to Order the Food from the platform which seems to be unhygienic food.
  • Food which ordered not correctly packed
  • Use of unhygienic plastic to serve food

Proposed System:

  • In this Food Ordering System project, we use the GPS of an Android-based Smartphone to record and analyze various locations that could give alert to the user, then asking the user to select particular food from given hotel list and place an order.

Modules:

  • Device Background module
  • Phone Orientation and Location module

UML Diagrams:

Activity Diagram:

Class Diagram:

Collaboration Diagram:

Sequence Diagram:

Use Case Diagram:

Download the Food Ordering System using Context-Aware Computing  Android App Project

Food App – Restaurant Food Ordering Service in Trains

EXISTING SYSTEM DESCRIPTION

In the existing system, there is no such restaurant food ordering service for providing food services for passengers on the train. Railway catering is the only option for passengers to get food. Passengers face several problems in trains with unhygienic food. There are several cases where passengers faced health problems due to unhygienic food provided in trains.

Limitations of the existing system

  • Due to unhygienic food provided on trains, passengers’ health will be affected.
  • Without good food, small children in train journey also will have health problems like indigestion etc.

PROPOSED SYSTEM DESCRIPTION

This is an android application which is designed to order the food online while travelling by train. While travelling a long distance by train the main problem we face is food. To overcome such a problem we want to develop a mobile application through which we are ordering the food online. If the person wants to order food he/her can directly order the food so that the food is delivered directly to your seat and the cash-on-delivery process takes place between the customer and the person who delivers the food to us from the particular restaurant which we order.

Features of Proposed System:

  • Ordering the food online while travelling by train.
  • Provide more comfort for the users in ordering the food.
  • To avoid the unhygienic railway catering system.
  • The passengers can overcome the problems faced regarding their food need Complaints / Reviews can also be given about the food service

 

MODULE DESCRIPTION

Modules

User Module Description

In this user should install the application and then he should register into it. Registering into the application requires some fields such as email id, phone number. After registering into the application he/she user has to enter from and to address. Then the list of restaurants in various locations is displayed. Each restaurant displays the menu of a wide variety of food items. From that menu, the user can select the restaurant and food items and can order the food before reaching that particular station. The order consists of a list of food items along with passenger details like PNR number, train number, compartment number, berth and seat number. When the food is delivered to him, he pays the bill.

Restaurant Management Module:

The restaurant management receives the order. He can see the order in the same app and sends a person to deliver the food to the passenger. As the train waits for sometime in the railway station and with the help of passenger’s details, the restaurant person can get on the train and deliver the food to passenger and collects the bill amount. The mode of payment is cash-on-delivery. Also, there is a facility of complaint box, where complaints about the quality of food can be given to restaurant management. So that the restaurant management can improve their quality of service. The restaurant management can see the list of orders date-wise.

This Project is an android app for ordering food sitting in the train and giving the berth information.

The main requirement of this project is to provide an android app same as this which relates to food ordering and railways.

Advantages

  • Ordering the food online while travelling by train.
  • Provide more comfort for the users in ordering the food.
  • To avoid the unhygienic railway catering system.
  • The passengers can overcome the problems faced regarding their food needs.
  • Complaints / Reviews can also be given about the food services

Disadvantages

  • Due to unhygienic food provided in trains, passengers’ health will be affected.
  • Without good food, small children in train journey also will have health problems like indigestion etc.

SYSTEM REQUIREMENTS 

Software Requirements and Hardware Requirements: 

Software 

  • Operating system: Windows
  • Coding language: Android SDK
  • Toolkit: Android 5.0
  • IDE: Eclipse

Hardware

  • System: Pentium IV 2.4 GHz
  • Hard Disk: 80 GB
  • Monitor: 15 VGA Color
  • RAM: 2 GB

Runtime environment:

  • Device : Mobile / Tablet
  • OS: Android
  • Minimum Version : 0 Ice Cream Sandwich 

SYSTEM ARCHITECTURE:

The user can create and organize tasks or actions by interacting with a user interface (UI). UI internally interact with Restaurant where all the tasks are based on customer and order of the action to be performed or on the basis of priority. At ant time order placed, the dispatcher dispatches the order placed successfully message to the user console.

ER Diagram for Restaurant, User and Orders:

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS

Functional Requirements

  • The user can create/view the actions which are already performed and to be performed in the future.
  • The user can divide the actions based on the category.
  • The user can view and add the categories.
  • The user can also view and add the tasks in Restaurant Manager.
  • The user can prioritize the actions.
  • The user can view the actions, which are selected.
  • The user can order the items as per the requirement.
  • The user can make use of PNR number can directly communicate with the Restaurant Manager.

Use case Diagram:

Use Case Specification for User

Primary Actor:

User

Secondary Actor:

Database

Precondition:

Click On the Icon of Food Application

Post Condition:

Add an action into a database or Delete an action from the database.

Basic Flow:

  • Click on the Items in Item List.
  • Click on Item Name button to add an action.
  • Enter the information such as
    • Checking for available items
    • Items Name, Item cost, Active are Inactive
    • Conformation to User
    • Receive Order
    • Payment (COD)
  • Click on the Review button for Restaurant Rating
  • Click on go back and logout to end the task

Alternate Flow:

  • The user can enter his login id and password to order any other items.

Use Case Specification for Restaurant:

Primary Actor:

User

Secondary Actor:

Database

Precondition:

Actions/Tasks must be added in Inbox.

Post Condition:         

Retrieve information from database and display information on UI. 

Basic Flow:

  • Click on the Notification received from the user.
  • Give the confirmation to the user.
  • It displays order ID, delivery boy contact number, total amount.
  • It displays information about the duration of the delivery of the order.

Alternate Flow: 

  • If the mentioned PNR number is wrong then the order may not be considered in that case the restaurant module calls the user requesting to check his PNR number.

Class Description 

Description for Bootstrap Activity class:  

Attributes:

Purpose:

Launching Food Application 

Description for Login Activity class:

Attributes:

Guest Button, LoginButton1, Register Button Email edit- text, Password edit-text.  

Purpose: 

Ask the user to demonstrate with predefined categories. 

 Description for Restaurant Activity:

Attributes:

Orders Menu Items, Reviews.

Purpose: Display List of options

 Description List Orders Activity:

Attributes:

Button Pending, Button completed.

Purpose:

Action information is displayed to the Restaurant. 

Description for Review class:

Attributes:

List Reviews, Rating Bar.

Purpose:

Displays the list of action based on category. 

Description for Menu Items class:

Attributes:

List all Items, Button Back, Button check.

Purpose:

Displays the list of actions based on a task created 

Description for Pending Order Activity class:

Attributes:

List pending Order

Purpose:

Help the Restaurant to create a new action. 

Description for Selected Items class:

Attributes:

List Selected Items, Button Back.

Purpose:

Asks the user to enter the action information.

Description for Items Details class:

Attributes:

Edit text cost, Item number, Radio group status, Button Submit, Button Cancel.

Purpose:

Display the Details to the user. 

Description for Order Details class:

Attributes:

ID No, User Name, User Phone No, Items, PNR No, Cost

Purpose:

Used to display user details category.

Description for PNR status class:

Attributes:

Passenger Date, Coach, Train No, Berth No.

Purpose:

Used for user details for the order delivery for a new task.

Description for Train Details class:

Attributes:

Web view

Purpose:

Used for knowing the current running status of the train.

Description for the User Activity:

Attributes:

Station, spinner, get Button

Purpose:

Used to create a new task by the user.

Description for the List of Restaurant class:

Attributes:

Name, Rating, List of  Restaurants.

Purpose:

Displays the list of Restaurants. 

Description of the Restaurant Items class:

Attributes:

List items, cost, items name, checkbox, write a review, Button next.

Purpose:

Displays items available at the restaurants and to create a new category.

Description of the Write Review class:

Attributes:

Edit description, rating, submit.

Purpose:

Displays reviews of the user for the restaurants. 

Description of the List Items class:

Attributes:

List Items, cost, Button cancel , order now.

Purpose:

Displays the list of items.

Sequence Diagram:

Collaboration Diagram for FoodApp:

For creating Orders and User Actions from it:

Collaboration Diagram for Creating Orders:

For creating Receiving Order to User Action:

Collaboration Diagram for Receiving Orders:

Activity Diagram:

Displaying Smart Phone Data Android Project Report

Problem Statement:

Nowadays MNC companies are not allowing using smartphones in the workplace because the data is being transferred illegally. Due to this, the user is unable to know any important or urgent information.

Existing System:

In the existing system, some information such as missed calls and battery, messages information, referred to as device-oriented information. However, such information is related to a user. For example, if the user works in a company and cannot carry his mobile due to security issues then the user is unable to view the information.

Proposed System:

The application is based on sharing information such as battery status; miscall info and message from the Android device to web application, i.e., whenever the battery drains or any miscalls or when a message comes all this information will be updated on the server system and the user can view that information using the web application from anywhere.

Product Scope:

Users can access their device information from anywhere, anytime using server services.

Literature Survey:

The application is based on sharing information such as battery status; miscall info and message from Android device to web application, i.e., whenever the battery drains or any miscalls or when a message comes all this information will be updated on the server system and the user can view that information using the web application from anywhere.

Software Requirements Specifications

Introduction

The software product described in this document is Displaying Smart Phone Data. The main purpose of developing this system is to share device-oriented information i.e., location details to the server and retrieve that information from a server using Web Application

Product Scope

Users can access their device information from anywhere, anytime using server services.

Product Functions

The major functionalities of this website will be as follows:

  • User credentials.
  • Sending data from Android Device.
  • Displaying data.

Development Environment

Software and hardware required to develop this project are mentioned as follows.

Software requirements

Programming Platform: JDK 1.7, Android SDK

IDE: STS (Spring Tool Suite)

Web server: Google Server (Google App Search Engine)

Database: Google Database

SYSTEM FEATURES

The major functionalities of this project will be as follows:

  • User credentials.
  • Sending data from Android device.
  • Displaying data.

User credentials

The user provides registration details and registers, then logins by providing username and password.

Functional Requirements

Authentication:

It provides authentication to individuals who wish to get connected. The registration details are stored in the database and whenever the user logs in, the user credentials are retrieved to check whether the user is an authorized user or not.

If the details entered do not match with any of the existing data then the system displays a warning.

Sending data from android device

Users click in android mobile to get missed call, messages and battery information.

Functional Requirements

A user can choose information to push to external services. The application currently supports three types of information:

the battery information of the device, SMS and missed call history. It shows how to get mobile device related information and send it to the server.

Displaying Data

In this, the system creates a web Application to show the missed call, messages and battery information.

Functional Requirements

In this module system will develop a web application which can access, show the data pushed from the device to the server. It will show the missed call, messages and battery information using the data grid

DESIGN DIAGRAMS

UML DIAGRAMS

Use-Case Diagram

Figure: Use-Case diagram for the User

The user interfaces with the server. When the user login for the first time a user has to register the details. After registration, the user logins and receives the information about the battery missed call and SMS history of the phone. Finally, the users can log out.

Class Diagram

Figure: Class Diagram for the user, Web application and Database

The above figure depicts the three main classes User, Application and Database, where the user depends on the Application. The user interacts with the Application using Username and Password. And the Application is associated to the Database to retrieve and for storing information about the phone.

Sequence Diagram

Figure: Sequence Diagram for the User

The sequence diagram shows the external flow of the system. The user logins with the server by giving username and password. Then the user receives the information about the battery, missed call and SMS history by requesting the server. After the user receives the information the user can log out.

Collaboration Diagram

Figure: Collaboration Diagram

Test Cases:

Test Case #: 1 

Test Case ID Test Case Type Test Case Description Expected Value Actual Value Result
1 Entering URL of the Web application Checking status of Google Server and URL, through which the application begins The application should begin If the URL entered is corect then the application starts functioning Application starts successfully
1 Entering wrong URL of the Web application Checking status of Google Server and then entered URL is wrong The application fails to begin Entered URL is incorrect the application doesn’t begin Unable to start the Web Application

 Test Case #: 2 

Test Case ID Test Case Type Test Case Description Expected Value Actual Value Result
2 User Registration Registration details of the user will be present here If the user name has unique identity then user get register successfully User is getting Authenticated User is successfully registered.
2 User  Registration gets failure Without entering anyone of the fields if the user clicks on submit then alert message will be displayed. User will not able to registered An alert will be displayed An alert will be displayed like “Enter all the fields”.
2 User  Registration gets failure When a user tries to register with the same user name, then user will not get registered. User will not able to registered A alert is displayed An alert will be displayed like “Username already exists, try another”.

 Test Case #: 3 

Test Case ID Test Case Type Test Case Description Expected Value Actual Value Result
2 User Authentication User credentials of user are authenticated. User credentials are to be correct

 

User gets Authenticated The user login is successful and is authorized to use the system
2 User  Authentication gets failure User credentials of user are not authenticated. Login details are to be incorrect User Authentication

Fails

The user login is failed and is not able to use the system
2 Login into website Without giving User credentials Trying to login without providing User credentials. An alert is to be displayed An alert is displayed The user login is failed.

  Test Case #: 4

Test Case ID Test Case Type Test Case Description Expected Value Actual Value Result
4 Navigates to Home page The user tries to view the information. The required information(call,

Sms, battery) information should be displayed.

Information is retrieved from database The information is displayed successfully.
4 Home page cannot be redirected The user tries to view the information but home page can’t be displayed. The error page will be displayed. Due to some connection problem (Sms, call and battery) information of mobile will not be sent to the database.

 

This webpage is not available.

 Test Case #: 5 

Test Case ID Test Case Type Test Case Description Expected Value Actual Value Result
5 Mobile Status Changed Mobile Status is changed automatically web service will be called. The information can be viewed by the user. (Call, sms and battery) information will send it to the database.

 

The information can be retrieved.
5 Mobile Status not Changed Mobile Status cannot be changed. The information can’t be viewed by the user. (Call, Sms and battery) information will not be sent to the database.

 

The information can’t be retrieved.

 Screen Shots

  • Home Page

  • Registration Page for USER

  • Entering details in Registration Page

  • Displaying Alert box to enter all details.
  • Entering all details
  • Redundancy of USER name

  • Successful Registration of User
  • Login page in Android Phone

  • Displaying Alert message

  • Displaying an alert message
  • Selecting all mobile information

  • Sending information to the database
  • User Login Page
  • Displaying an error message
  • Successful Login

  • Displaying Battery Status

  • Displaying a message if there are no results to show
  • Displaying information on Call History.
  • Displaying information of SMS history
  • Clearing the information

Conclusion and Future Scope

This application, “Displaying Smart Phone Data” is based on sharing information such as battery status; miscall info and message from android device to web application, i.e., whenever the battery drains or any miscalls or when a message comes all this information will be updated on the server system and the user can view that information using the web application from anywhere.

In future, this project is useful to any Android mobile user where the user can get his mobile information data using Android Broadcasters. Before using the application, the user should register. This application detects the mobile information like SMS, call and battery information. So that the user can view the mobile data in Flex Application.

Easy Market Android App Project Report

Presently handheld devices such as smartphones are using very huge. In short, we are using them to easy to solve our work. One application that falls into this category is Easy Market developed for Android phones. This application will help salespersons in managing the various types of Records such as client details, supplier details, product list and help to easily sell the product. The salesperson recording the details of the clients, suppliers, profit on paper is a time-consuming process. Also difficult to retrieve the previous records of clients, suppliers, product details.

This Easy Market Android App will solve the problem. The user can add a new product into the list by name, price or delete any product from the list which is not available in the market. It allowed changing the price of the product not affect the price registered in the catalogue of products. It shows how much the quantity of each product present in the inventory. It has an option to filter the products. It allows to record the customer details and show when he last came, what products he bought that day, the total price of the products. It records and shows the supplier details like the name of supplier, last visit, amount. It also displays how much profit he earn that day and how much is initial money at the opening of day and total money at the closing of the day.

The project “Easy Market” is developed with the objective of making the system reliable, easier, fast, and more informative.

Advantages:

  • Easy to maintain data.
  • Less time-consuming.

Easy Market is a mobile application used by the shopkeeper to record and manage the details of their shop like sales money. It is used to easily manage the details of the inventory and sell the product easily.

This application developed in android technology can install in any smartphones devices. This application contains various pages as clients, suppliers, sales, inventory etc. By logging in into the application shopkeeper can go to any page without recording in books.

Scope

To develop a product called “Easy Market” which is composed by an application for Mobile Devices and other Web management roles, users and information providers

The perspective of the product

Easy Market in a solution that will allow trade settlements through mobile devices like the Tablet, manage the operation of its business.

Product Functionality

The features that must have the applications are:

For mobile devices

  • Login
  • Client Details
  • Supplier Details
  • Inventory
  • Sales
  • Login Details

Assumptions and Dependencies

It should be developed for Android devices.

Predictable System Evolution

The system must be portable and scalable so that support users increased significantly and can be adapted to any type of establishment e.g. neighbourhood or shop etc.

Nowadays in general shopkeeper who used to record their shop details like client, product selling price, product purchase price, what is the discount on that product on paper and searching in the book. He/she used to search in books whether the client has to pay any amount in past and how much quantity of material still remaining in the shop. He uses a calculator to calculate the total amount of the bill.

Disadvantages of the existing system

  • Time-consuming.
  • Waste of paper.
  • Difficult to search and remember the details.

Proposed system

The proposed system aim is to reduce the difficulty of remembering the details and manage the shop details easily.

Advantages of the proposed system

  • Less time-consuming.
  • No paperwork.
  • No use of Calculator.
  • Reduce human effort.

Specific Requirements

Common Interfaces Requirements

Hardware Interfaces

• Input and output data are stored on the SQL Server 2014 database server.

• Development must support at least version 4.0 of Android.

Functional Requirements

Images of an example of what should be the requirements are attached in the next chapter.

Login

The application will ask for a username and password, previously created in the Database. The system must ensure that the username and password are valid, which otherwise will be left to the user in the login screen.

Client Module

• Enter this module list clients created with the value of the debt.

• You will have an option of creating customers where would deploy the user a screen where it will ask the following information:

Or required fields: name, Aadhar, phone, address, email address and gender.

Or non-obligatory data: the value of the initial debt. By default must be zero.

In the creation of the client should be validated by the number of identification card there is no customer.
• Created client list must have an option to edit customer data, in where it will display a window with the data of the client, allowing you to modify all data except for identification card and the value of the initial debt.
• Allow client search by the following filters: name and identification card.

• Whenever client doesn’t money to pay bill his debt will add to his details.

Supplier Module

• This module you enter providers that are created, data listed are as follows: Nit, the name of the manufacturer or distributor, a balance which is due.

• It will have a choice of provider creating, selecting this option would deploy a window to the user where requests the following information:

or – mandatory data: Nit., name, phone, address, visit (Monday, Tuesday, Wednesday, etc.) this field is multiple selections and frequency of visits (weekly, fortnightly and monthly.

or Optional data: name of contact and contact phone.

• When user unable to pay the total amount to supplier he can save the debt amount in this whenever required.

• The date when supplier last visit also record here.

Inventory Module

• Upon entering this module it lists the products created in the store. The following will show code of the product, the product description, quantity in the inventory, the price of sale and utility value.

• You will have a choice of creating the product. Selecting this option show the user a window where will ask for the following information:

or barcode: mandatory, to enter this field the system must validate if the product exists in the teacher’s products, if any product, you must bring the following information: name, group and line

or name: required field. It is the name of the product

or unit of measure: optional field. This field is for fruit and vegetable products. It allows selecting the type of measurement that will be used for the product (Kg and G) none for soap or others. It is not a mandatory field.

or purchase price: required field. It is the purchase price of the product.

or sale price: required field. It is the selling price of the product.

or quantity: required field. It is the amount that is the product.

or VAT: optional field. It is the value of VAT on the product. To create the product are:

• You will have an option to edit the product. Selecting this option will display the product data and allows to edit the following details: price sale, purchase price, taxes and supplier.

• You will have an option to search for products, search filters are as follows: barcode, name, internal code and provider.

• You will have an option to filter the list of products. The filters that you can arrange Products.

• Upon creating the product user need to arrange the product into his inventory. The first shop does not have any goods or products so the user needs to transfer his data from product module to the inventory module. Upon clicking the inventory module user will able to see his products which are present in his shop but not in the storeroom. He able to sell the items which are present in the inventory because the sales module navigate screen to inventory module only. So he needs to transfer shop products from storeroom to inventory.

• From product module user able to transfer products to inventory by entering the following data

Mandatory:-Quantity.

Not-Mandatory:-Unit of Measurement. Or any changes.

• Unit of measurement (UOM) is not mandatory because for bananas and sugar UOM is not the same.

Sales Module

• Allows to associate a client with the sale, the customer can be one registered (should be selected from a drop-down list) or one casual which is by default when this module is loaded.
• Be permitted creating users and payment of debt, as described in the customer module

• The user can register products on sale by either:

Or through a reader of the barcode in which case the screen the product price. Whenever You read the product is adding to the amount of reading product.

Or manually, where the user must have the following filters: name, barcode, code

Internal and the last 4 numbers of the barcode. When you select the product, will add the product on sale.

• Maybe delete some proceeds from the sale. Whenever you add a product on sale system calculate the Subtotal of sale, VAT and total sale.

• Should be allowed to change the quantities and price of a product manually. If the price is modified, this should not affect the price registered in the catalogue of products. However, if it should be recorded in the sales.

• At the end of the sale the user may choose different means of payment which are: Effective: would deploy a window with the total of the sale, a field to enter the value which is paying customer and a calculated field of change where it is calculated: the value paid by the customer, less the total of the sale.

This single payment method may be by customers of the store, for an occasional client does not appear this payment method. When you select this payment method displays a summary of the sale: the total sale, the name of the client and the client’s debt total. The system must add the total of the sale to the client’s debt.

• Discount value reduces the actual price cost.

• At the end of the sale system must subtract the quantities of each product in inventory.

• At the end of the sale system allows printing the invoice, where detailed invoice number, product, price, quantities and the total value of the sale.

• At the end of the sale system allow to modify and update the inventory module.

Login Details

• The time when the user last login details saved details as follows

Username, Date, Time.

Non-Functional Requirements

Performance Requirement

The Proposed system that we are going to develop will be used as a chief performance system in supermarkets. Therefore, it is expected that the database will perform functionally all the requirements specified by the user.

More Informative

The application is more informative because more information is stored in the database than paper stored information.

UML Diagrams:

Use case Diagram for Easy Market:

Class Diagram for Easy Market:

Sequence Diagram for Easy Market:

Activity Diagram for Easy Market:

Output Screens:

  • Login layout
  • Menu list layout
  • Client layout
  • Client Registration layout
  • Supplier layout
  • Supplier Registration
  • Inventory layout
  • Product Details layout
  • Product Registration layout
  • Product Details layout
  • Sales layout
  • Custom Sales layout
  • Saving Sales layout
  • Login Details layout

Conclusion

After the completion of the project, one can clearly say that our developed application will help shopkeepers in many ways to record the details. This is the easy way to record the details manage them. It can use by any persons who have a shop and who does not want to record the details of the shop not on paper to reduce his effort and time-consuming.