SOFTWARE ENGINEERING[IT301]

LAB FILE

Department of Computer Science & Engineering

AMITY SCHOOL OF ENGINEERING AND TECHNOLOGY
AMITY UNIVERSITY DUBAI

Batch: (2022-26) (Semester-6)

B. Tech (Program CSE)

Under the guidance of:

Faculty: Mrs.Asmita Mam

Lab Instructor: Ms. Fouqiah Jan

Submitted by:-

Name: Yash.N.Mistry
Enrollment No: A40105222019
University Email Address: [email protected]
Submission Date: //2025
 Declaration

I, Yash.N.Mistry, a student of B.Tech Computer Science and Engineering hereby affirm that the

lab file submitted for the course “Software Enginerring” to the Department of Computer Science

and Engineering, Amity university Dubai, is the result of my individual effort and original work.

I have abided by the academic standards and university guidelines in completing this lab file. I

acknowledge that academic integrity is of utmost importance, and I pledge to uphold honesty and

ethical practices in all academic tasks.

Sincerely,

Yash.N.Mistry
AUD18345
 File Index

S. NO. DATE PROGRAM NAME PAGE NO. SIGN

20/02/25 1
1. Create a use case diagram based on Online Shopping

27/02/25 Create a class diagram

2. 3
06/03/25 Create a Activity based diagrame based hospital
3. 5
management system
13/03/25 To make DFD of the hospital management system 8
4.

20/03/24 Create an entity relationship diagram for bakery 10

management system
5.

27/03/25 Create an exisiting and proposed diagram 12

6.
7.
8.
9.
10.
11.
12.

13.
14.

15.

16.

17.

18.

19.

20.

21.
22.
23.

24.

25.

26.
27.

28.
29.

30.

31.
Program 1 Date: 20/02/25

Aim:-

Create a use case diagram based on Online Shopping

Software Used: Draw.io

Theory:

Key Elements:

Users:-

Customer: Can add/remove items, checkout, review purchases, make payments, and check order status.

Sales Employee: Manages orders by retrieving them and sending them to the warehouse.

Warehouse Employee: Updates order status after processing.

Use Cases:-

Shopping Process: Adding/removing items, checking out, reviewing purchases.

Payment Process: Making a payment, which includes authentication when paying by card. Discount codes
are explicitly excluded.

Order Management: Sales employees get orders and send them to the warehouse, where warehouse
employees update the order status.

Relationships:-

Includes: Some processes (e.g., checkout includes login, card payment includes authentication).

Excludes: Discount codes are excluded from the payment process.

SOFTWARE ENGINEERING FILE 1

Output:-

SOFTWARE ENGINEERING FILE 2

Program 2 Date: 27/02/25

Aim:- Create a class diagram

Software Used: Draw.io

Theory:

1. Entities & Attributes

• Bank_Branch: Name, Phone

• Address_branch: Street, City, State, Postal Code, Bit_period
• Customer: ID_Cust, Name, Phone, Bit_period
• Address_customer: Street, City, State, Postal Code, Bit_period
• Account: Acc_No, Acc_type, Bit_period
• Balance: Value, Bit_period
• Transaction: Trans_ID, Type, Amount, Bit_period
• Loan: Loan_No, Amount, Type, Bit_period

2. Relationships

• 1:1 - Bank_Branch ↔ Address_branch, Customer ↔ Address_customer, Account ↔ Balance

• 1:M - Customer ↔ Account, Account ↔ Transaction
• 1:1 - Account ↔ Loan

3. Specialization & Inheritance

• Transaction Types: Deposit, Withdrawal, Transfer (target_source)

• Account Subclass: Withdrawal (Overdraft_Limit)

4. Functional Overview

• Customers own accounts managed by branches.

• Transactions occur on accounts: Deposit, Withdrawal, Transfer.
• Customers can have loans linked to accounts.
• Addresses are separately stored for branches & customers.

SOFTWARE ENGINEERING FILE 3

Output:-

SOFTWARE ENGINEERING FILE 4

Program 3 Date: 06/03/25

Aim:-

Create an activity diagram based on hospital management system

