A.

D PATEL INSTITUTE OF
TECHNOLOGY

PAGE
NO NAME OF EXPIREMENT DATE SIGN REMARK
NO.
An introduction to software engineering & Studying
Various phases of Water-Fall Model. For each SDLC
phase, identify the objectives and summaries outcomes.
Assume yourself as Software Analyst / Project
developer/ / Manager and complete following practical
2, 3,4,5,6,7,8,9,10 based on selected project. Choose
1. any one project like:
1. Library Information System
2. Villager Telephone System
3. Waste Management Inspection Tracking
System (WMITS) 4. Flight Control
System
5. Ambulance Dispatching System /108
6. Suraksha Setup project system

Define requirement Gathering and technical requirement

2.
specification for selected project.

Select any process model with justifying your view, how

3.
is it suitable to your selected project.

Define Design and implementation requirement for

selected project. Include all UML diagrams (DFD, E-R,
Use case, Activity, Sequence, State Transition, Class &
4. Object Diagrams, Deployment Diagram)
• DATA dictionary and Database design
• Prototype if required). Full fledge requirement must be
covered in Diagram

Plan code construction activity and State your testing

5.
plans and define test cases.

Design the Test Cases for software domain problem. ·

State and implement testing plans and define test
cases.
6. · Complete validation and verification requirement for
your project discuss with proper justification. Mention
and discuss the risk factors and how can you mitigate
risk.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

FunctionPoint:
http://conferences.embarcadero.com/article/32094#Bonus.
7. Analyze the case study and identify the error and solve it.
At the end, need to assess calculation part of effort using
FP oriented estimation model.

Study any existing project Case Study and Analyze detail

8.
with your justified view.

9. Generate SRS Document as per given format.

Why Agile process models with DevOps are

recommended in big companies like Infosys. Justify with
10.
one of the case studies (You can explore it with any tool
like JIRA). Write a report of 3-5 pages on case study.

11. Coursera Certificate “Software Architecture”

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL: - 1

AIM: Study the complete Software Development Life Cycle (SDLC) and
Waterfall Model. Analyze various activities conducted as a part of various
phases. For each SDLC phase, identify the objectives and summaries
outcomes
Software Development Life Cycle (SDLC):
Software Development Life Cycle (SDLC) is a well-defined sequence of stages in
software engineering to develop the intended software product.
SDLC provides a series of steps to be followed to design and develop a
software product efficiently. SDLC framework includes the following steps:

1. Planning
This step onwards the software development team works to carry on the
project. The team holds discussions with various stakeholders from problem
domain and tries to bring out as much information as possible on their
requirements. The requirements are contemplated and segregated into user
requirements, system requirements and functional requirements. The
requirements are collected using a number of practices as given studying the
existing or obsolete system and software, conducting interviews of users and
developers, referring to the database or collecting answers from the
questionnaires.
After requirement gathering, the team comes up with a rough plan of software
NAME: - PARMAR VIVEK, ZEEL GOYANI
ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

process. At this step the team analyses if a software can be made to fulfil all

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

requirements of the user and if there is any possibility of software being no

more useful. It is found out, if the project is financially, practically and
technologically feasible for the organization to take up.
2. Analysis
At this step the developers decide a roadmap of their plan and try to bring up
the best software model suitable for the project. System analysis includes
Understanding of software product limitations, learning system related
problems or changes to be done in existing systems beforehand, identifying
and addressing the impact of project on organization and
personnel etc. The project team analyses the scope of the project and plans
the schedule and resources accordingly.
3. Design
Next step is to bring down whole knowledge of requirements and analysis on
the desk and design the software product. The inputs from users and
information gathered in requirement gathering phase are the inputs of this
step. The output of this step comes in the form of two designs; logical design
and physical design. Engineers produce meta-data and data dictionaries,
logical diagrams, data-flow diagrams and in some cases pseudo codes.
4. Implementation
This step is also known as programming phase. The implementation of
software design starts in terms of writing program code in the suitable
programming language and developing error free executable programs
efficiently.
5. Integration and Testing
An estimate says that 50% of whole software development process should be
tested. Errors may ruin the software from critical level to its own removal.
Software testing is done while coding by the developers and thorough testing
is conducted by testing experts at various levels of code such as module
testing, program testing, product testing, in-house testing and testing the
product at user’s end. Early discovery of errors and their remedy is the key to
reliable software.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

Software may need to be integrated with the libraries, databases and other
program(s). This stage of SDLC is involved in the integration of software with
outer world entities.
6. Maintenance
This phase confirms the software operation in terms of more efficiency and less
errors. If required, the users are trained on, or aided with the documentation
on how to operate the software and how to keep the software operational.
The software is maintained timely by updating the code according to the
changes taking place in user end environment or technology. This phase may
face challenges from hidden bugs and real-world unidentified problems.

