Version 1.

Theme: eAmbulance

Project Name: LifeLink

Category: Website Design and Development
 Table of Contents
1.1 Background and Necessity for the Website ..................................... 3
1.2 Proposed Solution ........................................................................... 4
1.3 Purpose of the Document ................................................................ 5
1.4 Scope of Project… ......................................................................... 7
1.5 Constraints ...................................................................................... 7
1.6 Functional Requirements ................................................................ 7
1.7 Non-Functional Requirements ...................................................... 10
1.8 Interface Requirements ............................................................ ….11
1.8.1 Hardware .................................................................................. 11
1.8.2 Software ................................................................................... 11
1.9 Project Deliverables. ..................................................................... 11
1.1 Background and Necessity for the Website
This eAmbulance Website is a significant healthcare innovation that leverages
technology to address the critical requirement of efficient and timely emergency
medical transportation. Here are some reasons why such a Website would
be required:
 Prompt Assistance:
This Website will help individuals request for eAmbulance services promptly
and conveniently. It will also help them keep track of all the necessary updates
such as the type of eAmbulance, their individual costs, their availability, and so
on.

 Forge the Connection:

This Website will help patients and medical emergency services to work together
for saving a life. It will provide users with a secure and reliable platform to book
eAmbulance services during critical situations.

 Support and Maintenance:

Considering the vitality of this service, the Website must be available to its
users/patients 24/7. This information promotes responsible and holistic
approach to improve the emergency standards.

 Searching, Sorting, and Filtering Capabilities:

With a wide range of eAmbulance options, users may have specific preferences
as per their requirements. The Website's search, sort, and filter features allow
users to find all the eAmbulances that match their criteria efficiently. This saves
time and enhances the overall user experience by narrowing down options based
on their preferences.
 Customer Engagement and Loyalty:
A well-designed Website can foster customer engagement and loyalty by
offering the best and fastest eAmbulances at critical times. This engagement
strengthens the relationship between the customer and emergency services,
thereby leveraging technology to provide rapid, efficient, and life-saving
assistance to individuals.

1.2 Proposed Solution

The proposed solution is a Website called 'LifeLink' for eAmbulances. The
Website should enhance the efficiency and effectiveness of medical emergency
services where users can browse and view different eAmbulances based on their
requirements. It should also provide categories for different types of eAmbulances,
offer sorting and filtering options, and allow users to search for a specific
eAmbulance. Additionally, detailed information for each eAmbulance such as cost
and availability should be displayed.
 1.3 Purpose of the Document

The purpose of this document is to present a detailed description of the

Website, LifeLink, an online eAmbulance service through which users can
view different types of eAmbulances available near them.

This document explains the purpose and features of the Website, the
interface of the Website, what the Website will do, and the constraints under
which it must operate. This document is intended for both stakeholders and
developers of the Website.

Stakeholders and developers of the portal can use this document.

© Aptech Limited
 Sample Sitemap (with examples)

Landing Page

Upon selecting an option, such as eAmbulance types, it should display different

types of vehicles, their size, and price.

User Page

*Hard-coded values will be displayed since, there is no scope for database fetching
in this Website.
1.4 Scope of Project
The scope of this project is to develop a responsive and visually appealing
Web portal for the users. This portal allows users to seamlessly and quickly
search for the best eAmbulance for their requirement in any situation. Key
features will include real-time availability, cost comparisons, and user-
friendly navigation. The goal is to ensure that users can find the right
emergency medical transport with minimal effort and maximum efficiency.

1.5 Constraints
The Web portal will not have any facility to store information on the server.
Information can be fetched from JSON/TXT files and users can view the same
being displayed. However, information cannot be written to the files from within
the portal.

1.6 Functional Requirements

The portal will be designed as a Single-Page-Application (SPA) and a responsive
Website with a set of pages and menus that represent choice of activities to be
performed. The pages, menus, and other visual elements must be designed in a
visually appealing manner with attractive fonts, colors, and animations wherever
applicable. All of these should also be laid out in a responsive manner.

Following are the functional requirements of the portal:

Home Page:
The Website should allow users to browse through the catalog and view individual
eAmbulance listings.
About Us Page:
• Users should be able to view information about the company and creators
of the site. The company information can include number of cities/regions
served by them and best performing eAmbulances.

Image Gallery:
• Users should be able to view different eAmbulance images uploaded on the
Website.

