0% found this document useful (0 votes)
3 views41 pages

Grocery Store

Uploaded by

aasuanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views41 pages

Grocery Store

Uploaded by

aasuanu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 41

Employee Management

Employee Management
Employee Management
Lok Jagruti Kendra University
(LJ)

Developed By:
1. Mansuri Ayman Abidbhai 21018501210029
2. Patel Anushka Ajay 21018501210040
3. Patel Ashka Ajay 21018501210041

Group No: - 7

Under the Guidance of:


Prof. Harsh Shah

Submitted To:
L.J. INSTITUTE OF COMPUTER APPLICATION

Page 1 | 41
Employee Management

L.J. INSTITUTE OF COMPUTER APPLICATIONS


Sarkhej Road, S.G. Highway, Ahmedabad

CERTIFICATE

Enrolment No: 21018501210029 Seat No: _____________

This is to certify that Mrs. Mansuri Ayman Abidbhai of Integrated


Master of Computer Applications, Semester 8 has satisfactorily
completed his Employee Management Project under the supervision
of ProfHarsh.

Internal Guide Name: Signature


Prof Harsh

Date of Submission:
29-04-2023

Page 2 | 41
Employee Management

L.J. INSTITUTE OF COMPUTER APPLICATIONS


Sarkhej Road, S.G. Highway, Ahmedabad

CERTIFICATE

Enrolment No: 21018501210040 Seat No: _____________

This is to certify that Mrs. Patel Anushka Ajay of Integrated Master


of Computer Applications, Semester 8 has satisfactorily completed his
Project titled Employee Management under the supervision of
Prof Harsh

Internal Guide Name: Signature


Prof Harsh

Date of Submission:
29-04-2023

Page 3 | 41
Employee Management

L.J. INSTITUTE OF COMPUTER APPLICATIONS


Sarkhej Road, S.G. Highway, Ahmedabad

CERTIFICATE

Enrolment No: 21018501210041 Seat No: _____________

This is to certify that Mrs. Patel Ashka Ajay of Integrated Master of


Computer Applications, Semester 8 has satisfactorily completed his
Project titled Employee Management under the supervision of
Prof Hasrh

Internal Guide Name: Signature


Prof Harsh

Date of Submission:
29-04-2023

Page 4 | 41
Employee Management

Sr. No. TABLE OF CONTENTS Page No.

1. INTRODUCTION 6

1.1 Existing System 6

1.2 Need for the New System 6

1.3 Objective of the New System 7

1.4 Problem Definition 7

1.5 Core Components 7

1.6 Project Profile 8

1.7 Assumptions and Constraints 8

1.8 Advantages and Limitations of the Proposed System 9

2. REQUIREMENT DETERMINATION & ANALYSIS 10

2.1 Requirement Determination 10

2.2 Targeted Users 10

2.3 Timeline Chart 11

3. SYSTEM DESIGN 12

3.1 Use-Case 12

3.2 Class Diagram 15

3.3 Interaction Diagram 16

3.4 Activity Diagram 23

3.5 Data Dictionary 28

4. DEVELOPMENT 32

4.1 Coding Standard 33

4.2 Screenshots 35

5. AGILE DOCUMENTATION 36

5.1 Agile Project Charter 38

5.2 Agile Project Road / Schedule 39

Page 5 | 41
Employee Management

5.3 Agile Project Plan 40

5.4 Agile User Story 41

5.5 Agile Release Plan 42

5.6 Agile Spring Backlog 43

5.7 Agile Test Plan 44

5.8 Earned Value & Burned Charts 45

6. PROPOSED ENHANCEMENTS 49

7. CONCLUSION 50

8. BIBLIOGRAPHY 50

Page 6 | 41
Employee Management

1. Introduction:

The Employee Management System is a web application developed using the MERN stack
(MongoDB, Express.js, React.js, and Node.js) to streamline employee management. It
simplifies tasks like handling employee records, tracking attendance, assigning roles, and
managing payroll. With a user-friendly interface and role-based access control, it ensures data
security and automation, reducing manual efforts and enhancing efficiency. Designed for
businesses of all sizes, the system improves workforce management and supports better
decision-making through analytics and reporting tools.

