PRACTICAL FILE

SESSION: 2023-24

Software Engineering Lab (CIC-357)

III Year, V Sem

Submitted to: Submitted by:

Name: Dr. Archana Sharma Name: Jai Kumar Mishra

Designation: Professor Enrollment No. - 10918002721

 INDEX
S.NO TITLE DATE SIGNATURE

1. To develop a Fast Food Billing System

2. Do Requirement Analysis and develop Software

Requirement Specification Sheet (SRS) for Fast
Food Billing System.

3. To perform the function oriented diagram : DFD

and structured chart for Fast Food Billing System.

4. Draw the Entity Relationship diagram for Fast

Food Billing System

5. To perform the user’s view analysis for the Fast

Food Billling System : Use Case Diagram

6.
To draw the structural view diagram for the system
:- Class Diagram, Object Diagram.
 EXPERIMENT 1

AIM: To develop a Fast Food Billing System

REQUIREMENTS :
a) Software: Windows 10
b) Hardware –
1. POS Devices
2. Computer

THEORY:
A Fast Food Billing System is a specialized software application designed to streamline the
ordering and billing process in fast food restaurants, quick-service eateries, and other similar
establishments. Here is some information related to Fast Food Billing Systems:

This system needs to address several critical challenges faced by fast food establishments.
Firstly, it must streamline the process of order management, ensuring that customer orders are
accurately recorded, avoiding errors that can lead to customer dissatisfaction or financial
discrepancies. Secondly, it should integrate seamlessly with the restaurant's menu, simplifying
the selection of items and their corresponding prices. Thirdly, it should be capable of accurately
calculating bills, including taxes, discounts, and additional charges, to ensure that customers are
charged correctly.

Moreover, the system must handle diverse payment methods, from cash to credit cards and
mobile wallets, providing convenience to customers and reducing payment processing issues. It
should also allow for order customization to cater to individual preferences. Efficient order
tracking and display are essential to ensure orders are prepared promptly and delivered in a
timely manner. The system should generate clear and detailed receipts, either in print or
digitally, to provide transparency and serve as a reference for customers.
Furthermore, it should offer reporting and analytics capabilities to provide valuable insights into sales,
inventory, and customer preferences, facilitating data-driven decision-making. Integration with other
restaurant systems, such as inventory management and accounting, is critical for operational efficiency.
Data security is paramount, given the sensitive customer data and payment information involved. Lastly,
the system must be scalable, accommodating changes in menu offerings, staffing, and customer volume
as the business expands. Tackling these challenges comprehensively will lead to a fast food billing system
that enhances operational efficiency and customer satisfaction while fostering business growth.

CONCLUSION:
Fast Food Billing Systems are essential tools for fast food restaurants and similar
establishments. They improve operational efficiency, enhance the customer experience, and
provide valuable data for business decisions. These systems continue to evolve with
advancements in technology, such as mobile ordering and contactless payments.
 EXPERIMENT 2
AIM: Do Requirement Analysis and develop Software Requirement Specification Sheet (SRS)
for Fast Food Billing System.

REQUIREMENTS :
a) Software: Windows 10
b) Hardware –
1. POS Devices
2. Computer

1.2 Purpose

This document serves as a comprehensive guide for stakeholders involved in the development
and implementation of the Fast Food Billing System. It outlines the project's objectives,
features, and constraints to ensure a clear understanding of the system's requirements.

1.3 Scope

The Fast Food Billing System will cover order processing, billing, and inventory management for
a fast food restaurant, addressing the needs of both customers and staff. It will integrate
seamlessly with existing hardware and software infrastructure to create a cohesive and efficient
solution.
2. Overall Description

2.1 User Interfaces

The system will feature user-friendly interfaces for customers to browse the menu, customize
orders, and track their order status. Staff interfaces will include dashboards for order
management, billing, and inventory tracking. The interfaces will be designed with
responsiveness in mind, catering to both desktop and mobile devices.

2.2 Hardware Interfaces

The Fast Food Billing System will be compatible with a range of hardware components
commonly used in the food service industry, such as point-of-sale terminals, receipt printers,
kitchen display systems, and barcode scanners. Integration with these devices will be seamless
to ensure smooth and reliable operations.

2.3 Software Interfaces

