Faculty of Engineering & Technology

Subject-Name: Software Engineering

Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

FACULTY OF ENGINEERING
AND TECHNOLOGY OF
TECHNOLOGY

Software
Engineerin
g
(30310525
4)

4th SEMESTER

Laboratory
Manual
Enrollment No: 2303031460228
 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

CERTIFICATE

This is to certify that Mr./Ms. KUNCHALA PRANEETH with enrolment

no.

2303031460228 and 4th Semester / AI-ML- 4 (Batch-1 ) has

successfully completed his/her laboratory experiments in the Software
Engineering (303105254) from theDepartment of Computer Science & Engineering (AI-
ML) during the academic year 2024-25

Date of Submission: .........................

Head of Department: Staff In charge:

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

INDEX
SR. Start End Start Date End Date Marks
NO. TITLE Page Page out of Sign
no. no. 10
1 Project definition and objective 26-11-24 10-12-24
of the specified module and
perform requirement Engineering
Process
2 Identify Suitable Design and 10-12-24 26-12-24
Implementation model from the
different software engineering
models.
3 Prepare a Software Requirement 26-12-24 31-12-24
Specification (SRS) for the
selected module
4 Develop a Software project
management planning (SPMP)
for the specific module
5 Do Cost Estimation use Different
Software Cost Estimation
Models.
6 Prepare System Analysis and
System Design of Identified
Requirement specification using
structure design as DFD with
Data Dictionary and Structure
chart for the specific module.
7 Designing the module using
Object Oriented approach
including Use case Diagram with
scenarios, Class Diagram and
State Diagram, Sequence
Diagram and Activity Diagram.
8 Defining Coding Standards and
walk through.
9 Write the test cases for the
identified module.
10 Demonstrate the use of different
Testing Tools with comparison.

11 Define security and quality

aspects of the identified
module.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH
PRACTICAL -1

PROJECT TITLE : ONLINE RESERVATION /BOOKING FOR A HOTEL

PROJECT DEFINITION
An online reservation/booking system for hotels is a digital platform that enables customers to book rooms,
event spaces, or other hotel services via a website or mobile application. This system integrates with the
hotel’s management software to provide real-time availability, secure payments, and seamless booking
experiences for customers.

DESCRIPTION
Online booking systems eliminate the need for manual processes like phone calls or in-person visits. They
streamline the customer journey by providing:
 Instant access to room or function space availability.
 A clear overview of pricing and options.
 Simplified confirmation and payment processes.
These systems are essential for hotels to manage reservations efficiently while providing a convenient and
accessible service to customers.

FUNCTIONS

1. Real-Time Availability Management: Displays live room and event space availability.
2. User Account Creation: Allows customers to create and manage their bookings.
3. Multi-Language Support: Offers language options for international guests.
4. Dynamic Pricing: Adjusts rates based on demand, seasons, or promotions.
5. Integration with Management Tools: Syncs with Property Management Systems (PMS) for
smooth operations.
6. Customer Support: Includes chatbots, FAQs, or direct messaging for queries.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

FEATURES

1. Search and Filter Options

o Customers can search by dates, room types, amenities, or event space capacity.
2. High-Quality Visuals
o Showcases detailed images of rooms, function spaces, and amenities.
3. Customizable Add-Ons
o Offers services like catering, decorations, or transportation.
4. Secure Payment Gateways
o Accepts multiple payment methods like credit cards, PayPal, and local options.
5. Mobile Compatibility
o Optimized for use on mobile devices for on-the-go bookings.
6. Booking Confirmation and Notifications
o Sends automatic email or SMS updates upon successful booking.
7. Calendar Integration
o Allows users to sync bookings with personal calendars.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

LIMITATIONS
1. Technical Challenges : System downtime can disrupt booking processes.
2. Learning Curve : Customers unfamiliar with technology might face difficulties.
3. Overbooking Risks : Poorly integrated systems can lead to double bookings.
4. Cost : Initial setup and maintenance can be expensive.
5. Customization Limitations : Some platforms may not support unique hotel requirements.
6. Fraud Risks : Without robust security, systems may be prone to scams or
breaches.

ADVANTAGES OF ONLINE HOTEL BOOKING

1. Convenience for Customers

 24/7 Accessibility: Guests can book anytime, anywhere, without the need to visit or
call the hotel.

2. Increased Revenue for Hotels

 Wider Reach: The system allows global visibility, attracting both local and
international guests.

3. Real-Time Availability and Updates

 Reduced Overbooking Risks: Live inventory updates ensure accurate availability data.