1.1 Existing System:

Many organizations still use manual processes or outdated systems to manage employee data
and workflows. These systems often lack centralization, are prone to errors, and do not
provide sufficient features for streamlined operations, such as leave management, profile
management, or secure role-based access. For example, users cannot self-manage their data,
and super admin functionalities are often scattered or absent in such systems.

1.2 Need for the new system:

 The need for a new system arises from the limitations of existing systems in managing
employee details, leave requests, and role-based functionalities. Organizations require
a modern solution that offers:
 Secure user login and role-specific access.
 Centralized employee data storage.
 Streamlined workflows for leave management and profile updates.
 Efficient data handling and editing options for super admins. This project aims to
provide an all-in-one, user-friendly platform to address these needs.

Page 7 | 41
Employee Management

1.3 Objective of the New System

The primary objective of the proposed system is to create an employee management


platform that:

 Offers secure user authentication and role-based access for normal users and super
admins.
 Enables profile management, including editing usernames, passwords, and uploading
profile pictures.
 Simplifies leave management by allowing users to apply for leaves and track their
leave history, while providing super admins with tools to approve or reject requests.
 Provides super admins with complete control over employee data, including the
ability to view and edit all employee records.

1.4 Problem Definition

Current systems face the following challenges:


 Lack of role-specific access control, leading to security and data privacy issues.
 Inefficient leave management, resulting in delays and mismanagement.
 The absence of a centralized database makes employee data management
cumbersome.
 There are limited self-service options for users to update their profiles. The proposed
system addressess these challenges by incorporating modern web-based technologies
and intuitive user interfaces.

Page 8 | 41
Employee Management

1.5 Core Component:

The core components of the project include:

 Authentication Module: Secure login and role-based access control (normal users and
super admins).
 Profile Management:
 Users can edit their username, and password, and upload profile pictures.
 Super admins can view and edit all employee profiles.
 Leave Management:
 Users can apply for leaves and track their leave history.
 Super admins can approve or reject leave requests.
 Database: MongoDB for storing user and leave data securely.
 Frontend: React.js for a responsive and interactive user interface.
 Backend: Node.js and Express.js for handling API requests and business logic.

1.6 Project Profile:

Project Title Employee Management

Duration 36 Days

Project Internal Guide Prof. HarshShah

Front End React.JS

Framework Express.Js

Backend/Database Node.Js/MongoDB

Operating System Window 11

Page 9 | 41
Employee Management

1.7 Advantages and Limitations of the Proposed System:


Advantages:
 Secure and role-based access ensures data privacy.
 Self-service options for users, reducing the administrative workload.
 Centralized leave management and profile editing streamline workflows.
 Super admins have full control over employee data, enabling better decision-making.

Limitations:
 Initial setup, including data migration, may require effort and time.
 Internet dependency could limit offline accessibility.
 The learning curve for users transitioning from manual systems.

1.8 Assumptions and Constraints:

❖ Assumptions:
 Users have basic knowledge of logging into and navigating web-based systems.
 Super admins will manage sign-up and user creation for added security.
 Internet connectivity will be stable for all users to access the platform.

❖ Constraints:
 Budget constraints may limit advanced features or third-party integrations.
 The system is dependent on internet availability for real-time operations.

Page 10 | 41
Employee Management

2. Requirement Determination & Analysis:

2.1. Requirement Determination:

To gather requirements for the Employee Management System project, the following
approaches were considered:

1. User Interaction: Engaging with HR personnel and company administrators to


understand their challenges and needs in managing employee data and processes.

2. Similar System Study: Analyzing existing platforms like BambooHR, Zoho People,
and Gusto to identify key features and user-friendly designs.

3. Questionnaire/Survey: Collecting feedback from potential users on desired


functionalities and pain points in traditional employee management systems.

Chosen Approach: A combination of user interaction and similar system study was
selected to balance practical insights with established best practices.

 Hardware Requirements

The system requires the following minimum hardware specifications for optimal
development and deployment:

 Processor: Intel(R) Core (TM) i5-6040U CPU @ 2.3GHz or higher

 Memory: 4GB RAM (8GB recommended for smoother multitasking)

 Storage: 256 GB SSD or higher

 Software Requirements

