Tab 1

Faculty of Engineering & Technology

. Software Engineering Laboratory (303105253)

FACULTY OF ENGINEERING AND TECHNOLOGY

BACHELOR OF TECHNOLOGY

Software Engineering Laboratory

(303105253)

SEMESTER IV
Computer Science & Engineering Department

NAME : P.RAHUL 1
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

CERTIFICATE

This is to certify that

Mr./Ms Pamula Rahul with enrolment no.

2303031240145 has successfully completed his/her laboratory experiments in the

Software Engineering Laboratory (303105253) from the department of

........................................................... during the academic year ................................

Date of Submission:......................... Staff In charge:...........................

Head of Department:...........................................

NAME : P.RAHUL 2
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

PRACTICAL -1
AIM : PROJECT DEFINITION AND OBJECTIVE OF THE SPECIFIED MODULE AND
PERFORM REQUIREMENT ENGINEERING PROCESS.

Project Definition:
The goal of my project is to create a website for my mother's tailoring business. The website will serve as
an online presence, providing customers with information about the services she offers, showcasing her
work, and allowing potential customers to contact her.

Project title : CREATING WEB PAGE FOR TAILORING SHOP

Objective of the Specified Module:

1.​ Business Introduction:
○​ Provide an overview of the business, including its history, vision, and values.
○​ Include a personal message from my mother about her passion for tailoring and customer
satisfaction.
2.​ Service Offerings:
○​ List the tailoring services provided (e.g., custom tailoring, alterations, bridal wear, etc.).
○​ Include pricing information or offer a "Request a Quote" feature.
○​ Add clear descriptions and images to each service to help customers understand what
they are getting.
3.​ Portfolio/Showcase:
○​ Display a gallery of completed works, such as before-and-after photos of alterations or
custom dresses.
○​ Include testimonials from happy customers, if possible.
4.​ Booking and Contact Information:
○​ Allow customers to schedule appointments (through a form or integrated calendar).
○​ Provide clear contact information, including phone number, email, and physical address.
○​ Include a simple contact form for quick inquiries.
5.​ Online Store (Optional):
○​ If your mother sells products (e.g., tailored clothing, fabric, or accessories), you could
integrate a basic e-commerce system.
○​ Add a secure payment gateway for customers to buy products directly.
6.​ Social Media Integration:
○​ Add links to your mother’s business social media profiles (Instagram, Facebook, etc.), if
applicable.
○​ Optionally, embed her social media feed to show her latest work or updates.
7.​ SEO (Search Engine Optimization):
○​ Ensure the website is optimized for search engines (keywords related to tailoring and the
local area) to help potential customers find her business easily.
8.​ Mobile Compatibility:
○​ The website must be responsive, meaning it should work well on mobile devices, as many
users browse websites from smartphones.

NAME : P.RAHUL 3
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

Requirement Engineering Process:

The Requirement Engineering process helps in defining what needs to be done to create the website
and ensures that both functional and non-functional requirements are clear.

1. Requirements Elicitation:

●​ Interview your mother to gather detailed information about the business, her services, and any
specific preferences she has for the website.
●​ Research competitors and similar businesses to understand what works well in the tailoring
industry.
●​ Identify Target Audience: Understand who your target customers are (e.g., local community,
brides, fashion enthusiasts).

2. Requirements Analysis:

●​ Functional Requirements:
○​ Website must have a clear home page with a business overview.
○​ There must be a section for each service offered with detailed descriptions and pricing (if
applicable).
○​ Portfolio showcasing pictures of past work, including customer testimonials.
○​ Contact form for inquiries and appointment scheduling.
○​ Option to make purchases (if there is an online store).
●​ Non-Functional Requirements:
○​ Usability: The website should be easy to navigate and user-friendly for all age groups.
○​ Performance: The website must load quickly.
○​ Security: Secure forms for customer data, especially if payment or contact details are
involved.
○​ Scalability: The website should be able to handle increased traffic as the business grows.

3. Requirements Specification:

●​ Home Page: Introduction to the business, personal message from your mother, and business
values.
●​ Services Page: List of services, each with a description, photo, and price range (or "Request a
Quote" button).
●​ Portfolio Page: A gallery of past works with images and descriptions, including customer
feedback.
●​ Contact Page: Contact form, phone number, email, and a map with the physical location of the
business.
●​ Online Store (Optional): For any products she sells.
●​ Blog/News Section (Optional): Updates about the business, new projects, or seasonal offers.
●​ Social Media Integration: Links to Instagram, Facebook, etc.

4. System Design:

●​ Wireframing: Create wireframes or basic sketches of the website layout (how each page will look
and flow).
●​ Technology Stack: Decide on the technologies you'll use (HTML, CSS, JavaScript, and possibly
a backend like WordPress, Shopify, or a custom framework if you plan to add an online store).

NAME : P.RAHUL 4
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

5. Implementation Plan:

●​ Frontend Development: Design the visual layout and structure using HTML, CSS, and
JavaScript (for interactive elements).
●​ Backend Development: If needed, integrate a CMS (Content Management System) like
WordPress or a website builder platform (Wix, Squarespace).
●​ Testing: Test the website on different devices and browsers to ensure compatibility and fix bugs.
●​ Deployment: Upload the website to a hosting server and make it live.

6. Verification & Validation:

●​ User Testing: Ask friends or potential customers to use the site and provide feedback.
●​ Ensure Accessibility: Check for accessibility, ensuring the website can be used by people with
disabilities (e.g., screen reader support, color contrast).
●​ SEO Check: Ensure that all content is optimized for search engines (keywords, meta tags, alt
tags for images).

7. Maintenance & Updates:

●​ Regularly update the website with new work, customer reviews, and promotions.
●​ Monitor performance and adjust as needed to keep the website running smoothly.

Key Features to Focus On:

1.​ Clear Communication: Ensure the website reflects your mother’s skills and passion for tailoring.
Use language that’s warm, welcoming, and professional.
2.​ Visual Appeal: Use high-quality images of her work to make the website visually appealing.
3.​ Customer Experience: Make sure the site is easy to navigate and that contact or booking forms
are simple to use.
4.​ Local SEO: Focus on local SEO to help attract nearby customers. Optimize the site with
location-specific keywords like “tailor in [Your City].”

NAME : P.RAHUL 5
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

PRACTICAL -2
AIM : Identify Suitable Design and Implementation model from the different
software engineering models.

1. Introduction

The goal of this project is to create a website for a tailoring business. The website will provide
business information, showcase service offerings, display a portfolio of past work, offer booking
and contact options, and optionally support an online store. Based on the requirements defined
in Practical 1, it is essential to choose a suitable design and implementation model that will
ensure effective development, timely delivery, and flexibility for future changes.

2. Project Overview

Project Title: Creating a Web Page for a Tailoring Shop​

Objective: Develop a responsive, user-friendly, and visually appealing website that introduces
the tailoring business, highlights its services, and facilitates customer interactions through
booking, contact, and optional e-commerce features.

Modules to be Developed:

●​ Business Introduction: Overview of the business, vision, and values.

●​ Service Offerings: Details of services provided (custom tailoring, alterations, bridal wear,
etc.).
●​ Portfolio: Showcasing past works with a gallery of images and testimonials.
●​ Contact Page: Contact form, phone number, email, and location information.
●​ Online Store (Optional): Option to sell tailored products or accessories online.
●​ Social Media Integration: Links to social profiles and embedded feeds.

3. Selection of a Suitable Design and Implementation Model

Based on the characteristics and requirements of the tailoring shop website, the Incremental
Model combined with elements of the Agile Model is the most appropriate choice. Below is the
rationale for selecting these models.

4. Rationale for Selecting the Incremental and Agile Model