The system will integrate with popular payment gateways to facilitate secure and efficient
transactions. Additionally, it may interface with third-party inventory management software to
provide real-time updates on stock levels and automate reordering processes.

2.4 Communication

The communication between the user interfaces and the server will be facilitated through
secure protocols to ensure the confidentiality and integrity of data. Real-time updates on order
status and inventory levels will be transmitted efficiently to keep all system components
synchronized.
3. System Features

3.1 Order Processing

- Customers can browse the menu, view detailed item descriptions, and customize their
orders, including special requests and dietary preferences.

- Staff can efficiently manage incoming orders, prioritize tasks, and communicate
with the kitchen staff for order fulfillment.

- Real-time order status updates for customers through SMS or mobile app notifications.

3.2 Billing

- Automatic calculation of the bill based on ordered items, including applicable

taxes and discounts.

- Support for various payment methods, including cash, credit/debit cards, and digital wallets.

- Receipt generation with detailed order information for customer reference.

3.3 Inventory Management

- Real-time tracking of available stock for each menu item.

- Automated alerts for low-stock items, with the option to set up automatic reordering.

- Detailed inventory reports for better decision-making on stock management.

4. Performance Requirements

4.1 Response Time

The system should respond to user interactions within 2 seconds to ensure a seamless and
responsive user experience.

4.2 Throughput

The system should be capable of handling a minimum of 100 orders per hour during peak times
to prevent delays in order processing.

5. Design Constraint

The system architecture should be designed to operate on standard hardware, and scalability
considerations should be incorporated to accommodate potential increases in user load as the
restaurant expands.

6. Software System Attributes

6.1 Reliability

The system should ensure accurate billing and order processing with a maximum error rate of
0.1%. Regular system audits and testing will be conducted to maintain reliability.

6.2 Security

Secure user authentication and authorization mechanisms will be implemented to prevent

unauthorized access. Customer and transaction data will be encrypted to ensure confidentiality.
7. Logical Database Requirements

7.1 Database Structure

The system will utilize a normalized relational database to store menu items, customer
information, order details, and inventory data. The database schema will be designed for
optimal performance and scalability.

7.2 Data Integrity

The database will enforce data integrity through referential integrity constraints, ensuring
consistency and accuracy in the stored data.

8. Other Requirements

- The system should be compatible with Windows, macOS, and Linux operating
systems to accommodate various hardware configurations.

- Regular data backups will be performed nightly, with a retention period of one
month, to prevent data loss in the event of system failure or data corruption.

9. Change Management Process

Changes to the system, whether in terms of functionality or infrastructure, must go through a

formal change request process. This process involves detailed impact assessments, stakeholder
evaluations, and approvals to ensure that changes align with project goals.
10. Document Approval

This document is to be reviewed and approved by the Project Manager, Lead Developer, and key
stakeholders before development commences. Any subsequent changes to the document will
undergo a similar review and approval process.

11. Supporting Information

Include any additional information, diagrams, or references that support the requirements
outlined in this document. This may include mockups or wireframes of user interfaces, entity-
relationship diagrams for the database, and system architecture diagrams.
 EXPERIMENT 3

AIM : To perform the function oriented diagram : DFD and structured chart for Fast Food
Billing System.

Requirements:
Software Requirements:

A tool for drawing DFDs (e.g., draw.io, Microsoft Visio).

Understanding of DFD symbols and notation.

A structured programming environment for creating a Structured Chart.

System Requirements:

Processes: Order Processing, Billing, Inventory Management.

Data Stores: Customer Data, Menu Items, Order Details.

External Entities: Customer, Kitchen Staff.

THEORY

Level 0: This level is also known as Context level DFD. These levels are Level 0 DFD . Both these
levels are
Level 1 DFD: At this level, more detailed information is given about the processing of the
student result management system. The DFD of this level is shown below:
STRUCTURE CHART
Structure chart represents hierarchical structure of modules. It breaks down the entire system
into the lowest functional modules, describing function of each module of a system into a
greater detail. Structure Chart partitions the system into the black boxes. Inputs are given to
the boxes and appropriated outputs are generated.
CONCLUSION:-

Level – 0 and Level – 1 Data Flow Diagram (DFD) and Structure Chart for Fast Food Billing
System have been drawn successfully.
 EXPERIMENT 4
AIM: Draw the Entity Relationship diagram for Fast Food Billing System.

Requirements:
Software Requirements:

A tool for drawing ER diagrams (e.g., draw.io, Lucidchart).

Basic understanding of database concepts.

System Requirements:

Entities: Customer, Order, Item, Payment.

Relationships: Customer places Order, Order contains Item, Order requires Payment.

THEORY:
Entity Relationship Diagrams are a major data modelling tool and will help organize the data in
your project into entities and define the relationships between the entities. This process has
proved to enable the analyst to produce a good database structure so that the data can be
stored and retrieved in a most efficient manner.

Entity Identification:
Identify the main entities involved in the fast food billing system based on requirements -
Customer, Order, Item, Payment.
Relationship Identification:
Determine the relationships between entities:

- A Customer places an Order.

- An Order contains Items.

- An Order requires Payment.

Attribute Specification:
Define attributes for each entity:

- Customer: CustomerID, Name, ContactNumber, Address.

- Order: OrderID, Date, TotalAmount.

- Item: ItemID, Name, Price.

- Payment: PaymentID, Amount, PaymentMethod.

Primary Keys and Foreign Keys:

Identify primary keys for each entity and define foreign keys where needed:

- CustomerID (Primary key in Customer, Foreign key in Order)

- OrderID (Primary key in Order, Foreign keys in Item and Payment)

Conclusion:
The entity relationship diagram was made successfully by following the steps described above.
 EXPERIMENT 5

AIM: To perform the user’s view analysis for the Fast Food Billling System : Use Case Diagram

REQUIREMENTS:
2.1 Software Requirements:

- Diagramming tool (e.g., Microsoft Visio, Lucidchart, or any UML modeling tool).

- Access to the specifications and requirements of the Fast Food Billing System.

2.2 Knowledge Requirements:

- Understanding of the fast food billing system requirements.

- Knowledge of UML (Unified Modeling Language) and Use Case Diagrams.

3. Theory:

A Use Case Diagram is a visual representation of the functional requirements of a system from
the user's perspective. It shows the different ways users can interact with the system and the
various use cases that the system must support.

4. Methodology:

4.1 Use Case Identification:

Identify and list the primary actors involved in the fast food billing system. These could include
customers, cashiers, managers, and kitchen staff.
4.2 Use Case Definition:

For each actor identified, define the use cases they participate in. Use cases should represent
specific functionalities or tasks that users can perform within the system. For example:

- **Customer:** Place Order, Make Payment

- **Cashier:** Process Order, Generate Receipt

- **Manager:** View Sales Report, Manage Menu

4.3 Use Case Relationships:

Identify relationships between actors and use cases. Determine how actors interact with the
system and each other. For instance, a Customer interacts with the system by placing an order
and making a payment.

4.4 Diagram Creation:

Use a UML modeling tool to create a Use Case Diagram. Represent actors as stick figures and
use ovals to depict use cases. Connect actors to use cases with lines to indicate interactions.

5. Observation and Analysis:

5.1 User Interaction Flow:

Examine the diagram to understand how users interact with the system. Identify the main paths
and alternative flows.
5.2 Completeness:

Ensure that all major functionalities and interactions are captured in the diagram. Identify any
gaps or missing use cases.

5.3 Clarity:

Assess the clarity of the Use Case Diagram. Ensure that it is easily understandable by
stakeholders, including developers, testers, and end-users.
6. Conclusion:

The Use Case Diagram provides a clear representation of the user's view of the Fast Food Billing
System. It highlights the key interactions between users and the system, aiding in the
understanding of functional requirements. This analysis will be valuable for further system
design and development, ensuring that user needs are well-addressed.
 EXPERIMENT 6
AIM: To draw the structural view diagram for the system :- Class Diagram, Object Diagram.

THEORY :-
CLASS DIAGRAM :-

A class diagram is a type of static structure diagram in the Unified Modeling Language (UML) that
represents the structure and organization of a system or software application in terms of classes, their
attributes, methods, and the relationships among them. Class diagrams are a fundamental part of
object-oriented modeling and provide a visual representation of the code structure.
OBJECT DIAGRAM :-

An object diagram in the Unified Modeling Language (UML) is a diagram that provides a snapshot of the
instances of classes in a system at a particular point in time. It shows the objects and their relationships
based on the classes defined in a class diagram. Object diagrams are particularly useful for illustrating
real-world scenarios or specific system states.