Software Engineering Assignment-1

Name- Debiprasad Mohapatra

Roll- 22/19031

q)-1 Assume that you have to build a software system that:

(i) allows students to submit their assignments

(ii) provides an environment to the teachers to evaluate them
(iii) generate the result with minimum input

Draw a context diagram and level 1 DFD of the above requirements of the system.

Elements:

● External Entities:
○ Students: Submit assignments.
○ Teachers: Evaluate assignments and review results.
○ Admin: Generate results, manage users.
● System (Assignment Submission & Evaluation System): The central system that
processes the submission of assignments, allows teachers to evaluate them, and
generates results.

The context diagram provides a high-level overview of the system, showing how external
entities (like students and teachers) interact with the system. The system is represented as a
single process, and external entities are connected to it via data flows.
Data Flow:

● From Student to System: Students submit assignments to the system.

● From System to Student: The system can send feedback or confirmations about the
submission.
● From Teacher to System: Teachers evaluate assignments and upload the results.
● From System to Teacher: The system provides the assignments for evaluation and
later provides results.

The Level 1 DFD breaks down the main system into subprocesses that represent the main
functionalities of the system.

Subprocesses:

Submit Assignment:
● Students upload or submit their assignments through a user interface. These
assignments are stored in the Assignments Database for future access and evaluation.

Evaluate Assignment:

● Teachers access the assignments stored in the Assignments Database. They evaluate
the assignments by grading them or providing feedback. These evaluations are then
stored in the Evaluations Database.

Generate Result:

● The system automatically generates results using the evaluations provided by the
teachers. It compiles the grades and feedback and provides a summary, which can be
viewed by the students.

Data Stores:

1. Assignments Database:
○ Stores all the assignments submitted by the students. This is where assignments
are fetched when teachers want to evaluate them.
2. Evaluations Database:
○ Stores the feedback and grades provided by the teachers after evaluating
assignments. The system accesses this database to generate the final results.
q)-2 Assume that you have to build a web-based order processing system. Draw a
context diagram and level-1 DFD of the system. Also develop a data dictionary for the
same.

Components of the Context Diagram:

1. Web-Based Order Processing System (Central Process):

○ This is the core system responsible for handling orders, managing payment
processes, maintaining inventory, and communicating with external stakeholders
like customers, admins, and suppliers.
 2. External Entities: These are the actors that interact with the system. Each external
entity communicates with the system to either send or receive data. They are not part of
the system itself but are essential for its functioning.
○ Customer:
■ Interaction: The customer places an order with the system.
■ Flow:
■ The system receives the Order Details from the customer.
■ After processing, the system sends back the Order Status to
inform the customer about the order progress (e.g., confirmation,
shipping, delivery).
○ Admin:
■ Interaction: Admins manage and oversee orders within the system.
■ Flow:
■ Admins provide inputs or adjustments to the system, such as
managing order details, updating statuses, or modifying inventory.
■ The system sends Order Status updates back to admins for
management purposes, ensuring they can monitor orders
effectively.
○ Payment Gateway:
■ Interaction: Handles the payment processing for customer orders.
■ Flow:
■ The system sends Payment Information to the payment gateway
to process the payment for an order.
■ The payment gateway returns the Payment Status to the system
once the transaction is completed, which is then communicated to
the customer or admin.
○ Supplier:
■ Interaction: Receives orders and supplies the necessary goods.
■ Flow:
■ The system sends Order Information to the supplier when items
need to be fulfilled.
■ The supplier, in return, provides confirmation of goods delivery or
updates the system with inventory or shipping details.

Data Flows:

● The arrows in the diagram represent the data flow between the system and the external
entities. These arrows are labeled to specify the type of information being exchanged,
such as "Places Order," "Sends Order Status," "Processes Payment," etc.
For example:
○ Customer → System: The customer sends order details to the system.
○ System → Customer: The system sends back order status updates.
○ System → Payment Gateway: The system forwards payment details to the
payment gateway.
 ○ Payment Gateway → System: The payment gateway informs the system
whether the payment has been processed successfully.

Data Interactions:

● Customer: Places order and receives status updates.

● Admin: Manages orders and gets updates.
● Payment Gateway: Processes payment and provides payment status.
● Supplier: Receives orders and updates inventory/shipment details.

Sub-processes:

1. Order Management: Handles customer orders and sends status updates.

2. Payment Processing: Interacts with the payment gateway to process payments.
3. Inventory Management: Notifies the supplier and updates the system.
4. Admin Management: Admin can view or manage orders.

Data Stores: Represented in light green and connected to processes:

● Order DB: Stores customer orders.

● Payment DB: Stores payment transactions.
● Inventory DB: Stores inventory information.
The Level-1 Data Flow Diagram (DFD) shows the detailed breakdown of processes involved in
the web-based order processing system. Here's an overview of the main entities and processes:

1. Customer:
○ The customer places an order.
○ The customer receives an order status update after placing the order.
2. Order Processing System (Main Process):
○ Receives the order from the customer.
○ Communicates with the payment gateway to process payments.
○ Sends the order status to the customer.
○ Interacts with the admin for managing orders and inventory.
3. Payment Gateway:
○ Processes the payment for the order made by the customer.
○ Sends a payment status update to the order processing system.
4. Admin:
○ Manages customer orders (e.g., updating status, managing inventory).
○ Keeps track of the supplier's interactions and updates the inventory accordingly.
5. Supplier:
○ Supplies products when inventory is low.
○ Receives inventory orders from the order processing system.

Relations:

● Customer ↔ Order Processing System: The customer sends an order to the system,
and the system updates the customer about the order status.
● Order Processing System ↔ Payment Gateway: The system sends payment
requests, and the gateway processes them and sends responses back.
● Order Processing System ↔ Admin: Admin manages orders, updates statuses, and
handles supplier-related inventory actions.
● Order Processing System ↔ Supplier: The system sends inventory orders to suppliers
when required.
Data Dictionary for Web-Based Order Processing System

Data Element Description Data Type Constraints

Customer ID Unique identifier for each Integer Primary Key, Auto-increment

customer

Customer Full name of the customer String Not Null, Length: 1-100
Name (varchar)

Email Email address of the customer String Not Null, Unique, Length:
(varchar) 5-255, Valid email format

Phone Contact number of the String Not Null, Length: 10-15,

Number customer (varchar) Numeric only
Order ID Unique identifier for each Integer Primary Key, Auto-increment
order

Order Date Date when the order was Date Not Null
placed

Order Status Current status of the order String Not Null, Length: 1-50
(e.g., Pending, Shipped) (varchar)

Total Total cost of the order Decimal Not Null, Positive value
Amount

Payment ID Unique identifier for each Integer Primary Key, Auto-increment

payment transaction

Payment Status of the payment (e.g., String Not Null, Length: 1-50
Status Successful, Failed) (varchar)

Payment Date when the payment was Date Not Null

Date made

Payment Method used for payment String Not Null, Length: 1-50
Method (e.g., Credit Card, PayPal) (varchar)

Supplier ID Unique identifier for each Integer Primary Key, Auto-increment

supplier

Supplier Name of the supplier String Not Null, Length: 1-100

Name (varchar)
Inventory ID Unique identifier for each Integer Primary Key, Auto-increment
inventory item

Product Name of the product String Not Null, Length: 1-100

Name (varchar)

Quantity Quantity of the product Integer Not Null, Positive value

available

Price per Price of the product per unit Decimal Not Null, Positive value
Unit

Order Details Description of the items in the String (text) Not Null
order

Shipping Address to which the order String (text) Not Null

Address will be shipped

Tracking Shipping tracking number String Length: 0-50 (Optional)

Number provided by the carrier (varchar)

Explanation of Key Data Elements:

1. Customer Data: Contains personal details to identify and contact customers.

2. Order Data: Includes the order itself, its status, and associated amounts.
3. Payment Data: Details of the payment process, including status and method.
4. Supplier Data: Information about suppliers who fulfill the orders.
5. Inventory Data: Manages product availability and pricing.
6. Shipping Information: Details on where the orders are sent and any tracking
information.