The following software stack will be used to develop and deploy the application:

 Operating System: Windows 10 or higher / macOS / Linux

 Database: MongoDB for scalable and efficient data handling

 Development Tool: Visual Studio Code, chosen for its robust development
environment

 Framework: MERN Stack (MongoDB, Express.js, React.js, Node.js) for modern


and scalable web development

Page 11 | 41
Employee Management

2.2. Targeted user:

The Employee Management System is designed for the following primary roles:

1. HR/Admin

o Responsibilities:

 Manage employee records (add/update/delete).

 Track attendance and generate performance reports.

 Oversee payroll processing and role-based access control.

 Handle announcements and employee feedback.

2. Employees

o Features:

 Access personal profiles and update contact information.

 View attendance records, leave status, and salary details.

 Receive company announcements and provide feedback.

 Submit leave requests and track their approval status.

2.3. Proposed Timeline Chart:

Month January February


Weeks 1 2 3 4 1 2
Planning

Analysis

Design

Coding

Testing
Implementation
Documentation

Page 12 | 41
Employee Management

3. System Design:
3.1. Use Case Diagram:

Page 13 | 41
Employee Management

3.2. Class Diagram:

Page 14 | 41
Employee Management

3.3. Interaction Diagram:

Page 15 | 41
Employee Management

3.4. Activity Diagram:

Page 16 | 41
Employee Management

5. Data dictionary:
Sr.No Table Name

1 Employee

2 Department

3 Role

4 Salary

5 Attendance

6 Leave

7 Project

8 Task

9 Performance Review

10 ContactInfo Table

11 Account

Page 17 | 41
Employee Management

TABLE NAME: USERS

TABLE DESCRIPTION: STORES THE BASIC DETAILS INCLUDING USER ID, USER NAME
USER EMAIL ID.

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION SAMPLE DATA


<WITH SIZE>
USER_ID BIGINT (20) PRIMARY- AUTO-INCREMENT 1
KEY
NAME VARCHAR NOT NULL NAME OF THE USER AMAAN
(191)
EMAIL VARCHAR NOT NULL EMAIL ID USER A@GMAIL.COM
(191)
PASSWORD VARCHAR NOT NULL PASSWORD OF USET ********
(191)
Registration: It Stores the detail of all the users.

TABLE NAME: PRODUCTS

TABLE DESCRIPTION: STORES THE BASIC DETAILS INCLUDING ID, NAME, AND IMAGE OF
PRODUCT.

FIELD NAME DATA CONSTRAINT DESCRIPTION SAMPLE DATA


TYPE
(WITH
SIZE)
PRODUCT_ID BIGINT PRIMARY PRODUCTID 1
(20) KEY
PRODUCT _NAME VARCHAR NOT NULL NAME OF THE CLOVES
(191) PRODUCT
PRODUCT _PRICE VARCHAR NOT NULL PRICE OF 2000
(191) PRODUCT
PRODUCT_IMAG VARCHAR NOT NULL IMAGE OF images/5RMq5Gg6E
E (191) PRODUCT
C_ID BIGINT NOT NULL CART ID 1
(20)

Page 18 | 41
Employee Management

Table name: CARTS

Table description: STORES DETAILS OF CARTS ID, QUENTITY, TOTAL, USER_ID AND
PRODUCT_ID.

Field name Data type (with size) Constraint Description Sample data
ID BIGINT (20) PRIMARY CART_ID 1
KEY
QUN INT (11) NOT NULL CART 1
QUANTITY
TOTAL INT (11) NOT NULL TOTAL OF 1220
CART
U_ID INT (11) REFRENCES ID OF USER 1
USERS
P_ID INT (11) REFRENCES ID OF 1
PRODUCTS PRODUCT

TABLE NAME: CONTACT US

TABLE DESCRIPTION: STORES DETAILS OF CARTS ID, QUENTITY, TOTAL, USER_ID AND
PRODUCT_ID.

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION SAMPLE DATA