Software Used: Draw.io

Theory:

This flowchart illustrates the systematic process followed in hospitals for patient registration, test
results management, and discharge procedures.

1. Patient Registration

• The patient registers using their phone number.

• A unique ID is generated by the registration desk to maintain patient records.
• The patient receives a ticket from the registration desk to wait for the doctor.

2. Record Management

• The IT desk team manages all department records to ensure smooth hospital operations.

3. Test Results Processing

• Lab staff processes test results and records them in the system.
• A copy of the test result is generated.

4. Test Result Distribution

• A copy is sent to the doctor through internal hospital records.

• A copy is sent to the patient via email.

5. Doctor’s Duty Record

• The hospital maintains a duty chart for doctors.

• Doctors must log in and check out during their working hours, which is verified in the records.

6. Billing Process

• The billing department generates patient bills and receipts before discharge.

7. Patient Type Decision

• The patient is categorized as either:

SOFTWARE ENGINEERING FILE 5

 o In-patient: Requires hospital admission.
o Out-patient: Can leave after consultation and treatment.

8. In-Patient Billing

• In-patients pay extra charges for room and food before leaving.

9. Patient Discharge

• Once the process is completed, the patient leaves the hospital.

Output:-

SOFTWARE ENGINEERING FILE 6

Program 5 Date: 20/03/25

Aim: Create an entity relationship diagram for bakery management system

Software Used: Draw.io

Theory:

1. Customer

• Represents a person who places an order at the bakery.

• Attributes:
o Name – Customer’s name
o Contact Number – Phone number of the customer
o Address – Location of the customer

2. Order

• Represents the purchase request made by a customer.

• Relationships:
o A customer places an order.
o An order consists of multiple products.
o An order can be delivered.

3. Products

• Represents bakery items available for sale.

• Attributes:
o Name – Name of the bakery item (Cake, Pastry, Bread, etc.)
o Unit Price – Price of a single product

4. Other Products

• Additional bakery items that may be combined into special packages or offers.

5. Unique Customer

• Identifies customers who have placed orders, helping in order tracking.

6. Requests

• Represents the relationship between Orders and Products.

• An Order Requests Products, meaning a customer can order multiple bakery items.

7. Combination

SOFTWARE ENGINEERING FILE 7

 • Represents a special combo offer or packaged products.
• Some products may be grouped together as a special offer for customers.

8. Delivered

• Represents the delivery status of an order.

• A Unique Customer can have multiple deliveries.

Output:-

SOFTWARE ENGINEERING FILE 8

Program 6 Date: 27/03/25

Aim:- Create an exisiting and proposed diagram

Software Used: Draw.io

Theory:

Existing Diagram
Supply Chain: The restaurant interacts with a Supplier to Order Supplies. Upon receiving the
Supplies, a Supply Record is created and stored in the Supplies Register. The restaurant then
Make Payment to the Supplier, potentially after a Check. The received Supplies are used to
Make Dishes.

Sales Process: Customers Take Order, which is then used to Process Order. This process utilizes
Food Items derived from the made dishes. A Bill is then Produce Bill for the Customer. The
Customer provides Payment (Bill and Money), and a Receipt is generated. The sales information
(Sales) is recorded in the Record Sale process and stored in the Sale Register. The Customer
receives the Served Meal. Additionally, the restaurant can Order Supplies based on the sales data
recorded in the Sale Register.

Proposed Diagram

proposed DFD outlines an enhanced system for a restaurant, incorporating more detailed
processes and data stores. It separates the handling of Supplies (managed by a Supply Manager
and stored in Supplies Files) from the order and sales process. The system includes checks for
supply discrepancies and generates supply orders to the Supplier. Customer orders are processed,
bills are produced, and payments are recorded. The system also generates Account Reports and
Statistics for the Owner, feeding financial data into the Account File. A Man-Machine Boundary
suggests some processes are automated.

Output:-

SOFTWARE ENGINEERING FILE 9

Existing Diagram

Proposed Diagram

SOFTWARE ENGINEERING FILE 10

SOFTWARE ENGINEERING FILE 11