Sen Final

You might also like

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

ProgrammeName:ComputerEngineering AcademicYear: 2022-2023

Program Code : CO4I

CourseName:SoftwareEngineering Semester: IV
Course Code: 22413
A STUDY ON

SHOPPING BILLING SYSTEM

Group number-22 MICRO PROJECT REPORT


Submitted in Apr 2023 by the group of 4 students
Sr. Enrollment Exam Seat
No Roll No Full name of Student No No
1 26 Devyani Gaikwad 2100590073 378642

2 29 Harshwardhan Thalnerkar 2100590076 378645

3 85 Riya Rajendra Patil 2100590136 378700

4 118 Janhvi Sunilkumar Suryawanshi 2100590171 378733


Under the Guidance of
MS. D.R. Agrawal
in
Three Years Diploma Programme in Engineering &
Technology of Maharashtra State Board of Technical
Education, Mumbai (Autonomous) ISO 9001: 2008 (ISO/IEC-
27001:2013)
at
0059 - Shri Shivaji Vidya Prasarak Sanstha’s Bapusaheb
Shivajirao Deore Polytechnic, Vidyanagari, Deopur, Dhule-424005.
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION,
MUMBAI
Certificate This
is to certify that,
Sr. Roll Full name of Student Enrollment Exam
No No No Seat No
1 26 Devyani Gaikwad 2100590073 378642
2 29 Harshwardhan Thalnerkar 2100590076 378645
3 85 Riya Rajendra Patil 2100590136 378700
4 118 Janhvi Sunilkumar Suryawanshi 2100590171 378733
students of Fourth Semester, Diploma Programme in Engineering & Technology at

0059 - Shri Shivaji Vidya Prasarak Sanstha’s Bapusaheb Shivajirao Deore

Polytechnic- Dhule, has completed the Micro Project satisfactorily in Subject

Software Engineering (22413) in the academic year 2022-2023 as

prescribed in the

MSBTE curriculum of I Scheme.

Place: Dhule

Date: / /2023

Project Guide Head of the Department Principal

PART – A MICRO PROJECT PROPOSAL


SHOPPING BILLING SYSTEM

1.0 Introduction
The Shopping Billing project deals with the automation of supermarket. This will help salespersons in
managing the various types of record of customer. The product will help the user to work in a highly
effective and efficient environment. Salespersons have been recording the customer information in the
past and even in the present through their personal manual efforts. In manual system, there are number
of the inefficiencies that a salesperson faces. The information retrieval is one of the foremost problems.
It is very difficult to gather the overall performances reports of the customer. Large record books have
to be maintained where relevant and irrelevant information has to be stored. This automation deals with
all such problems and tries to remove them in the best suitable fashion. The new system will cater to
need of salespersons of any supermarket so that they can manage the system efficiently. The project is
developed with the objectives of making the system reliable, easier, fast and more informative.

2.0 Aim of the Micro-Project

The project aims at serving the Department of Shopping Billing by computerising the
Billing System in Software Engineering.

3.0 Intended Course Outcomes

1)Apply project management and quality assurance principles in software


development.
2)Select suitable process model for software development.
3)Prepare software requirement specification
4)Use software modelling to create data designs
5)Apply project management and quality assurance principles in software development

4.0 Literature review

We have learned from this project the different phases of Software Engineering and
how does the software work in various steps. We have also learned to extract ER
Diagrams, Data Flow Diagram, USE Case diagram in actual modelling phase for the
Shopping Billing System.

5.0 Proposed Methodology

Requirement Analysis: The first step in any software development project is to gather
and analyze requirements.This involves Identifying the features and functionalities
that the Shopping Billing System should offer, as well as any constraints or limitations
that need to be taken into account.
System Design: Once the requirements are gathered, the next step is to design the
system architecture. This involves deciding on the software components and
technologies that will be used to build the system, as well as the data models and user
interfaces.
Implementation: After the system architecture is designed, the next step is to implement
the system. This involves writing the code, building the database, and integrating the
various software components. It is important to ensure that the code is well- structured,
well-documented, and follows best coding practices.
Testing: Once the system is implemented, it needs to be tested thoroughly to ensure
that it works as expected. This involves both functional and non-functional testing,
including testing for usability, reliability, performance, and security.
Deployment: Once the system is tested and ready to go, it can be deployed in a
production environment. This involves configuring the system for the production
environment, installing it on the servers, and setting up any necessary infrastructure.
Maintenance: Once the system is deployed, it needs to be maintained and updated over
time to ensure that it continues to function correctly. This involves monitoring the
system for Issues, fixing any bugs that are discovered, and making updates and
enhancements as needed.

6.0 Resources Required


Book-Name-Software and Software Engineering 7th Edition
Author Name-Roger S. Pressman References-https://slideplayer.com
https://www.engppt.com
7.0 Action Plan

Sr. Detail of Activity Planned Start Planned Finish Name of


No. Date Date responsible
team members

1. Define problem for 24/3/2023 31/3/2023 Tejas pawar


Project

2. Gather the 31/3/2023 7/4/2023 Mohit patil