(WITH
SIZE)
ID BIGINT (20) PRIMARY CART_ID 1
KEY
USER_NAME VARCHAR NOT NULL NAME OF AMAAN
(191) USER
USER_EMAIL VARCHAR NOT NULL EMAIL ID A@GMAIL.COM
(191) USERS
PHONE_NUMBER VARCHAR NOT NULL NUMBER OF 9265588226
(191) USER
MASSAGE VARCHAR NOT NULL MASSAGE OF PRODUCT NOT
(191) USERS(QUERY) DELIVERED

TABLE NAME: CATEGORY

TABLE DESCRIPTION: STORES DETAILS OF PRODUCTS CATEGORYS.

FIELD NAME DATA CONSTRAINT DESCRIPTION SAMPLE


TYPE DATA
(WITH
SIZE)
ID BIGINT (20) PRIMARY CART_ID 1
KEY
CATEGORY_NAME VARCHAR NOT NULL CATEGORY OF ORGANIC
(191) PRODUCTS

Page 19 | 41
Employee Management

TABLE NAME: ORDERS

TABLE DESCRIPTION: STORES DETAILS OF ORDERS.

FIELD NAME DATA CONSTRAINT DESCRIPTION SAMPLE


TYPE DATA
(WITH
SIZE)
ID BIGINT PRIMARY KEY ORDER_ID 1
(20)
U_ID INT (11) FOREIGN ID OF USER 1
KEY(USERS)
P_ID INT (11) FOREIGN ID OF 1
KEY(PRODUCTS PRODUCT
)
ADDRESS VARCHAR NOT NULL ADDRESS OF MANINAGER
(191) CUSTOMER
NAME VARCHAR NOT NULL NAME OF ORGANIC-
(191) PRODUCT FRUITS
CITY VARCHAR NOT NULL ADDSRESS OF AHMEDABAD
(191) CITY
COUNTRY VARCHAR NOT NULL COUNTRY OF INDIA
(191) USER
ZIP-CODE INT(11) NOT NULL PIN-CODE 380028

4. Development:
Page 20 | 41
Employee Management

4.1. Coding standards:

1. Follow naming conventions in variable name and methods name.

2. Give minimum two spaces between operator and operand.

3. Give proper indentation.

Page 21 | 41
Employee Management

Page 22 | 41
Employee Management

4.2. Screen shots:

Page 23 | 41
Employee Management

Page 24 | 41
Employee Management

Page 25 | 41
Employee Management

5. Agile Documentation:

5.1 Agile Project Charter

General Project Information

Project Name E Learning

Project Champion Munish Prajapati, Nisheeth Bhatt, Dipal Patel

Project Sponsor LJ Institute of Computer Application

Project Manager Prof Monica Gahlawat

Stakeholders Admin, Student, Teacher

Expected Start Date 20/01/2023

Expected Completion Date 20/04/2023

Project Details

We continuously innovate to be the best Fashion store for our


Mission
customers.

E-commerce is when we use the internet to conduct business, think


of it as an online market that organizes transactions between buyers
Vision
and store owners. It eases access to many Courses and encourages
international learning by making it more accessible than ever.

Admin can deal in a wide range of courses. They can analyse


customer buying patterns and preferences and offer tailor-made
offers, discounts, and services. Business can be easily scaled. By
Scope selling via online retail sites like learn vision,

Edureka, Vedanta, etc., small traders and manufacturers get the seal
of legitimacy.

Date 20/04/2023

Page 26 | 41
Employee Management

5.2 Agile Roadmap / Schedule:

Page 27 | 41
Employee Management

5.3 Agile Project Plan:

Task Name Duration Start Finish Status

Sprint#1 : Project Structure 7d 29/03/2023 04/03/2023 Completed

UI Designing 4d 29/03/2023 01/03/2023 Completed

Database Management 3d 02/03/2023 04/03/2023 Completed

Sprint#2 : Registration 5d 24/03/2023 28/03/2023 Completed

Customer Registration 5d 24/03/2023 28/03/2023 Completed

Sprint#3 : Login and Logout 4d 04/04/2023 03/04/2023 Completed

Customer Login 2d 04/04/2023 04/04/2023 Completed