SDLC - Waterfall Model

The Waterfall Model was the first Process Model to be introduced. It is also
referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software
development. The waterfall Model illustrates the software development
process in a linear sequential flow. This means that any phase in the
development process begins only if the previous phase is complete. In this
waterfall model, the phases do not overlap.
Waterfall Model - Design
Waterfall approach was first SDLC Model to be used widely in Software
Engineering to ensure success of the project. In "The Waterfall" approach, the
whole process of software development is divided into separate phases. In this
Waterfall model, typically, the outcome of one phase acts as the input for the
next phase sequentially. The following illustration is a representation of the
different phases of the Waterfall Model.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

[Waterfall Model]
The sequential phases in Waterfall model are :-
1. Requirement Gathering and analysis
All possible requirements of the system to be developed are captured in this
phase and documented in a requirement specification document.
2. System Design
The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware
and system requirements and helps in defining the overall system architecture.
3. Implementation
With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
4. Testing
All the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is tested
for any faults and failures.
5. Deployment of system

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

Once the functional and non-functional testing is done; the product is deployed
in the customer environment or released into the market.
6. Maintenance
There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.
All these phases are cascaded to each other in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases. The next
phase is started only after the defined set of goals are achieved for previous
phase and it is signed off, so the name "Waterfall Model". In this model,
phases do not overlap.
 Waterfall Model - Advantages
The advantages of waterfall development are that it allows for
departmentalization and control. A schedule can be set with deadlines for
each stage of development and a product can proceed through the
development process model phases one by one. Development moves from
concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order.

 Some of the major advantages of the Waterfall Model are

as follows
 Simple and easy to understand and use
 Easy to manage due to the rigidity of the model. Each phase has
specific deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very
well understood. Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

 Waterfall Model - Disadvantages

The disadvantage of waterfall development is that it does not allow much
reflection or revision. Once an application is in the testing stage, it is very
difficult to go back and change something that was not well-documented or
thought upon in the concept stage.

 The major disadvantages of the Waterfall Model are

as follows :-
 ∙ No working software is produced until late during the life cycle.
 ∙ High amounts of risk and uncertainty.
 ∙ Not a good model for complex and object-oriented projects.
 ∙ Poor model for long and ongoing projects.
 ∙ Not suitable for the projects where requirements are at a
moderate to high risk of changing. So, risk and uncertainty
is high with this process model.
 ∙ It is difficult to measure progress within stages.
 ∙ Cannot accommodate changing requirements.
 ∙ Adjusting scope during the life cycle can end a project.
 ∙ Integration is done as a "big-bang. at the very end,
which doesn't allow identifying any technological or
business bottleneck or challenges early.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL :- 2
AIM :- DEFINE REQUIREMENT GATHERING AND
TECHNICAL REQUIREMENT SPECIFICATION
FOR SELECTED PROJECT.

REQUIREMENT GATHERING :-
Requirement Gathering is the process of understanding what is needed for a
system or application. For a college campus application for students, this
involves:
 Identifying Stakeholders: Students, faculty, admins, IT staff.
 Interviews and Surveys: Talking to stakeholders to understand their needs.
 Workshops and Meetings: Collaborating to refine and detail requirements.
 Observation: Seeing how current systems are used and identifying gaps.
TECHNICAL REQUIREMENT SPECIFICATION (TRS)
A Technical Requirement Specification (TRS) is a document that outlines the
technical needs and features of the application. It includes:

 Functional Requirements: What the system should do (e.g., registration,

course enrolment).
 Non-Functional Requirements: How the system performs (e.g., speed,
security, usability).
 System Architecture: High-level design of the system’s structure.
 Data Requirements: Types of data, data flow, storage needs.
 Interface Requirements: How the application interacts with other systems
or users.
 Technical Constraints: Limitations like budget, time, and technology stack.
1. IDENTIFY STAKEHOLDERS
 Students: Understand their needs, preferences, and pain points.
 Administrators: Gather requirements from the college administration.
 Faculty: Get input from teachers and professors.
 IT Staff: Understand technical requirements and constraints.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

2. DEFINE FUNCTIONAL REQUIREMENTS

 User Registration: How students will register and create accounts.
 Course Enrolment: Process for enrolling in courses.
 Grade Management: How grades will be recorded and accessed.
 Communication Tools: Features for messaging, announcements, etc.
 Financial Management: Handling tuition fees, scholarships,
and payments.

3. DEFINE NON-FUNCTIONAL REQUIREMENTS

 Performance: System response times and load handling.
 Security: Data protection and privacy measures.
 Usability: User interface design and ease of use.
 Scalability: Ability to handle an increasing number of users.

4. GATHER USER STORIES AND USE CASES

 User Stories: Describe specific tasks users will perform.
 Use Cases: Detail interactions between users and the system.