Requirements

3. Searching and gathering 7/4/2023 21/4/2023 Mohit patil


Requirements

4. Designing the project 21/4/2023 21/4/2023 Mohit patil

5. Documentation 21/4/2023 24/4/2023 Avinash Deore

6. Demonstration 24/4/2023 5/5/2023 Avinash deore


PART B – Micro-Project Report

SHOPPING BILLING SYSTEM

1.0 Rationale
Billing system for grocery shop is built to calculate and display bills for different items and serve the customer in a faster
and efficient manner. Grocery shop is the place where customers come to purchase their daily using products and pay for
that. So there is a need to calculate how many products are sold and to generate the bill for the customer. This system is
built for fast data processing and bill generation for customers. It also allows the customer to purchase and pay for the item
purchased. The user will consume less time in calculation and sales activity will be completed within fraction of seconds
whereas in a manual system will make a user to write it down which is a long procedure and it also consumes a lot of time.
Because Only shopkeeper can use this software. The billing system consists of an sql database and effective front end
design.

2.0 Course Outcomes Addressed


a) Performed various operations on software as accept,calculate,display.
b) Computed the Shopping bill in software.

3.0 Literature Review

We have learned from this project the different phases of Software Engineering and
how does the software work in various steps. We have also learned to extract ER
Diagrams ,
Data Flow Diagram, USE Case diagram in actual modelling phase for the Hospital
Management

4.0 Actual Methodology Used

Problem Definition:
Modern billing software can solve many problem to manage retail efficiently.
Retailers and quick service shopping store owners need to take lots of features
into consideration in order to make sure that the business runs smoothly.It is
not only the everyday sales, but also the customer retention, sales and stock
tracking, accounts recievables, which needs proper management. And being in
charge of all of these things is definitely not easy, more so, when you are
required to take care of all these things single handedly. An automated and
intuitive billing solution makes things easier in such a situation
Functional Requirements:

There are various features included in the ShoppingBilling System . Some of the
system functions include Validation of customer details,Computing Shopping bill as
per the product purchased by the customer, Report generation, and more. In this blog,
let's check out the functional and nonfunctional requirements of the Shopping Billing
System in depth. There are a lot of software requirements specifications included in the
functional requirements of the ShoppingBilling System, which contains various
processes, namely Validation of customer details,Computing Shopping bill as per the
products purchased by the customer, Report generation,and database.

Registration Process of SRS (Software Requirements Specification)

● Accepting Details of customer : The Shopping Billing System enables the


customer to enter his or her valid details in the system.
● Validation of customer details : The Shopping Billing System enables the
customer to verify his details ,also the system makes an authentication and
verification of details entered by customer during Login .
● Verification of Customer Information : Every customer can make the verification
of his or her details .

● Accepting products purchased by customer : The Shopping Billing System


enables accepting the products purchased by the customer.

● Validation of entered products : The Shopping Billing System enables for


Verification and Authentication of the entered products .

● Computing the Shopping Bill : The Shopping Billing System enables for
computerising the Shopping Bill as per the products purchased by the customer.

● Displaying Details and Shopping Bill : The Shopping Billing System enables for
Displaying the details and Shopping bill of customer.

Non-Functional Requirements

There are a lot of software requirements specifications included in the non-


functional requirements of the Shopping Billing System, which contains various
processes, namely Security, Performance, Maintainability, and Reliability.
● Customer Identification: The system needs the customer to recognize herself
orhimself using valid phoneNo and name.

● Customer ID: Any users who make use of the system need to hold a Customer
ID
.
● Administrator rights: The administrator can view as well as alter any
informationin the Shopping Billing System.

● Modifications: Any modifications like insert, delete, update, etc. for the

databasecan be synchronized quickly and executed only by the ward

administrator Performance:

● Response Time: The system provides acknowledgment in just one second


oncethe customer’s information is checked.

● Capacity: The system needs to support at least 1000 people at once.

● User-Interface: The user interface acknowledges within five seconds.

● Conformity: The system needs to ensure that the guidelines of the


Microsoftaccessibilities are followed.

Maintainability:

● Back-Up: The system offers efficiency for data backup

● Errors: The system will track every mistake as well as keep a log of it.

Reliability:

● Availability: The system is available all the time.

Hope you got a clear idea of the functional and non-functional requirements and
the features required by the Shopping Department. Any other queries on the topic
are welcome.
1.Use Case diagram

Activity Diagram
3.ER Diagram
TEST SCENARIOS/CASES

Sr.no Test Test Pre- Test Test Data


Expected Port
Scenario case Condition Step Result Condition
1 Verify the Enter Need a 1.Enter <valid Successful Billing
Login of Valid verified user username> Login of Details
Shopping
username name Name <valid cutomer are
Department
and valid and phone shown
phone phone 2.Enter number>
number number phone
for the numbe
login r

3.Click
on the
login
button
2 Verify the Enter the Need a 1.Enter <valid Successful A message
login of valid verified user username> Login of “you
username
Shopping
and
name Name <invalid customer Entered
Billing invalid
System invalid and phone phone
phone phone 2.Enter number> number “is
number number phone shown
for the numbe
login r