Admin Login 3d 04/04/2023 03/04/2023 Completed

Sprint#4 : Forget Password 2d 03/04/2023 03/04/2023 Completed

Customer changes Password 2d 03/04/2023 03/04/2023 Completed

Sprint#5 : Manage 9d 04/04/2023 05/04/2023 Completed


Courses(Admin)

Add, Update, View, Delete 1d 04/04/2023 05/04/2023 Completed

Sprint#6 : Courses(User) 5d 05/04/2023 06/04/2023 Completed

View Course 2d 06/04/2023 06/04/2023 Completed

View Course Details 3d 06/04/2023 07/04/2023 Completed

Sprint#7 : Enrol 6d 07/04/2023 10/04/2023 Completed

View Enrolled Courses 2d 10/04/2023 12/04/2023 Completed

Sprint#04 : Filters 5d 12/04/2023 14/04/2023 Completed

By Course Category 2d 15/04/2023 17/04/2023 Completed

By Course Duration 2d 18/04/2023 20/04/2023 Completed

By Teacher 1d 21/04/2023 24/04/2023 Completed

Page 28 | 41
Employee Management

5.4 Agile User Story:

User Story ID As a (type of user) I want to (perform So that I can


some task) (achieve some
goal)
1 Admin Manage Login Module Ensure that
validate user can
join
2 Admin Manage Courses Insert, Update
Delete and View
the Courses
3 Admin Manage order Ensures the
course
information is
valid
4 Student View Couse View
Course

5 Student Select Course Select the course

6 Student Enrolled courses To see what Course


you in the past
7 Student Make Payment Payment for the
Enrolled Course
8 Student Search Course Search Course
according to
their
requirement
9 Student Course Course Complication

04 Student Certificate Get Certificate after


Course Complication

Page 29 | 41
Employee Management

5.5 Agile Release Plan:

Task Name Duration Start Finish Release Date

Sprint#1: Project Structure 7d 29/03/2023 04/03/2023 04/03/2023

UI Designing 4d 29/03/2023 01/03/2023 01/03/2023

Database Management 3d 02/03/2023 04/03/2023 04/03/2023

Sprint#2 : Registration 5d 24/03/2023 28/03/2023 28/03/2023

Customer Registration 5d 24/03/2023 28/03/2023 28/03/2023

Sprint#3 : Login and Logout 4d 04/04/2023 03/04/2023 03/04/2023

Customer Login 2d 04/04/2023 04/04/2023 04/04/2023

Admin Login 3d 04/04/2023 03/04/2023 03/04/2023

Sprint#4 : Forget Password 2d 03/04/2023 03/04/2023 03/04/2023

Change Customer Password 2d 03/04/2023 03/04/2023 03/04/2023

Sprint#5 : Manage 9d 04/04/2023 05/04/2023 05/04/2023


Courses(Admin)

Add, Update, View, Delete 1d 04/04/2023 05/04/2023 05/04/2023

Sprint#6 : Courses(User) 5d 05/04/2023 06/04/2023 06/04/2023

View Course 2d 06/04/2023 06/04/2023 06/04/2023

View Course Details 3d 06/04/2023 07/04/2023 07/04/2023

Sprint#7 : Enrol 6d 07/04/2023 10/04/2023 10/04/2023

View Enrolled Courses 2d 10/04/2023 12/04/2023 12/04/2023

Sprint#04 : Filters 5d 12/04/2023 14/04/2023 14/04/2023

By Course Category 2d 15/04/2023 17/04/2023 17/04/2023

By Course Duration 2d 18/04/2023 20/04/2023 20/04/2023

By Teacher 1d 21/04/2023 24/04/2023 24/04/2023

Page 30 | 41
Employee Management

5.6 Agile Sprint Backlog:


Task Name Story Spri Priority Status Stor
nt y
Read Poi
y nt
Sprint#1: Project Structure Yes Yes High Completed 3

UI Designing Yes Yes High Completed 2

Database Management Yes Yes High Completed 2

Sprint#2 : Registration Yes Yes High Completed 2

Customer Registration Yes Yes High Completed 1

Sprint#3 : Login and Logout Yes Yes High Completed 4