5. CREATE A REQUIREMENTS DOCUMENT

 Document Requirements: Compile all gathered information into
a structured document.
 Review and Validate: Ensure all stakeholders review and agree on
the requirements.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

6. PRIORITIZE REQUIREMENTS
 Must-Have vs. Nice-to-Have: Prioritize features based on importance
and feasibility.

7. PLAN FOR TESTING

 Test Cases: Develop test cases to validate the system
meets requirements.
 Feedback Loop: Plan for gathering feedback and making adjustments.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL :- 3
AIM :- DEVELOPMENT OF DFD AND E-R DIAGRAM FOR THE
SOFTWARE DOMAIN PROBLEM.
DFD DIAGRAM FOR COLLEGE CAMPUS CONNECT APP:
1. LEVEL 0 DFD:
 Displays the main interactions of Students, Faculty, and Admins
with the system.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

2. LEVEL 1 DFD:
 Breaks down the system into four major processes: User
Authentication, Course Management, Event Management,
and Notification System, showing detailed interactions.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

3. LEVEL 2 DFD:
 Focuses on the User Authentication process, detailing login,
signup, and session management for all user types.

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

ENTITY-RELATIONSHIP DIAGRAM FOR COLLEGE CAMPUS CONNECT

APP:
 Login: login_id, password
 Student:M_Number,Email,Enrolment,U_id,Student_Passwd
 Faculty:M_Number, Email, Faculty_passwd, U_id
 Admin:M_Number, Admin_id, Admin_passwd, Emial,U_id

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL :- 4
AIM :- AIM: DRAW USE CASE AND ACTIVITY DIAGRAMS FOR THE
PROJECT DEFINITION.
Use case Diagram:
 A use case diagram visually represents the interactions between
users (actors) and a system,
 illustrating how they achieve specific goals (use cases). Here’s a
simple guide to creating a use case diagram.

Components of a Use Case Diagram:

1. Actors: Represent external entities (users, systems) that interact with
the system. They can be primary (who directly interacts) or secondary
(who provide support).

2. Use Cases: Represent the functionalities or services the system provides

to the actors. Each use case should focus on a specific goal.

3. System Boundary: A box that defines the scope of the system. Use cases
are inside this boundary, while actors are outside.
4. Relationships:
 Associations: Lines connecting actors to use cases, showing interaction.
 Include: Indicates that a use case always incorporates the behavior
of another use case.
 Extend: Indicates that a use case can add additional behavior
under certain Condition

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

COMPONENTS FOR COLLEGE CAMPUS CONNECT APP:

 Student
 Faculty
 Admin

USE CASE:
1. REGISTER : Student and Faculty can Register on the App
2. LOGIN : Student, faculty and admin can login in these app
3. SUGGESTION: Faculty and Student can give a suggestion
4. MANAGE EVENT : Admin, Faculty or Student can Create or Manage Event
of college
5. MANAGE COMPLAIN: Check and Solve the Problem
6. REPORT COMPLAIN: Student and Faculty can submit Problem in college
7. CHECK SUGGESTION: Admin check the Suggestions, Submitted by
Student and Faculty
8. MANAGE PROFILE: Faculty or Student can Manage Profile
9. STUDENT DETAIL: Admin or Faculty can check student detail
10.FACULTY DETAIL: Admin can check Faculty detail

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

ACTIVITY DIAGRAMS:
1. User Activity Diagram

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

2. Faculty Activity Diagram

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

3. Admin Activity Diagram

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 5
AIM : DRAW THE SEQUENCE DIAGRAM FOR THE PROJECT
DEFINITION.
SEQUENCE DIAGRAM :

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 6
AIM : DEVELOPMENT OF STATE TRANSITION DIAGRAM FOR
SOFTWARE PROJECT DEFINITION

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 7
AIM : DESIGN CLASS & OBJECT DIAGRAMS FOR SOFTWARE DOMAIN
PROBLEM.
CLASS DIAGRAM FOR COLLEGE CAMPUS CONNECT APPLICATION:-

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

OBJECT DIAGRAM FOR COLLEGE CAMPUS CONNECT APPLICATION:-

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 8
AIM : PREPARE A DATA DICTIONARY FOR SOFTWARE PROJECT
DEFINITION.
1) Student

Field Name Data Type Description

Student_u_id Integer Unique identifier for each student
username String Username for student login
password String Password for student login
full_name String Full name of the student
email String Email address of the student
phone_number String Contact number of the student
Array List of courses the student is
Courses_detail
of currently enrolled in
Strings
Branch String Branch name
Array
Events_id Event Detail(name, date, description)
of
Objects
Report Write Issue you face in
String
Problem college/hostel
Suggestion_id String Give suggestion, that help college
Array Messages and notifications from
notifications
of teachers or admin
Objects

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