4. Better Guest Experience

 Personalized Options: Guests can choose specific room types, amenities, or additional
services based on their preferences.

5. Streamlined Operations for Hotels

 Integration with Hotel Management Systems: Seamlessly connects with tools like
Property Management Systems (PMS) for smoother operations.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

PRACTICAL-2
AS I AM SELECTING AGILE MODEL FOR MY ONLINE RESERVATION BOOKING FOR A HOTEL
DESCRIPTION :

The Agile Model is an iterative and flexible approach to software development that focuses on delivering
small, incremental improvements to a product in short cycles or "sprints." Instead of trying to build the
entire product upfront, Agile allows development to evolve based on continuous feedback, changing
requirements, and collaboration between cross-functional teams and stakeholders. The goal is to build a
functional system quickly, release it, and improve it continuously with each iteration .

AGILE MODEL DIAGRAM :

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

ADVANTAGES OF AGILE MODEL:

1. Flexibility and Adaptability

 Changing Requirements: Agile is highly adaptable to changes in requirements, even late in the development
process. This makes it ideal for projects where business needs or user preferences are likely to evolve.
 Continuous Improvement: Each iteration (or sprint) offers an opportunity to review the product and make
changes, improving it incrementally based on feedback.

2. Faster Time to Market

 Incremental Delivery: Agile delivers small, functional pieces of the product in short cycles (sprints). These
increments can be released to users early, allowing for faster time to market.
Enrollment No: 2303031460228
 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH
 Early and Frequent Releases: With frequent releases of working software, users can start benefiting from
the product sooner, providing immediate value.

3. Improved Product Quality

 Continuous Testing: Agile integrates testing throughout the development cycle, ensuring bugs and issues are
detected and resolved early, leading to a higher-quality product.
 Frequent Feedback: The ability to gather regular feedback from stakeholders and users helps ensure that the
product meets the real-world needs and expectations, reducing the likelihood of rework.

4. Customer Involvement and Satisfaction

 Frequent Collaboration: Agile encourages constant communication and collaboration between development
teams and stakeholders (including customers), ensuring that the product is built according to their needs.
 Customer-Focused Development: Since the product is developed incrementally and feedback is collected
regularly, the final product is more likely to align with customer expectations.

5. Transparency and Visibility

 Clear Progress: Agile provides regular updates, reviews, and demonstrations of the product at the end of each
sprint. This gives stakeholders and team members clear visibility into the progress and direction of the project.
 Product Backlog: The backlog, which lists the tasks and features to be worked on, provides a transparent
view of what’s planned, in progress, and completed.

6. Risk Management
 Early Detection of Issues: The iterative nature of Agile means that risks and problems are identified early,
reducing the chance of major issues arising late in the project.
 Frequent Releases: Since the product is developed and tested in small chunks, the project can adapt to
changing requirements or unexpected issues without causing major disruptions.

7. Better Team Collaboration

 Cross-Functional Teams: Agile encourages teams that are cross-functional and self-organizing, meaning that
team members from different skill areas (e.g., developers, designers, testers) work closely together, promoting
better communication and collaboration.
 Daily Standups: Daily meetings (or "standups") ensure team members are aligned and can discuss progress,
challenges, and next steps.

8. Higher Engagement and Morale

 Empowered Teams: Agile teams are often empowered to make decisions and organize their work, which can
lead to increased job satisfaction and higher morale.
 Focus on Small Wins: With the focus on achieving small, tangible goals in each sprint, teams can feel a sense
of accomplishment, boosting motivation and engagement.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

9. Cost Efficiency
 Early Detection of Problems: By identifying problems early through continuous testing and feedback, Agile
helps prevent costly errors from accumulating, leading to more efficient use of resources.
 Prioritization of Features: The backlog prioritization ensures that the most important features are developed
first, meaning the business can get the most value out of each sprint without spending resources on less
critical tasks.

10. Better Alignment with Business Goals

 Continuous Stakeholder Feedback: Agile allows the product to evolve in alignment with the business’s
needs by incorporating feedback from stakeholders on a regular basis.
 Value-Driven Development: Features that provide the most value to the business or customers are prioritized
in the backlog, ensuring that the development is aligned with business goals.

DISADVANTAGES OF AGILE MODEL

1. Scope Creep
 Description: Due to its flexible nature, Agile can lead to scope creep—where the project continuously
evolves, adding new features or changes without clear boundaries.
 Impact: This can result in the project becoming more complex and difficult to manage, potentially leading to