1.​ Requirement Clarity: While some of the features (like the Home Page, Service
Offerings, and Contact Page) have clear requirements, other components (like the Online
Store) may require refinement during development. This aligns well with the incremental
model, where modules are developed and delivered in phases.
2.​ Flexibility: The tailoring business may require adjustments based on customer feedback,
so Agile practices will ensure quick responses to feedback.
3.​ Timely Delivery: Delivering essential modules (like Home Page, Service Offerings, and
Contact Page) first allows the tailoring business to have an online presence early. Other
modules like the Portfolio and Online Store can be added incrementally.

NAME : P.RAHUL 6
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
4.​ Risk Management: The incremental model helps identify risks early, allowing for better
control over development.

5. Design and Implementation Process

1. Requirement Analysis

●​ Functional Requirements
○​ Home Page with business introduction.
○​ Service Offerings with clear descriptions and pricing.
○​ Portfolio with an image gallery and customer testimonials.
○​ Contact page with an inquiry form and business contact details.
○​ Optional online store to sell tailored products.
●​ Non-Functional Requirements
○​ Usability: Intuitive navigation and simple user interface.
○​ Performance: Fast page load speed and responsiveness on mobile devices.
○​ Security: Secure customer contact forms and data protection.
○​ SEO: Optimized for search engines to increase local visibility.
○​ Scalability: Ability to add more services and store products in the future.

2. Incremental Development Stages

●​ Increment 1: Develop the Home Page, Business Introduction, and Contact Page.
●​ Increment 2: Build the Services Page with service descriptions, images, and optional
request-a-quote functionality.
●​ Increment 3: Develop the Portfolio Page to showcase past work and customer
testimonials.
●​ Increment 4: Integrate Social Media Links and SEO Enhancements.
●​ Increment 5: Optional Online Store development with a shopping cart and payment
gateway.

3. Agile Practices to Be Followed

●​ Sprint Planning: Divide each increment into smaller sprints with clear deliverables for
each sprint.
●​ Daily Standups: Review daily progress to ensure timely completion.
●​ Backlog Refinement: Continuously refine the list of features and prioritize the most
essential components.
●​ Feedback Loops: Gather feedback from the business owner after each increment to
make changes and improvements.

6. Design Process
1. Wireframing and Prototyping

●​ Design wireframes for each page (Home, Services, Portfolio, Contact, and Store).

NAME : P.RAHUL 7
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
●​ Use prototyping tools like Figma or Adobe XD to create mockups for review.

2. Technology Stack

●​ Frontend: HTML, CSS, JavaScript (for responsive and interactive elements).

●​ Backend: Optional use of WordPress, Shopify, or a custom-built backend using PHP,
Node.js, or Python (Django/Flask).
●​ Database: MySQL or a simple content management system (CMS) database for storing
portfolio items, testimonials, and store products.
●​ Version Control: Use Git for version control and GitHub or GitLab for repository
management.

7. Implementation Plan

1.​ Frontend Development

○​ Develop static HTML/CSS pages for Home, Services, Portfolio, and Contact.
○​ Add animations and interactive elements using JavaScript.
2.​ Backend Development
○​ Set up a CMS (like WordPress) or a custom backend to manage dynamic content.
○​ Develop a system for handling inquiries from the contact form.
3.​ Integration of External Tools
○​ Use third-party services like Calendly for appointment booking.
○​ Payment gateway integration (if an online store is developed).
4.​ Testing and Quality Assurance
○​ Test for cross-browser compatibility and mobile responsiveness.
○​ Test usability, ensuring the website is intuitive for users of all ages.

8. Verification & Validation

1.​ User Testing: Get feedback from potential customers and stakeholders (like the business
owner) to ensure the design meets their needs.
2.​ Accessibility Testing: Ensure the website is usable for people with disabilities (e.g.,
using screen readers or color contrast adjustments).
3.​ SEO Review: Verify that keywords, meta descriptions, and alt text are in place.

9. Maintenance & Updates

1.​ Regular Content Updates: Add new testimonials, portfolio items, and new services
offered.
2.​ Security Patches: Apply security updates to protect the website from vulnerabilities.
3.​ Performance Optimization: Continuously improve page load speed and
responsiveness.

NAME : P.RAHUL 8
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

10. Comparison of Software Engineering Models

