5.

Designing test cases for an e-commerce application like Flipkart

Designing test cases for an e-commerce application like Flipkart involves testing
various functionalities such as user registration, login, product search, product
details, cart management, checkout, payment, order tracking, and more. Below is a
comprehensive list of test cases categorized by functionality:

1. User Registration

Test
Description Precondition Steps Expected Result
Case ID
1. Navigate to the
registration page.
TC_REG_0 Register with valid User is not User is registered
2. Enter valid
1 details registered successfully.
details.
3. Submit.
1. Navigate to the
registration page.
TC_REG_0 Register with an Email already Error: "Email
2. Enter existing
2 existing email exists already registered."
email.
3. Submit.
1. Navigate to the
registration page.
TC_REG_0 Register with invalid Error: "Invalid email
None 2. Enter invalid
3 email format format."
email.
3. Submit.
1. Navigate to the
registration page.
Register with
TC_REG_0 2. Leave Error: "Please fill all
missing mandatory None
4 mandatory fields mandatory fields."
fields
blank.
3. Submit.

2. User Login
Test Case
Description Precondition Steps Expected Result
ID
1. Navigate to the
login page.
TC_LOGIN_ Login with valid User is User is logged in
2. Enter valid email
01 credentials registered successfully.
and password.
3. Submit.
1. Navigate to the
Login with login page.
TC_LOGIN_ User is Error: "Invalid
invalid 2. Enter valid email
02 registered credentials."
password and invalid password.
3. Submit.
1. Navigate to the
Login with login page.
TC_LOGIN_ Email is not Error: "Email not
unregistered 2. Enter unregistered
03 registered registered."
email email.
3. Submit.
1. Navigate to the
login page.
Login with Error: "Please enter
TC_LOGIN_ 2. Leave
missing None email and
04 email/password
credentials password."
blank.
3. Submit.

3. Product Search

Test Case Preconditi

Description Steps Expected Result
ID on
1. Enter a valid
TC_SEARCH_ Search for an product name in the Relevant products
None
01 existing product search bar. are displayed.
2. Click search.
1. Enter a non-
TC_SEARCH_ Search for a non- existing product Message: "No
None
02 existing product name. results found."
2. Click search.
1. Enter a product
name. Products matching
TC_SEARCH_ Search with filters
None 2. Apply filters (e.g., the filters are
03 (e.g., price range)
price range). displayed.
3. Click search.