3.Click
on the
login
button
3 Verify the Enter the Need a 1.Enter <invalid Successful A message
login of invalid verified user username> Login of “you
username
Shopping name Name <valid customer Entered
Billing and valid invalid
System phone and phone username
number phone 2.Enter number> “is shown
number phone
for the numbe
login r

3.Click
on the

login
button
4 Verify the Enter the Need Enter <invalid Calculation A
units to valid verified Valid product of message”Y
compute products products to prod s> Shopping ou entered
The purchased compute ucts Bill invalid
Shopping Shopping units1”is
Bill Bill shown
5 Verify the Enter the Need Enter <invalid Calculation A
products valid verified Valid product of message”Y
to products products to prod s> Shopping ou entered
compute purchased compute ucts Bill valid
The Shopping units1”is
Shopping Bill shown
Bill
5.Actual Resources Used
Sr. No. of Specifications Quantity Remarks
Name
Resources

1 Hardware Desktop- 1
computer PRH
system 45k9(i5),
RAM 8.00GB
And
(usable7.74GB)

2 Operating 64-bitOperating 1
system system,
Widows11
Home single
Language

3 Software StarUML 1

6.0 Skills Developed/Learning out of this Micro-Project

We successfully learned and implemented all the operations and applications for
computing Electricity Bill as per the units .

7.0 Applications of this Micro-Project

This system is used in the Grocery Shop or Super Market for computerising the Billing System .

8.0 Area of Future Improvement

• ONLINE PAYMENT : In future additional facilities like Online Payment can be


added to the system.

• REORD MANAGEMENT : It can track all the information of Bill, Shopping


Board, Store Record etc. Manage the information of Bill, Also can show the
information and description of Shop.
Title of the Project: Shopping Billing System
COs addressed by the Micro Project:

a) Performed various operations on software as accept,compute,display.

Academic Year: 2022-2023 Name of Faculty: Mr.S.P Chavan


Program Name and Code: CO(4I)
Semester: Fourth

Course Code: 22413 Course Name: Software Engineering


Major Learning Outcomes achieved by students by doing the Project:
(a) Practical Outcomes
Basic Knowledge: Apply knowledge of basic mathematics, sciences and basic
engineering to solve the broad-based Electronics related problems.

(b)Unit Outcomes (in Cognitive domain)


Unit 1(A), Unit 2(A)

(c) Outcomes in Affective Domain


Performed various operations on software as accept,compute,display.
Comment/Suggestions about team work/leadership/inter-personal Communication
(If Any
):

Any Other Comment:

Marks:
Name of Student: Mohit patil

(A) Marks for Group work: (B) Marks for Individual work: (C) Total Marks (A+B) =

(Mr.S.P Chavan Lecturer in Software Engineering)

Signature with Name and Designation of the Faculty


Member
Title of the Project: Shopping Billing System
COs addressed by the Micro Project:

a) Performed various operations on software as accept,compute,display.


Major Learning Outcomes achieved by students by doing the Project:
(a) Practical Outcomes
Basic Knowledge: Apply knowledge of basic mathematics, sciences and basic
engineering to solve the broad-based Electronics related problems.
(b)Unit Outcomes (in Cognitive domain)
Unit 1(A), Unit 2(A)

(c) Outcomes in Affective Domain

Academic Year: 2022-2023


Comment/Suggestions Name
about team of Faculty: Mr.S.P Chavan Communication
work/leadership/inter-personal
(If Any
):
Program Name and Code: CO(4I)
Sem: Fourth

Course Code: 22413 Course Name: Software Engineering


Any Other Comment:

Marks:

P
erformed various operations on software as accept,compute,display.
Name of Student: Avinash Deore

(A) Marks for Group work: (B) Marks for Individual work: (C) Total Marks (A+B) =

(Mr.S.P Chavan Lecturer in Software Engineering)

Signature with Name and Designation of the Faculty


Member
Title of the Project: Shopping Billing System
COs addressed by the Micro Project:

a) Performed various operations on software as accept,compute,display.


Major Learning Outcomes achieved by students by doing the Project:
(a) Practical Outcomes
Basic Knowledge: Apply knowledge of basic mathematics, sciences and basic
engineering to solve the broad-based Electronics related problems.

(b)Unit Outcomes (in Cognitive domain)


Unit 1(A), Unit 2(A)

(c) Outcomes in Affective Domain


Comment/Suggestions about team work/leadership/inter-personal Communication
(If Any
):

Academic Year: 2022-2023 Name of Faculty: Mr.S.P Chavan


Any Other Comment:
Program Name and Code: CO(4I)
Sem: Fourth
Marks:
Course Code: 22413 Course Name :Software Engineering

P
erformed various operations on software as accept,compute,display.
Name of Student: tejas pawar

(A) Marks for Group work: (B) Marks for Individual work: (C) Total Marks (A+B) =

(Mr.S.P Chavan Lecturer in Software Engineering)

Signature with Name and Designation of the Faculty


Member

You might also like