delays, overspending, and resource strain.

2. Requires High Collaboration and Availability

 Description: Agile demands constant communication and collaboration between all stakeholders
(development team, business owners, customers, etc.), often through regular meetings and feedback loops.
 Impact: If stakeholders or team members are unavailable or fail to participate actively, it can delay the
process and create misalignments. This can be particularly challenging in distributed or remote teams.
Enrollment No: 2303031460228
 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH

3. Less Predictability
 Description: Agile’s flexible nature means that detailed upfront planning is minimized. As a result, it can be
harder to predict exact timelines, costs, and the overall scope of the project from the outset.
 Impact: For organizations or projects that require strict timelines or budgets, Agile may not provide enough
certainty. It can also be difficult to estimate the final product’s cost, which is challenging for clients or
managers expecting clear forecasts.

4. Overemphasis on Short-Term Deliverables

 Description: Agile focuses on delivering small, incremental improvements in each sprint. While this is great
for adaptability, it can sometimes lead to an overemphasis on short-term deliverables rather than long-term
architectural planning.
 Impact: The focus on quick results might result in a lack of long-term vision, and crucial infrastructure or
non-functional aspects (e.g., scalability, security) may be neglected or deferred, leading to potential issues
down the line.

5. Can Be Resource-Intensive
 Description: Agile often requires more resources, such as time, effort, and skilled personnel. Regular
communication, daily standups, sprint planning, and reviews can consume significant time and energy.
 Impact: Small or resource-constrained teams may struggle to maintain the necessary pace and workload,
leading to burnout or inefficiencies. Agile's iterative nature also means that frequent testing, changes, and bug
fixes require a significant amount of effort.

6. Difficulty Scaling for Large Projects

 Description: While Agile works well for small to medium-sized projects, scaling Agile for larger projects or
organizations can be challenging. Multiple teams need to coordinate effectively, and ensuring consistent
communication and alignment across teams can become complex.
 Impact: Without proper frameworks like Scaled Agile Framework (SAFe) or LeSS (Large Scale Scrum),
scaling Agile to large projects or enterprises can lead to fragmentation, lack of coordination, and inconsistent
implementation.

7. Potential for Inconsistent Quality

 Description: Agile emphasizes speed and flexibility, but if testing and quality assurance are not carefully
planned or executed during each sprint, the result could be inconsistent quality or technical debt.
 Impact: Rushed development in some sprints or lack of proper QA processes can result in bugs or
suboptimal code that accumulates over time, creating problems in the long run. Continuous integration and
testing are key, but may not always be sufficient.

Enrollment No: 2303031460228

 Faculty of Engineering & Technology
Subject-Name: Software Engineering
Subject-Code:303105254
B.Tech CSE Year: 2ND Semester: 4TH
8. Unclear Roles and Responsibilities

 Description: Agile encourages self-organizing teams, but this can sometimes lead to unclear or overlapping
roles and responsibilities, especially in teams that are new to Agile practices.
 Impact: If roles are not clearly defined, it may cause confusion, duplication of work, or accountability issues.
In some cases, team members may struggle to make decisions without a clear leader or authority.

9. Requires Experienced and Skilled Team Members

 Description: Agile’s success depends heavily on the expertise and experience of the team. Developers,
testers, product owners, and other stakeholders need to be skilled in Agile methodologies and able to work
autonomously within self-organizing teams.
 Impact: If the team is not familiar with Agile practices, the project can experience delays, inefficiencies, or
misunderstandings about how to implement Agile principles effectively. Training new teams can require
significant investment in time and resources.

10. Harder to Manage Long-Term Projects

 Description: For projects with fixed deadlines, budgets, or detailed plans (e.g., government contracts, large
infrastructure projects), Agile may not be a suitable approach. It’s harder to align long-term goals with short,
iterative sprints.
 Impact: The lack of comprehensive upfront planning and exact milestones can create difficulties when
stakeholders demand detailed reports on long-term progress or when there’s a need to adhere to a strict
timeline or budget.

11. Not Ideal for All Types of Projects

 Description: Agile is not always the best choice for all types of projects. For example, projects that are highly
structured, require strict compliance (e.g., in healthcare or finance), or involve a high level of complexity and
integration may benefit more from a traditional approach like the Waterfall model.
 Impact: Agile may be less effective for projects where requirements are unlikely to change or where precise
documentation and processes are more important than flexibility and rapid iterations.

SITUATION WHERE WE HAVE TO APPLIED AGILE MODEL

Enrollment No: 2303031460228