- Introduced new documentation for the DataHUB service, including purpose, roles, and business case. - Added detailed API reference for Quotes and Visits, including search endpoints and response structures. - Created sections for service records, time reports, and visits in the CustomerHUB documentation. - Implemented a change log and test plan for the DataHUB project. - Updated the introduction to include links to the new DataHUB documentation. - Modified navbar configuration to reflect changes in documentation structure.
35 lines
1.1 KiB
Markdown
35 lines
1.1 KiB
Markdown
---
|
|
sidebar_position: 1
|
|
title: Purpose & Roles
|
|
---
|
|
|
|
# Purpose & Roles
|
|
|
|
## Purpose and Guidance
|
|
|
|
This document specifies how the defined functions shall be developed or how the application shall be customized to solve the business requirements.
|
|
|
|
The **Solution Description** defines what will be delivered. The solution is matched against the requirements described in the Requirements section.
|
|
|
|
The **Delimitations** describe what is explicitly not covered by this spec. Together with the Solution description, these sections delimit the extent of the functional addition agreed for implementation.
|
|
|
|
The **Business Requirements and References** describe the business problem(s) to be resolved by this HUB spec. This section should be completed by a representative of the business user. The language of this section is aimed at capturing the desired outcomes and is less concerned with how those outcomes will be achieved.
|
|
|
|
---
|
|
|
|
## HUB Process Roles and Responsibilities
|
|
|
|
### Customer
|
|
|
|
- ME to provide Tech from their end for testing
|
|
|
|
### Hoist Developer (DEV)
|
|
|
|
- Najib El-Husseini (Senior)
|
|
- Tiago Pereira (Senior)
|
|
- Jaime Mesa (Junior)
|
|
|
|
### HUB Delivery Lead
|
|
|
|
- Dan Lefebvre
|