Search, Sort, and Filter menus:

Users should be able to search for different types of eAmbulances and sort/filter
them as per their requirements. One can search according to the area/region, for
example, user can type ‘Chicago’ and it should display the eAmbulances available
in this particular region. Sort and Filter should display based on users requirement
such as costs or type of vehicle he/she wants.

eAmbulance Type:
The eAmbulance type menu should display the type/kind of vehicle, size, and
equipment along with its costs to the users. The menu can also include
specialization of the eAmbulance, such as A/C or Non-A/C, ICU or ICCU, and so
on.

For example, users can search based on price $12 so it should display the
ambulances available for this cost range.

Feedback:
The Feedback option should enable users to provide their feedback about the
eAmbulance Website through a feedback form.

Contact Us:
The Contact Us field should display the contact information of the creators of the
Website. An email id and Contact Number can be displayed here.

Sitemap: To help users understand the flow of the Website, you will create a
Sitemap and add it to the home page of your Website.
Checkout or payment functionality regarding eAmbulances are not
required to be implemented.

Technical Considerations:

• Use HTML5, CSS3, Figma Toolkit, Bootstrap, jQuery, and JavaScript to

build the User Interface (UI).
• Use either Angular or ReactJS to develop the application's frontend and
add dynamic and responsive features along with SPA functionality.
• Use JSON/TXT files to handle data retrieval.
• Ensure the application is responsive and compatible with different screen
sizes.
Tasks:

1. Design the UI for the LifeLink Website including the catalog display,
search bar, sorting options, and eAmbulance information section.
2. Create necessary components and services to display the Ambulance
type and handle searching, sorting, and filtering operations.
3. Implement the Website’s required functionalities.
4. Implement GPS functionality as applicable.
5. Optionally, use REST APIs if you are well-versed with them.
6. Test the Website's functionality including browsing, searching, and
adding feedback. Deploy the Website to a local Web server such as
XAMPP for testing purposes.

Important: Do NOT use boilerplate templates or readymade templates for

development as it will adversely affect your evaluation. Your own Website design
and development skills will be tested, hence no third-party templates should be
used here.
1.7 Non-Functional Requirements
There are several non-functional requirements that should be fulfilled by the
Website. These include:

Safe to use: The Website should not result in any malicious downloads or
unnecessary file downloads.
Accessibility: The Website should have clear and legible fonts, user-interface
elements, and navigation elements.
User-friendliness: The Website should be easy to navigate with clear and
easy to understand elements.
Operability: The Website should be reliable and efficient.
Performance: The Website should demonstrate high value of performance
through speed and throughput. In simple terms, the Website should have
minimal load time and smooth page redirection.
Scalability: The Website should support a large number of concurrent users.
Availability: The Website should be available 24/7 with minimum downtime.
Compatibility: The Website should be compatible with latest browsers and
devices.

These are the bare minimum expectations from the

project. It is a must to implement the FUNCTIONAL and
NON-FUNCTIONAL requirements given in this SRS.

Once they are complete, you can use your own creativity
and imagination to add more features if required.
 1.8 Interface Requirements
1.8.1 Hardware
Intel Core i5/i7 Processor or higher
8 GB RAM or higher
Color SVGA
500 GB Hard Disk space
Mouse
Keyboard

1.8.2 Software
Technologies to be used:

IDE: Visual Studio Code / Notepad++ / CoffeeCup or any other HTML Editor

Frontend: HTML5, CSS3, Bootstrap (optional), JavaScript, Figma Toolkit, jQuery,

AngularJS/Angular 9 or higher/ReactJS 18 or higher, and XML

Data Store: JSON/TXT

1.9 Project Deliverables

You will design and build the project and submit it along with a complete project report
that includes:
• Problem Definition
• Design Specifications
• Diagrams such as flowcharts for various Activities, Data Flow Diagrams, and so on
• Test Data Used in the Project
• Project Installation Instructions (if any)

Documentation is considered a very important part of the project. Ensure that the
documentation is complete and comprehensive. Documentation should not include any
source code.

The consolidated project must be submitted as a zip file containing the source code used
for the complete Website. Include a ReadMe file mentioning software used,
assumptions made (if any), and test data used.

Submit a video (.mp4 file) demonstrating the working of the Website,

including all the functionalities of the project. This is MANDATORY.
~~~ End of Document ~~~