Customer Login Yes Yes High Completed 4

Admin Login Yes Yes High Completed 4

Sprint#4 : Forget Password Yes Yes High Completed 4

Change Customer Password Yes Yes High Completed 3

Sprint#5 : Manage Yes Yes Medium Completed 3


Courses(Admin)

Add, Update, View, Delete Yes Yes High Completed 3

Sprint#6 : Courses(User) Yes Yes High Completed 2

View Course Yes Yes High Completed 4

View Course Details Yes Yes High Completed 3

Sprint#7 : Enrol Yes Yes Medium Completed 4

View Enrolled Courses Yes Yes High Completed 5

Sprint#04 : Filters Yes Yes Low Completed 2

By Course Category Yes Yes Low Completed 2

By Course Duration Yes Yes Low Completed 2

By Teacher Yes Yes High Completed 4

Page 31 | 41
Employee Management

5.7 Agile Test Plan:

Test Case ID : 101 Test Case Name : Customer Login

Designed by : Munish Prajapati Design Date :- 07/04/2023


Module Name : User Login Sub Module Name : Login
Executed by : Munish Prajapati Execution Date : 12/04/2023
Brief Description : User Login
(wit Data : “email : Test Priority (Low/Medium/High) :
t@g.com & password:1234”) High
Pre-Conditions: User Must Registered
& have Correct Username & Password.
Dependencies : None

Test Test Data Expect Actual Result Status Remar


Step ed (Pass/Fa ks
Resul il)
t
1 Email: Successfu Login Pass None
t@g.com lly login Successful.
& redirect
Password:
to
1234
Home
Page.
2 Email: Show Login Fail Need
t1@g.com “Invalid Not to
Credentials Successf Sho
Password:
.” ul w
1234
Erro
r
Messag
e.
3 Email: Show Login Fail Need
Page 32 | 41
Employee Management

t@g.com “Invalid Not to


Password: Credentials Successf Sho
.” ul w
1234Mah
Erro
r
Messag
e.
4 Email: Successfu Login Pass None
t@g.com lly login Successful &
in to Redirect to home
Password:
system & Page.
1234
redirect
to home
Page.

Test Case ID : 102 Test Case Name : User Registration


Designed by : Nisheeth bhatt Design Date : 28/04/2023
Module Name : User Registration Sub Module Name : Register
Executed by : Nisheeth bhatt Execution Date : 12/04/2023
Brief Description: User
Registration page for the new
user. User needs to provide Test Priority (Low/Medium/High) : High

the correct details for Registration.


Pre-conditions : None
Dependencies: Username & Password are store & fetch from auth_user Table.

Te Test Data Expected Actual Status Rem


st Result Result (Pass/Fai ar
St l) ks
ep
1 First Name: Successfully Registere Pass
nisheeth Last Registered & d
Redir
Name: bhatt Redirect to Successful
Page 33 | 41
Employee Management

Email: Login Page. ly. ect to


nisheeth@gmail.co login
m Password: Page.
1234 Confirm
Password:
1234
2 First Name: Show Not Fail No
nisheeth Last Error Registered & ne
Name: bhatt Message remain in
Email: as Registration
nisheeth@gmail.co “Password page.
m Password: & Confirm
1234 Confirm Password
Password: must be
12345 Equal”
3 First Name: Show Error Not Fail No
nisheeth Last Message as Registered & ne
Name: bhatt “Email remain in
Email: Registration
Id Already
nisheeth@gmail.co page.
Exist”
m Password:
1234 Confirm
Password:
1234
4 First Name: Successful Successful Pass No
Tushar Last ly ly ne
Name: shah Registered Registered
Email: & &
tushar@gmail.com
Password: 4321
Confirm
Password:
4321
Test Case ID : 103 Test Case Name : Add Course(Admin)
Designed by : Dipal patel Design Date :
Module Name : Add CourseModule Sub Module Name : Add Course
Executed by : Dipal patel Execution Date : 13/04/2023
Brief Description: Admin can Add Test Priority (Low/Medium/High) :
the High
Page 34 | 41
Employee Management

course.
Pre-conditions : Admin must be Logged in.
Dependencies : None