2) Faculty

Data
Field Name Description
Type
faculty_id Integer Unique identifier for each Faculty
username String Username for Faculty login
password String Password for faculty login
full_name String Full name of the Faculty
email String Email address of the Faculty
phone_number String Contact number
Array
List of students (student_u_id, full_name)
manage_students of
for faculty management
Objects
Array
Provide study material for students
Study_Material of
(course_id, name)
Objects
Array
List of announcements made by the admin
Manage_announcements of
(date, message)
Objects
Report_Problem String Write a problem
Suggestion_id String Give Suggestion
Array
Manage
Manage_Event of
event(Event_id,Student_u_id,full_name
object

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

3) Admin

Field Name Data Type Description

Admin_id Integer Unique identifier for each Admin
username String Username for Admin login
password String Password for Admin login
full_name String Full name of the Admin
email String Email address of the Admin
phone_number String Contact number
Array List of students (student_u_id, full_name) for
Students_detail
of faculty management
Objects
Array
Faculty_detail List of faculty member(faculty_id,full_name
of
object
Provide study material for students
Array
Manage Complain (Report_Problem,
of
faculty_id,full_name,Student_u_id,full_name)
Objects
List of
Array
Manage_Event event(Event_id,Student_u_id,full_name,faculty
of
_id,full_name)
object
Manage_announcem Array List of announcements made by the admin
ents of (date, message)
Objects
Report Problem String Write a problem

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

Field Name Data Type Description

View
View_Suggestion String Suggestion(Suggestion_id,Student_u_id,full_na
me,faculty_id,full_name)

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 9
AIM : DRAW THE DEPLOYMENT DIAGRAM FOR THE PROJECT
DEFINITION
Deployment Diagram Components :

User Device:
Represents devices like laptops, tablets, or smartphones used by
students, faculty, and admin.
Web Server:
Hosts the web application and handles user requests.
Database Server:
Stores user data, course information, event details, etc.
Notification Service:
Manages sending notifications to users.
API Server:
Handles requests and responses between the front end and back
end.
Connections:
User Device ↔ Web Server (HTTP)
Web Server ↔ Database Server (JDBC or
SQL) Web Server ↔ Notification Service
(REST API) Web Server ↔ API Server (REST
API)

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

DEPLOYMENT DIAGRAM

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

PRACTICAL : 10
AIM :- DESIGN THE TEST CASES FOR SOFTWARE DOMAIN PROBLEM.
Test Case Structure:
Each test case should include the following elements:
1. Test Case Description
2. Preconditions
3. Test Steps
4. Expected Result
5. Status (Pass/Fail)
All Test Case Scenarios:
 Test Case 1: User Login (Failing Scenario)
 Description: Verify that students can log in with valid credentials.
 Preconditions: Student account exists in the system.
 Test Steps:
1. Navigate to the login page.
2. Enter invalid username and password.
3. Click on the "Login" button.
 Expected Result: The system should display an error message
indicating invalid credentials and prompt the user to re-enter correct
information.
 Actual Result: The system erroneously redirects the user to
the dashboard instead of displaying an error message.
 Status: Fail

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

Problem :
The system does not handle incorrect login attempts properly, allowing users
with invalid credentials to access the dashboard.
Fix:
1. Modify the authentication logic to check if the entered
credentials match existing records in the database.
2. If the credentials are incorrect, display an error message and do
not allow access to the dashboard.
Test Case 1: User Login (After Fix – Successful Scenario)
 Description: Verify that students can log in with valid credentials.
 Preconditions: Student account exists in the system.
 Test Steps:
1. Navigate to the login page.
2. Enter valid username and password.
3. Click on the "Login" button.
 Expected Result: The student should be logged in and redirected to
the dashboard.
 Actual Result: The student is successfully logged in and redirected to
the dashboard.
 Status: Login Successful
Fix:
1. Implement validation checks to ensure all required fields
(e.g., ratings, comments) are filled out before submission.
2. Provide user-friendly error messages if any fields are left blank.
3. Fix the backend logic to handle and store feedback data properly.
Test Case 2: Providing Feedback on Lectures (After Fix – Successful Scenario)
 Description: Verify that a student can provide feedback on a lecture.
 Preconditions: User is logged in; lectures have been attended.
 Test Steps:

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142
 A.D PATEL INSTITUTE OF
TECHNOLOGY

1. Navigate to the "Feedback" section.

2. Choose a lecture and add comments or ratings.
3. Click on the "Submit Feedback" button.
 Expected Result: Feedback should be submitted successfully, and
a confirmation message should be displayed.
 Actual Result: Feedback is successfully submitted, and a
confirmation message is displayed.
 Status: Pass

NAME: - PARMAR VIVEK, ZEEL GOYANI

ENROLL: - 12302080603015,12202080601142