Model Reason to Use/Not Use

Waterfall Not suitable since requirements are not fully

clear from the start. Inflexible to change.

V-Model Not suitable as it emphasizes testing after

development phases are complete.

Incremental Chosen because the project can be delivered

in multiple phases.

Prototyping Useful in the early stages to refine

requirements. However, it is not suitable for
full implementation.

Spiral Too complex for this project. Risk

management is not a primary concern.

Agile Partially Chosen since iterative development

with frequent feedback is required.

RAD Not suitable as it emphasizes fast

development, which is not a priority.

11. Conclusion

The most suitable design and implementation model for the tailoring shop website is a
combination of the Incremental Model and Agile Model. The Incremental approach allows for
the step-by-step development and delivery of essential modules, while Agile practices facilitate
continuous feedback and changes. This hybrid approach ensures timely delivery, flexibility, and
customer satisfaction.

NAME : P.RAHUL 9
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

NAME : P.RAHUL 10
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
PRACTICAL-3

AIM :Prepare a Software Requirement Specification (SRS) for the selected module.

Software Requirements Specification (SRS) Document​

Project Title: Creating a Web Page for a Tailoring Shop

1. Introduction
1.1 Purpose

The purpose of this document is to define the functional and non-functional requirements for the
tailoring shop website. This website will serve as an online presence for the business,
showcasing services, displaying a portfolio, allowing customer interaction, and potentially
supporting an online store.

1.2 Intended Audience

●​ Business owner (tailor)

●​ Web development team
●​ Customers seeking tailoring services

1.3 Overview

The document outlines the requirements for the tailoring shop’s web page, including its
functionalities, constraints, and system interactions. The document serves as a guideline for the
development process.

1.4 Definitions, Acronyms, and Abbreviations

●​ CMS: Content Management System

●​ UI: User Interface
●​ SEO: Search Engine Optimization

1.5 References

●​ Requirement Engineering Process Document

●​ Software Engineering Principles

2. Overall Description
2.1 Product Perspective

NAME : P.RAHUL 11
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

This website will be an independent product designed to enhance the online presence of the
tailoring shop, allowing customers to explore services, view previous work, and get in touch with
the tailor.

2.2 Product Functions

●​ Business Introduction Page

●​ Service Offerings Page
●​ Portfolio/Showcase
●​ Booking & Contact Information
●​ Optional Online Store
●​ Social Media Integration

2.3 User Characteristics

●​ Customers looking for tailoring services

●​ Users with varying technical expertise

2.4 General Constraints

●​ Must be accessible on mobile and desktop

●​ Should load within 3 seconds
●​ Must be visually appealing and easy to navigate

2.5 Assumptions and Dependencies

●​ The business owner will provide content (images, service descriptions)

●​ Hosting and domain will be provided by the owner

3. Specific Requirements
3.1 Functional Requirements

1.​ Home Page: Displays an introduction to the business with a welcome message.
2.​ Service Page: Lists tailoring services with descriptions and pricing or a "Request a
Quote" option.
3.​ Portfolio Page: Displays images of previous work and customer testimonials.
4.​ Contact Page: Includes a form, phone number, email, and map for location.
5.​ Online Store (Optional): Allows customers to buy tailored products online.
6.​ Social Media Integration: Links to business social media pages and embedded feeds.

3.2 Non-Functional Requirements

●​ Usability: Intuitive navigation and accessibility-friendly design

●​ Performance: Fast load times and optimized for search engines

NAME : P.RAHUL 12
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
●​ Security: Secure customer inquiries and transactions
●​ Scalability: Ability to add new features and expand in the future

4. External Interface Requirements

4.1 User Interfaces

●​ Simple and elegant UI for easy navigation

●​ Responsive design for mobile and desktop

4.2 Hardware Interfaces

●​ Compatible with standard web browsers and mobile devices

4.3 Software Interfaces

●​ May use WordPress, Shopify, or a custom-built backend

●​ Integration with third-party APIs for booking and payments

4.4 Communication Interfaces

●​ Email notifications for customer inquiries