Te Test Step Action Expecte Actual Result Status


st d (Pass/Fail)
Result
1 Click on Open Show form Show form Pa
Add course for for ss
Course details Entering Entering
page details details
2 Fill Taking Validation of Validatio P
course Valid input n of as
Details details data input s
. data
3 Submit Click on Add course Add course P
data save and show it and show it as
button to admin to admin s

Page 35 | 41
Employee Management

Test Case ID : 104 Test Case Name : Cart


Designed by : Munish Prajapati Design Date : 20/04/2023
Module Name : Course Module Sub Module Name : Add Course
Executed by : Nisheeth bhatt Execution Date : 13/04/2023
Brief Description: User can Add the
Test Priority (Low/Medium/High) : High
Courses
Pre-conditions : User must be Logged in.
Dependencies : None

Te Test Step Action Expected Actual Result Status


st Result (Pass/Fail)
1 Click on Course Course should Course Fa
add course should be be added and should not be il
Button added display added

2 Click on Course Course should Course Pa


add course should be be added and should be ss
Button added display added to
display
3 Click Adde Course count Course count Pa
on(+) d Increase add Increase add ss
Increase Cours same item same
Button e multiple time Course
count multiple time
Incre
ase
4 Click on(-) Added Course count Course count Pa
Increase Course Decrease & Decrease & ss
Button count Delete/remove Delete/remov
Decreas e
e&
Delete
5 Click on Add the able to add able to Pa
Course Course multiple add ss
multiple
Page 36 | 41
Employee Management

Button Course Course

Page 37 | 41
Employee Management

Test Case ID : 105 Test Case Name : Payment


Designed by : Nisheeth bhatt Design Date : 08/03/2023
Module Name : Payment Sub Module Name : Payment
Executed by : Dipal patel Execution Date : 20/03/2023
Brief Description: payment for
Test Priority (Low/Medium/High) : High
courses
Pre-conditions : User must be Logged in.
Dependencies : None

Tes Test Step Action Expected Actual Result Status


t Result (Pass/Fail)
1 Click Show the All the All the Pass
on All Payment Payment
Check Payment options are options are
out options visible visible
Button
2 Click on Selecte Start the Start the Pass
Cash On d process and process and
Delivery option Course Order Course
Option Process is is Done Order is
Start Successf Done
ully Successful
3 Click On Need To Start online Start online Pass
Cart Filled up Payment Payment
Online All Process Process
Payment mandator
y
informati
on
4 Successful Ask for Online Online Pass
for add the right strip payment payment
mandatory number, Process is Process is
informatio cvv, date Done Done
n Successfully Successfully
5 Successful Ask strip If Add Credit Online Fail
Page 38 | 41
Employee Management

for add the number, card or Debit payment


mandatory cvv, date card Number Process is
informatio Not start
n
Successful Ask for Online Online Fail
6 for add the wrong payment payment
mandatory strip Process is Not Process is
informatio number, start Not start
n cvv, date

5.8 Earned-Value Burned Chart:

6. Proposed Enhancement:

⮚ We try to implement SMS functionality in our system like sending


weakly student reports.
Page 39 | 41
Employee Management

⮚ Try to implement online payment facility.

⮚ Try to implement automated testing functionality.

⮚ Make a common web application that multiple courses for student who
can use it.

Page 40 | 41
Employee Management

7. Conclusion:
While developing this project we have learnt a lot of thing about E-learning
learning work cycle and many other things. Our Goal was to design a reusable,
scalable and extensible digital E-learning website. This application provide
courses at low cost. This application helps in significant time and database
management and for better customer satisfaction.

Here, we need to learn Flutter technology to develop this application. Also we


learn PHP, Laravel and my Sql to make our Project even Better.

Building of project has given a precise knowledge about how Flutter framework
used to develop a web application, how it connects with firebase to access data
and how the data and web pages are modified provide to user with this system

8. Bibliography:

✵ www.google.com

✵ www.learnvern.com

✵ www.tutorialspoint.com

✵ www.learnvern.com

✵ www.w3school.com

✵ www.stackoverflow.com

Page 41 | 41

You might also like