4. Product Details
Test Preconditi
Description Steps Expected Result
Case ID on
1. Search for a
Product details (price,
TC_PD_0 View product Product product.
description, reviews) are
1 details exists 2. Click on the
displayed.
product.
1. Navigate to
TC_PD_0 Add product to cart Product product details. Product is added to the
2 from details page exists 2. Click "Add to cart.
Cart."
Availability status is
TC_PD_0 Check product Product 1. Navigate to
displayed (e.g., "In
3 availability exists product details.
Stock").

5. Cart Management

Test Case
Description Precondition Steps Expected Result
ID
1. Search for a
TC_CART_ Add a product to product. Product is added to
Product exists
01 the cart 2. Click "Add to the cart.
Cart."
1. Navigate to
the cart.
TC_CART_ Remove a product Product is in Product is removed
2. Click
02 from the cart the cart from the cart.
"Remove" for a
product.
1. Navigate to
the cart.
TC_CART_ Update product Product is in Quantity is updated
2. Change the
03 quantity in the cart the cart successfully.
quantity.
3. Click "Update."
1. Navigate to
Proceed to
TC_CART_ Cart is not the cart. User is redirected to
checkout from the
04 empty 2. Click "Proceed the checkout page.
cart
to Checkout."

6. Checkout and Payment

 Preconditio Expected
Test Case ID Description Steps
n Result
1. Add product
to cart.
2. Proceed to
Place an order with
TC_CHECKOUT_ User is checkout. Order is placed
valid payment
01 logged in 3. Enter valid successfully.
details
payment
details.
4. Place order.
1. Add product
to cart.
2. Proceed to
TC_CHECKOUT_ Place an order with User is checkout. Error: "Payment
02 invalid payment logged in 3. Enter invalid failed."
payment
details.
4. Place order.
1. Add product
to cart.
2. Proceed to Discount is
TC_CHECKOUT_ Apply a valid coupon User is
checkout. applied
03 code logged in
3. Apply valid successfully.
coupon code.
4. Place order.
1. Add product
to cart.
2. Proceed to
TC_CHECKOUT_ Apply an invalid User is Error: "Invalid
checkout.
04 coupon code logged in coupon code."
3. Apply invalid
coupon code.
4. Place order.

7. Order Tracking
Test Case Preconditio
Description Steps Expected Result
ID n
1. Navigate to "My
TC_ORDER_ Track an existing Order is Orders." Order status is
01 order placed 2. Click "Track displayed.
Order."
1. Navigate to "My
Orders."
TC_ORDER_ Track a non- Error: "Order not
None 2. Enter invalid
02 existing order found."
order ID.
3. Click "Track."

8. Logout

Test Case Preconditio

Description Steps Expected Result
ID n
TC_LOGOUT_ Logout from the User is 1. Click on the User is logged out
01 application logged in "Logout" button. successfully.

9. Edge Cases

Test Case Expected

Description Precondition Steps
ID Result
1. Search for an out-
TC_EDGE_ Add out-of-stock Product is out of-stock product. Error: "Product is
01 product to cart of stock 2. Click "Add to out of stock."
Cart."
1. Navigate to the
TC_EDGE_ Checkout with an cart. Error: "Your cart
Cart is empty
02 empty cart 2. Click "Proceed to is empty."
Checkout."
6. Designing test cases for mobile application (consider any example from
Appstore)

Designing test cases for a mobile application involves testing various functionalities
such as installation, login, navigation, features, performance, and usability.
Let’s take the example of the Instagram mobile app (available on the App Store)
and design test cases for it.

1. Installation and Launch

Test Case Preconditio

Description Steps Expected Result
ID n
1. Open App Store.
Install the app
TC_INSTALL_ App is not 2. Search for App is installed
from the App
01 installed Instagram. successfully.
Store
3. Click "Install."
1. Tap the
TC_INSTALL_ Launch the app App is App launches
Instagram icon on
02 after installation installed successfully.
the home screen.
1. Turn off internet. App launches with a
TC_INSTALL_ Launch the app App is
2. Tap the "No Internet"
03 without internet installed
Instagram icon. message.

2. User Registration and Login

Test Case Preconditio

Description Steps Expected Result
ID n
1. Open the app.
Login with 2. Enter valid
TC_LOGIN_ User is User is logged in
valid email/username and
01 registered successfully.
credentials password.
3. Tap "Log In."
1. Open the app.
Login with 2. Enter valid
TC_LOGIN_ User is Error: "Incorrect
invalid email/username and
02 registered password."
password invalid password.
3. Tap "Log In."
1. Open the app. Error: "The username
Login with
TC_LOGIN_ Email is not 2. Enter unregistered you entered doesn't
unregistered
03 registered email. belong to an
email
3. Tap "Log In." account."
1. Open the app.
Login with 2. Leave
TC_LOGIN_ Error: "Please enter
missing None email/password
04 email and password."
credentials blank.
3. Tap "Log In."
3. Navigation

Test Preconditio Expected

Description Steps
Case ID n Result
TC_NAV_0 Navigate to the User is 1. Tap the "Home" Home screen is
1 Home screen logged in icon at the bottom. displayed.
TC_NAV_0 Navigate to the User is 1. Tap the "Search" Explore screen is
2 Explore screen logged in icon at the bottom. displayed.
TC_NAV_0 Navigate to the User is 1. Tap the "Profile" Profile screen is
3 Profile screen logged in icon at the bottom. displayed.

4. Posting Content

Test Case Preconditio

Description Steps Expected Result
ID n
1. Tap the "+"
icon.
2. Select a
TC_POST_0 Upload a photo with User is Photo is posted
photo.
1 a caption logged in successfully.
3. Add a
caption.
4. Tap "Share."
1. Tap the "+"
icon.
2. Select a
TC_POST_0 Upload a video with User is Video is posted
video.
2 a caption logged in successfully.
3. Add a
caption.
4. Tap "Share."
1. Tap the "+"
icon.
TC_POST_0 Upload without User is Error: "Please select a
2. Skip media
3 media logged in photo or video."
selection.
3. Tap "Share."
5. Interacting with Posts

Preconditio
Test Case ID Description Steps Expected Result
n
1. Navigate to a
TC_INTERACT_ User is post. Post is liked
Like a post
01 logged in 2. Tap the "Like" successfully.
button.
1. Navigate to a
post.
TC_INTERACT_ Comment on a User is 2. Tap Comment is added
02 post logged in "Comment." successfully.
3. Enter text.
4. Tap "Post."
1. Navigate to a
post.
TC_INTERACT_ User is 2. Tap the "Share" Post is shared
Share a post
03 logged in button. successfully.
3. Select a
platform.

6. Stories

Test Case Descriptio Preconditio

Steps Expected Result
ID n n
1. Tap the "+" icon on the
TC_STORY_ Upload a User is Stories bar. Story is uploaded
01 story logged in 2. Select a photo/video. successfully.
3. Tap "Your Story."
TC_STORY_ User is 1. Tap on a user's story in Story is displayed
View a story
02 logged in the Stories bar. successfully.
1. View a story.
2. Tap the "Send
TC_STORY_ React to a User is Reaction is sent
Message" button.
03 story logged in successfully.
3. Enter text.
4. Tap "Send."
7. Direct Messaging

Test Case
Description Precondition Steps Expected Result
ID
1. Tap the "DM"
icon.
Send a text User is logged Message is sent
TC_DM_01 2. Select a user.
message in successfully.
3. Enter text.
4. Tap "Send."
1. Tap the "DM"
icon.
2. Select a user.
Send a photo via User is logged Photo is sent
TC_DM_02 3. Tap the camera
DM in successfully.
icon.
4. Select a photo.
5. Tap "Send."
1. Tap the "DM"
icon.
2. Select a user.
Send a video via User is logged Video is sent
TC_DM_03 3. Tap the camera
DM in successfully.
icon.
4. Select a video.
5. Tap "Send."

8. Notifications

Test Case Preconditio Expected

Description Steps
ID n Result
TC_NOTIF_ Receive a like User is 1. Like a post from Notification is
01 notification logged in another account. received.
Receive a
TC_NOTIF_ User is 1. Comment on a post Notification is
comment
02 logged in from another account. received.
notification
TC_NOTIF_ Turn off User is 1. Go to Settings. Notifications are
03 notifications logged in 2. Turn off notifications. disabled.
9. Performance and Usability

Test Case Preconditi

Description Steps Expected Result
ID on
TC_PERF_0 App performance Battery is 1. Use the app with App functions
1 under low battery low low battery. normally.
App loads content
TC_PERF_0 App performance Internet is 1. Use the app with
with a loading
2 with slow internet slow slow internet.
indicator.
App usability in 1. Rotate the device
TC_USAB_ App adjusts layout
portrait and None to portrait and
01 accordingly.
landscape landscape modes.

10. Logout

Test Case Preconditio

Description Steps Expected Result
ID n
1. Go to Profile.
2. Tap the
TC_LOGOUT_ Logout from the User is logged User is logged out
menu icon.
01 app in successfully.
3. Tap "Log
Out."
3.Consider any application calculate effort using FP oriented estimational
model

Let’s consider a Food Delivery Mobile Application (e.g., Uber Eats or Zomato) and
calculate the effort using the Function Point (FP) Oriented Estimation Model.
The Function Point Analysis (FPA) is a method to estimate the size of software based
on its functionality, which can then be used to estimate effort, cost, and time.

Steps to Calculate Effort Using FP-Oriented Estimation

1. Identify and Categorize Functions:

o Classify functions into External Inputs (EI), External Outputs
(EO), External Inquiries (EQ), Internal Logical Files (ILF),
and External Interface Files (EIF).

2. Assign Complexity Weights:

o Determine the complexity of each function (Low, Average, High) and
assign weights based on the FP counting standards.

3. Calculate Unadjusted Function Points (UFP):

o Multiply the number of functions in each category by their respective
weights and sum them up.

4. Determine the Value Adjustment Factor (VAF):

o Evaluate 14 General System Characteristics (GSCs) on a scale of 0 to 5
and calculate the VAF.

5. Calculate Adjusted Function Points (AFP):

o Multiply UFP by VAF.

6. Estimate Effort:
o Use the formula: Effort (Person-Hours) = AFP × Productivity
Factor.

Example: Food Delivery Application

1. Identify and Categorize Functions

Cou
Function Type Description
nt

User registration, login, order placement, payment, feedback

External Inputs (EI) 5
submission

External Outputs (EO) Order confirmation, delivery status, invoice generation, 4

 Cou
Function Type Description
nt

promotional offers

External Inquiries Search restaurants, view menu, track order, check order
4
(EQ) history

Internal Logical Files User profiles, restaurant details, menu items, order history,
5
(ILF) payment records

External Interface
Payment gateway integration, map services, restaurant APIs 3
Files (EIF)

2. Assign Complexity Weights

Lo Avera Hig
Function Type
w ge h

External Inputs (EI) 3 4 6

External Outputs (EO) 4 5 7

External Inquiries (EQ) 3 4 6

Internal Logical Files

7 10 15
(ILF)

External Interface
5 7 10
Files (EIF)

Assume the complexity for all functions is Average.

3. Calculate Unadjusted Function Points (UFP)

Cou Weig Tot
Function Type
nt ht al

External Inputs (EI) 5 4 20

External Outputs (EO) 4 5 20

External Inquiries (EQ) 4 4 16

Internal Logical Files

5 10 50
(ILF)
 Cou Weig Tot
Function Type
nt ht al

External Interface
3 7 21
Files (EIF)

Total UFP 127

4. Determine the Value Adjustment Factor (VAF)

Evaluate the 14 General System Characteristics (GSCs) on a scale of 0 to 5. For

simplicity, assume the total degree of influence (TDI) is 42.

 VAF = 0.65 + (0.01 × TDI)

 VAF = 0.65 + (0.01 × 42) = 1.07

5. Calculate Adjusted Function Points (AFP)

 AFP = UFP × VAF

 AFP = 127 × 1.07 = 135.89 (approx. 136 FP)

6. Estimate Effort

Assume the Productivity Factor is 20 hours per FP (this can vary based on team
experience, tools, and technology).

 Effort (Person-Hours) = AFP × Productivity Factor

 Effort = 136 × 20 = 2,720 Person-Hours

If a team of 5 developers works 8 hours a day:

 Total Days = Effort / (Team Size × Hours per Day)

 Total Days = 2,720 / (5 × 8) = 68 Days

Summary

 Unadjusted Function Points (UFP): 127

  Value Adjustment Factor (VAF): 1.07

 Adjusted Function Points (AFP): 136

 Effort: 2,720 Person-Hours (approx. 68 days for a team of 5)

This estimation can be refined further by adjusting the complexity weights, GSCs,
and productivity factor based on the specific project and team

2.Consider any application using COCOMO model estimate the effort

Let’s consider a Project Management Software (e.g., Trello or Asana) and

estimate the effort using the COCOMO (Constructive Cost Model). COCOMO is a
widely used algorithmic software cost estimation model that estimates effort, cost,
and schedule based on the size of the software and other project-specific factors.

Steps to Calculate Effort Using COCOMO

1. Determine the Size of the Software:

o Estimate the size of the software in Lines of Code (LOC) or Function
Points (FP).

o For this example, we’ll assume the size is 10,000 LOC.

2. Select the COCOMO Model:

o Basic COCOMO: Estimates effort and schedule based on size and mode
(Organic, Semi-Detached, Embedded).

o Intermediate COCOMO: Adds cost drivers to refine the estimate.

o Detailed COCOMO: Incorporates phase-wise effort distribution.

We’ll use the Intermediate COCOMO model.

3. Determine the Mode:

o Organic: Small, simple projects with experienced teams.

o Semi-Detached: Medium-sized projects with mixed experience levels.

o Embedded: Large, complex projects with strict requirements.

For this example, we’ll assume the project is Semi-Detached.

 4. Calculate Effort:
o Use the formula: Effort (Person-Months) = a × (Size)^b × EAF.
 a and b are constants based on the mode.

 EAF is the Effort Adjustment Factor based on cost drivers.

5. Calculate Development Time:

o Use the formula: Time (Months) = c × (Effort)^d.
 c and d are constants based on the mode.

Example: Project Management Software

1. Size of the Software

 Size = 10,000 LOC

2. Select the COCOMO Model

 We’ll use the Intermediate COCOMO model.

3. Determine the Mode

 Mode = Semi-Detached

4. Constants for Semi-Detached Mode

 a = 3.0, b = 1.12 (from COCOMO table)

 c = 2.5, d = 0.35 (from COCOMO table)

5. Effort Adjustment Factor (EAF)

The EAF is calculated by evaluating 15 cost drivers (e.g., product complexity, team
experience, reliability requirements). For simplicity, assume the EAF = 1.2 (slightly
higher due to moderate complexity and team experience).

6. Calculate Effort
 Effort (Person-Months) = a × (Size)^b × EAF

 Effort = 3.0 × (10,000)^1.12 × 1.2

First, calculate (10,000)^1.12:

 (10,000)^1.12 ≈ 16,218

Now, calculate Effort:

 Effort = 3.0 × 16,218 × 1.2 ≈ 58,384.8 Person-Months

7. Calculate Development Time
 Time (Months) = c × (Effort)^d

 Time = 2.5 × (58,384.8)^0.35

First, calculate (58,384.8)^0.35:

 (58,384.8)^0.35 ≈ 17.5

Now, calculate Time:

 Time = 2.5 × 17.5 ≈ 43.75 Months

8. Team Size
 Team Size = Effort / Time

 Team Size = 58,384.8 Person-Months / 43.75 Months ≈ 1,334 Persons

Summary

 Size of Software: 10,000 LOC

 Mode: Semi-Detached

 Effort: 58,384.8 Person-Months

 Development Time: 43.75 Months

 Team Size: 1,334 Persons

Refinement with Cost Drivers

If we refine the estimate by considering specific cost drivers (e.g., higher team
experience, better tools), the EAF can be adjusted, leading to a more accurate
estimate. For example:

 If EAF = 1.0, Effort = 3.0 × 16,218 × 1.0 ≈ 48,654 Person-Months.

 If EAF = 1.5, Effort = 3.0 × 16,218 × 1.5 ≈ 72,981 Person-Months.

This example demonstrates how to use the COCOMO model to estimate effort for a
project management software application.

Test cases are a fundamental part of software testing in software engineering. They
are used to validate the functionality of a system and ensure that it behaves as
expected under various conditions. A test case typically includes the following
components:

1. Test Case ID: A unique identifier for the test case.

2. Test Case Description: A brief explanation of what the test case is verifying.
3. Preconditions: Any conditions that must be true before executing the test
case.
4. Test Steps: The specific steps to follow when executing the test case.
5. Test Data: The input data for the test case.
6. Expected Results: The expected output or behavior of the system based on
the given test data.
7. Postconditions: Any conditions that should be true after executing the test
case.
8. Actual Results: The results observed when the test case is executed.
9. Status: Whether the test passed, failed, or is blocked.

1. (i). Do the requirement analysis and prepare SRS

Requirement Analysis and Software Requirements Specification

(SRS)

1. Introduction

The purpose of this document is to outline the requirements for the development of a
software system. The system aims to address specific user needs and provide a
comprehensive solution to the identified problem.

2. Objectives
 To define the functional and non-functional requirements of the system.

 To provide a clear understanding of the system's scope and constraints.

 To serve as a reference for stakeholders during the development process.

3. Scope

The system will be designed to:

 Automate specific tasks to improve efficiency.

 Provide a user-friendly interface for ease of use.

 Ensure data security and integrity.

4. Stakeholders
 Users: End-users who will interact with the system.

 Developers: Team responsible for system development.

 Project Managers: Oversee the project timeline and deliverables.

 Clients: Entities funding the project and expecting the final product.

5. Functional Requirements
1. User Authentication:
o The system shall allow users to log in using a username and password.

o The system shall provide password recovery options.

2. Data Management:
o The system shall allow users to create, read, update, and delete records.

o The system shall validate data inputs to ensure accuracy.

3. Reporting:
o The system shall generate reports based on user-defined criteria.

o Reports shall be exportable in multiple formats (PDF, Excel).

4. Notifications:
o The system shall send email notifications for important events.

o Users shall be able to configure notification preferences.

6. Non-Functional Requirements
1. Performance:
o The system shall handle up to 10,000 concurrent users without performance
degradation.

o Response time for any action shall not exceed 2 seconds.

2. Security:
o The system shall encrypt sensitive data both in transit and at rest.

o The system shall implement role-based access control.

3. Usability:
o The system shall have an intuitive user interface.

o The system shall provide tooltips and help documentation.

4. Scalability:
o The system shall be scalable to accommodate future growth in user base and
data volume.
7. System Models
1. Use Case Diagram:
o Illustrates interactions between users and the system.

2. Entity-Relationship Diagram (ERD):

o Represents the data model and relationships between different entities.

3. Data Flow Diagram (DFD):

o Shows how data moves through the system.

8. Constraints
 The system must be developed within a budget of $500,000.

 The system must be completed and deployed within 12 months.

 The system must comply with relevant industry regulations and standards.

9. Assumptions and Dependencies

 It is assumed that all necessary hardware and software infrastructure will be available.

 The project is dependent on timely delivery of third-party components.

10. Glossary
 SRS: Software Requirements Specification.

 ERD: Entity-Relationship Diagram.

 DFD: Data Flow Diagram.

11. References
 IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements
Specifications.

This SRS document provides a comprehensive overview of the requirements for the software
system. It serves as a foundation for the design, development, and testing phases of the
project.

1. (Ii).Draw E-R Diagrams DFD, CFD and structured charts for the project

Creating Entity-Relationship Diagrams (ERD), Data Flow Diagrams (DFD), Control

Flow Diagrams (CFD), and Structured Charts requires visual representation, which
cannot be directly drawn in text format. However, I can describe how to create these
diagrams and provide guidance on their structure and components. You can use tools
like Lucidchart, Draw.io, Microsoft Visio, or Miro to create these diagrams.
1. Entity-Relationship Diagram (ERD)

An ERD represents the data model of the system, showing entities, attributes, and
relationships.

Example for a User Management System:

 Entities:
o User
 Attributes: UserID (PK), Username, Password, Email, Role

o Role
 Attributes: RoleID (PK), RoleName

o Permission
 Attributes: PermissionID (PK), PermissionName

o UserRole
 Attributes: UserID (FK), RoleID (FK)

o RolePermission
 Attributes: RoleID (FK), PermissionID (FK)

 Relationships:
o A User can have one or more Roles (Many-to-Many relationship via UserRole).

o A Role can have one or more Permissions (Many-to-Many relationship

via RolePermission).

ERD Structure:
[User] ----(has)---- [UserRole] ----(belongs to)---- [Role]
[Role] ----(has)---- [RolePermission] ----(belongs to)---- [Permission]

2. Data Flow Diagram (DFD)

A DFD shows how data flows through the system. It includes processes, data stores, external
entities, and data flows.

Example for a User Management System:

 Level 0 (Context Diagram):
o External Entities: User, Admin

o Process: User Management System

o Data Stores: User Database, Role Database, Permission Database

 Level 1 (Detailed DFD):

o Processes:
1. Authenticate User: Validate username and password.
 2. Manage Roles: Assign or revoke roles for users.

3. Manage Permissions: Assign or revoke permissions for roles.

o Data Stores:
 User Database: Stores user details.

 Role Database: Stores role details.

 Permission Database: Stores permission details.

o Data Flows:
 User credentials → Authenticate User → User Database.

 Role assignment → Manage Roles → Role Database.

 Permission assignment → Manage Permissions → Permission Database.

DFD Structure:
[User] --> (Authenticate User) --> [User Database]
[Admin] --> (Manage Roles) --> [Role Database]
[Admin] --> (Manage Permissions) --> [Permission Database]

3. Control Flow Diagram (CFD)

A CFD represents the flow of control between processes or modules in the system.

Example for a User Management System:

 Processes:
1. Login: User enters credentials.

2. Validate Credentials: System checks if credentials are valid.

3. Check Role: System determines the user's role.

4. Grant Access: System grants access based on role and permissions.

CFD Structure:
[Login] --> [Validate Credentials] --> [Check Role] --> [Grant Access]

4. Structured Chart

A structured chart represents the hierarchical structure of modules in the system.

Example for a User Management System:

 Top-Level Module: User Management System
o Sub-Modules:
1. Authentication Module
 Validate Credentials
  Generate Session Token

2. Role Management Module

 Assign Role

 Revoke Role

3. Permission Management Module

 Assign Permission

 Revoke Permission

4. Reporting Module
 Generate User Report

 Generate Role Report

Structured Chart Structure:

User Management System
├── Authentication Module
│ ├── Validate Credentials
│ └── Generate Session Token
├── Role Management Module
│ ├── Assign Role
│ └── Revoke Role
├── Permission Management Module
│ ├── Assign Permission
│ └── Revoke Permission
└── Reporting Module
├── Generate User Report
└── Generate Role Report

Tools to Create Diagrams:

1. Lucidchart: Great for ERDs, DFDs, and structured charts.

2. Draw.io: Free and easy-to-use tool for creating diagrams.

3. Microsoft Visio: Professional tool for creating detailed diagrams.

4. Miro: Collaborative tool for creating diagrams with teams.

Summary:

 ERD: Focuses on entities, attributes, and relationships.

 DFD: Focuses on data flow between processes, data stores, and external entities.

 CFD: Focuses on the control flow between processes.

 Structured Chart: Focuses on the hierarchical structure of modules.