●​ Optional chat support for real-time assistance

5. Design Constraints
5.1 Standards and Conventions

●​ Follows HTML5, CSS3, JavaScript best practices

●​ SEO-optimized content structure

5.2 Programming Languages

●​ Frontend: HTML, CSS, JavaScript

●​ Backend: WordPress, Shopify, or a custom framework

5.3 Development Tools

●​ VS Code, Figma (for design), GitHub (for version control)

5.4 Hardware Limitations

NAME : P.RAHUL 13
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

●​ Should function efficiently on standard hosting services

6. Review and Validation

●​ Regular feedback from the business owner
●​ User testing for usability and performance
●​ SEO and accessibility compliance check

7. Approval and Maintenance

●​ Stakeholders to approve the finalized requirements
●​ Regular updates to keep the website functional and secure

NAME : P.RAHUL 14
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
PRACTICAL-4

AIM : Develop a Software project management planning (SPMP) for the specific module

1. Introduction

1.1 Project Title: Web Page for Tailoring Shop

1.2 Purpose: The purpose of this document is to outline the management strategy for
developing the tailoring shop's website module. It defines the scope, assumptions, constraints,
and execution plan required for the successful development and deployment of the module.

1.3 Scope: The module includes:

●​ Business Introduction Page

●​ Service Offerings Page
●​ Portfolio Showcase
●​ Booking & Contact Information
●​ Optional Online Store
●​ Social Media Integration

1.4 Assumptions and Constraints:

●​ The project must be completed within 3 months.

●​ Budget constraints limit the use of premium tools and services.
●​ The website must be mobile-friendly and SEO-optimized.
●​ The business owner will provide content and images.
●​ Hosting and domain acquisition will be handled by the business owner.

2. Project Organization

2.1 Roles and Responsibilities

●​ Project Manager: Oversees project progress and ensures timely delivery.

●​ Developer: Handles website coding, backend setup, and deployment.
●​ UI/UX Designer: Designs user-friendly interfaces and website aesthetics.
●​ Tester: Conducts testing to ensure website functionality and performance.
●​ Business Owner: Provides input on business requirements and feedback.

2.2 Communication Plan

●​ Weekly team meetings to review progress.

●​ Regular updates and feedback collection from the business owner.
●​ Issue tracking and documentation via GitHub or project management tools.

NAME : P.RAHUL 15
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

3. Work Breakdown Structure (WBS)

1.​ Phase 1: Planning & Requirement Analysis

○​ Gather business requirements
○​ Identify competitors and industry standards
○​ Finalize functional and non-functional requirements
2.​ Phase 2: Design
○​ Create wireframes and UI/UX design
○​ Review and finalize design with stakeholders
3.​ Phase 3: Development
○​ Frontend development (HTML, CSS, JavaScript)
○​ Backend development (CMS, database setup, integrations)
○​ Implement security measures
4.​ Phase 4: Testing & Quality Assurance
○​ Conduct usability and performance testing
○​ Resolve bugs and improve website speed
○​ Ensure compatibility across browsers and devices
5.​ Phase 5: Deployment & Maintenance
○​ Deploy the website on a hosting server
○​ Optimize SEO and analytics tracking
○​ Regular updates and content management

Risk Probability Impact Mitigation Strategy

Scope Creep Medium High Define clear

requirements and get
early approvals

Technical Issues High High Have backup

solutions and
contingency plans

Budget Overrun Low High Use cost-effective

tools and
open-source
technologies

Delays in Content Medium Medium Set strict deadlines

Delivery for content
submission

Security High High Implement security

Vulnerabilities best practices and
regular updates

NAME : P.RAHUL 16
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

Phase Duration Start Date End Date

Planning & 2 Weeks MM/DD/YYYY MM/DD/YYYY

Requirement
Analysis

Design 3 Weeks MM/DD/YYYY MM/DD/YYYY

Development 6 Weeks MM/DD/YYYY MM/DD/YYYY

Testing & QA 2 Weeks MM/DD/YYYY MM/DD/YYYY

Deployment & Ongoing MM/DD/YYYY Continuous

Maintenance

6. Resource Allocation

6.1 Human Resources:

●​ 1 Project Manager
●​ 1 Developer
●​ 1 UI/UX Designer
●​ 1 Tester

6.2 Technical Resources:

●​ Development Tools: VS Code, GitHub, Figma

●​ Hosting Services: WordPress, Shopify, or Custom Server
●​ Database: MySQL or CMS-based database

7. Monitoring & Evaluation

●​ Regular progress tracking using Agile sprints.

●​ Conduct usability testing with potential customers.
●​ Ensure compliance with performance and SEO requirements.

NAME : P.RAHUL 17
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)
PRACTICAL-5

AIM : Do cost and effort estimation using different software cost estimation models.

Cost and Effort Estimation for the Specified Module

1. Introduction

Accurate cost estimation is crucial for the successful execution of the project. It helps in
budgeting, resource allocation, scheduling, risk management, and contract negotiations.

2. Cost Estimation Models Used

For this project, we will use the Basic COCOMO Model for effort estimation.

3. Estimating Effort for the Tailoring Shop Web Page

3.1 Assumptions:

●​ The project is estimated to contain 8,000 lines of code (LOC).

●​ The project follows an organic development model.
●​ Using the Basic COCOMO equation:
○​ Effort = a * (LOC)^b
○​ For an organic mode project, constants a = 2.4 and b = 1.05

3.2 Effort Calculation:

Effort = 2.4 * (8000)^1.05 = 2.4 * 18723.5 = 44,936.4 person-hours

3.3 Duration Estimation:

Assuming an average developer productivity of 20 person-hours per week:

Duration = Effort / Productivity = 44,936.4 / 20 = 2,246.8 weeks ≈ 43.2 months

4. Conclusion

Software cost estimation is an iterative process that requires continuous refinement. By using
appropriate models like COCOMO and considering project-specific factors, we can improve
estimation accuracy and make informed decisions regarding project budgets and schedules.

NAME : P.RAHUL 18
ENROLLMENT NUMBER : 2303031460145
 Faculty of Engineering & Technology
. Software Engineering Laboratory (303105253)

NAME : P.RAHUL 19
ENROLLMENT NUMBER : 2303031460145
Tab 2
 Model Reason to Use/Not Use

Waterfall Not suitable since requirements

are not fully clear from the start.
Inflexible to change.

V-Model Not suitable as it emphasizes

testing after development
phases are complete.

Incremental Chosen because the project can

be delivered in multiple phases.

Prototyping Useful in the early stages to

refine requirements. However, it
is not suitable for full
implementation.

Spiral Too complex for this project. Risk

management is not a primary
concern.

Agile Partially Chosen since iterative

development with frequent
feedback is required.

RAD Not suitable as it emphasizes

fast development, which is not a
priority.
11. Conclusion

The most suitable design and implementation model for the tailoring shop website is
a combination of the Incremental Model and Agile Model. The Incremental
approach allows for the step-by-step development and delivery of essential modules,
while Agile practices facilitate continuous feedback and changes. This hybrid
approach ensures timely delivery, flexibility, and customer satisfaction.

Model Reason to Use/Not Use

Waterfall Not suitable since requirements are not

fully clear from the start. Inflexible to
change.

V-Model Not suitable as it emphasizes testing

after development phases are complete.

Incremental Chosen because the project can be

delivered in multiple phases.

Prototyping Useful in the early stages to refine

requirements. However, it is not suitable
for full implementation.

Spiral Too complex for this project. Risk

management is not a primary concern.

Agile Partially Chosen since iterative

development with frequent feedback is
required.

RAD Not suitable as it emphasizes fast

development, which is not a priority.

11. Conclusion

The most suitable design and implementation model for the tailoring shop website is
a combination of the Incremental Model and Agile Model. The Incremental
approach allows for the step-by-step development and delivery of essential modules,
while Agile practices facilitate continuous feedback and changes. This hybrid
approach ensures timely delivery, flexibility, and customer satisfaction.